Skip to content

Commit 8462b48

Browse files
authored
Clarify why you'd use a fork (github#26153)
1 parent a952b20 commit 8462b48

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/get-started/quickstart/fork-a-repo.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ topics:
2121
---
2222
## About forks
2323

24-
Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
24+
Most commonly, forks are used to either propose changes to someone else's project to which you don't have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
2525

2626
### Propose changes to someone else's project
2727

0 commit comments

Comments
 (0)