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 893bbf24c8d2..534d01a01498 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
@@ -46,9 +46,10 @@ Forking a repository is similar to duplicating a repository, with the following
 * Code pushed to a fork is visible to all repositories in the fork network, even after that fork is deleted.
 * You can use a pull request to suggest changes from your fork to the upstream repository.
 * You can bring changes from the upstream repository to your fork by synchronizing your fork with the upstream repository.
-* Forks have their own members, branches, tags, labels, policies, issues, pull requests, discussions, actions, projects, and wikis.
 * Forks inherit the restrictions of their upstream repositories. For example, branch protection rules cannot be passed down if the upstream repository belongs to an organization on a {% data variables.product.prodname_free_team %} plan.
 
+Like duplicated repositories, forks have their own members, branches, tags, labels, policies, issues, pull requests, discussions, actions, projects, and wikis.
+
 ## Further reading
 
 * [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)