Skip to content

Commit e263f28

Browse files
authored
Merge branch 'main' into repo-sync
2 parents 82a12e7 + 377a947 commit e263f28

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ That's how you can easily become a member of the GitHub Documentation community.
3333
## READMEs
3434

3535
In addition to the README you're reading right now, this repo includes other READMEs that describe the purpose of each subdirectory in more detail:
36-
YOu can go through among them for specified details regarding the topics listed below.
36+
You can go through among them for specified details regarding the topics listed below.
3737

3838
- [content/README.md](content/README.md)
3939
- [content/graphql/README.md](content/graphql/README.md)

content/get-started/using-git/getting-changes-from-a-remote-repository.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ $ git pull <em>remotename</em> <em>branchname</em>
7777

7878
Because `pull` performs a merge on the retrieved changes, you should ensure that
7979
your local work is committed before running the `pull` command. If you run into
80-
[a merge conflict](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
80+
[a merge conflict](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)
8181
you cannot resolve, or if you decide to quit the merge, you can use `git merge --abort`
8282
to take the branch back to where it was in before you pulled.
8383

0 commit comments

Comments
 (0)