Misplaced word in 'Repository Terminology' under 'About repositories'

[ashwingopalsamy]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/repositories/creating-and-managing-repositories/about-repositories#repository-terminology

What part(s) of the article would you like to see updated?

What part(s) of the article would you like to see updated?

• The definition of "Upstream" under the "Repository Terminology" section.

Give as much detail as you can to help us understand the change you want to see.

• The current definition states: "Upstream: The branch on an original repository that has been forked or cloned. The corresponding branch on the cloned or forked branch is called the "downstream.""
• The word "repository" should be used instead of "branch" in the later part of the definition.
  • "Upstream: The branch on an original repository that has been forked or cloned. The corresponding branch on the cloned or forked branch repository is called the "downstream.""

Why should the docs be changed? What use cases does it support?

• The current definition is inaccurate and can mislead users, especially beginners, about the relationship between upstream and downstream repositories.
• Correcting this definition will:
  • Improve the accuracy and clarity of the documentation.
  • Prevent confusion and misunderstandings for users learning about Git and GitHub.
  • Ensure that users have a solid foundation for understanding how forking and cloning work in a Git environment.

What is the expected outcome or behavior?

The definition of "Upstream" should be updated:

Upstream: The branch on an original repository that has been forked or cloned. The corresponding branch on the cloned or forked repository is called the "downstream."

• This change will provide users with a correct and accurate understanding of the upstream and downstream relationships in Git.

Additional information

• Reproducibility: This is a factual error in the documentation, so it's consistently reproducible.

• User impact: The impact is potentially significant as incorrect terminology can:

  • Lead to confusion and misunderstanding among users, especially beginners.
  • Hinder effective collaboration and code management practices.
  • Create difficulties in understanding and troubleshooting issues related to forking and cloning.

• Context: The incorrect definition appears within the "Repository Terminology" section of the GitHub documentation, likely within a page or section dedicated to explaining Git concepts and workflows.

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[nguyenalex836]

@ashwingopalsamy Thank you for opening an issue and linking it to your PR! ✨

[ashwingopalsamy]

Thanks, @nguyenalex836. Glad I could help.