Update about-forks.md for clarity and style

Refined the About forks article to improve readability, conciseness, and user focus. 

Changes include:
- Shortened the introduction to a single, punchy sentence emphasizing user benefit.
- Simplified explanations of how forks differ from branches.
- Streamlined "When to use a fork" section with concise, actionable bullets.
- Ensured headings, formatting, and links match GitHub Docs style.
- Removed unnecessary technical details and extra words for scannability.

These changes align the article with other "About" articles and improve clarity for readers.

Author: SachinSingh008

content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md

@@ -1,6 +1,6 @@
 ---
 title: About forks
-intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
+intro: A fork is your personal copy of a repository that lets you experiment safely and propose changes to the original project.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks
   - /articles/about-forks
@@ -16,36 +16,35 @@ topics:
 
 ## About forks
 
-Forks are like independent copies of repositories. Unlike branches, forks give you more freedom to experiment without affecting the original project. Unlike cloned or duplicated repositories, changes from forks can be merged back into the upstream repository via pull requests, similar to a branch.
+A fork is an independent copy of a repository. It lets you experiment without affecting the original and propose changes via pull requests.
 
-When you view a forked repository on {% data variables.product.github %}, the upstream repository is indicated below the name of the fork.
+The upstream repository appears below the fork’s name on {% data variables.product.github %}.
 
 ![Screenshot of a repository's page on GitHub. Below the name of the repository, "mona/docs", the text "forked from github/docs" is outlined in orange.](/assets/images/help/pull_requests/fork-path.png)
 
-## What makes forks distinct from branches
+## How forks differ from branches
 
-Each fork is a complete repository with its own:
+Each fork has:
 
-* Branches
-* Members and discussions
+* Its own branches
+* Discussions and members
 * Issues and pull requests
 * Actions and projects
 * Tags, labels, and wikis
 
 ## When to use a fork
 
-There are times when a fork may be a better fit for your task than a branch would be. A fork might be better:
+Use a fork to:
 
-* To experiment safely without affecting the original project
-* To create separate space for discussions unrelated to a project's main goals
-* When you might want to make your work an independent repository later
+* Experiment safely
+* Hold separate discussions
+* Make your work independent
 
 ## Which repositories can be forked?
 
 {% data reusables.repositories.you-can-fork %}
 
 ## Next steps
 
-For instructions for forking a repository, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).
-
-For more information about when you can create forks, and the permission and visibility settings of forks, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks).
+- [Fork a repository](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)  
+- [About permissions and visibility of forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks)