Skip to content

Typo in github-glossary#gitfile #33102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
nguyenalex836 opened this issue May 21, 2024 · 0 comments · Fixed by #33114
Closed
1 task done

Typo in github-glossary#gitfile #33102

nguyenalex836 opened this issue May 21, 2024 · 0 comments · Fixed by #33114
Labels
content This issue or pull request belongs to the Docs Content team get started Content related to "Getting Started" doc set good first issue Good for newcomers

Comments

@nguyenalex836
Copy link
Contributor

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/get-started/learning-about-github/github-glossary#gitfile

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

You can view this file for your repository on the command line with git rev-parse --git-dir. that is the real repository.

The first letter of the second sentence should be capitalized

Additional information

No response

@nguyenalex836 nguyenalex836 added good first issue Good for newcomers content This issue or pull request belongs to the Docs Content team get started Content related to "Getting Started" doc set labels May 21, 2024
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label May 21, 2024
@nguyenalex836 nguyenalex836 removed the triage Do not begin working on this issue until triaged by the team label May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team get started Content related to "Getting Started" doc set good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant