Update about-forks.md for clarity and style

[SachinSingh008]

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.

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@SachinSingh008 This was one of the examples for how "about" articles SHOULD look. We specifically did NOT make it as efficient as possible, because it's introductory and a little inefficiency feels human and friendly. This has been very intentionally written as it is, and we're not going to accept these edits, sorry. I recommend you concentrate on an "about" article that hasn't already been edited.