From 5de36346621c6237fbea6d0d5ed220b51abf5bdf Mon Sep 17 00:00:00 2001 From: Ryosuke Nakayama Date: Thu, 10 Feb 2022 17:58:38 +0900 Subject: [PATCH] Update about-forks.md (#25209) --- .../working-with-forks/about-forks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index f9a5eda3a6..6a9ee0d344 100644 --- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -16,7 +16,7 @@ topics: --- Forking a repository is similar to copying a repository, with two major differences: -* You can use a pull request to suggest changes from your user-owned fork to the original repository, also known as the *upstream* repository. +* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository. * You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository. {% data reusables.repositories.you-can-fork %}