Minor documentation formatting and wording improvement in README

This PR makes two small improvements to the README:

• Removes trailing whitespace after a sentence
• Improves wording in one sentence for readability

No functional changes.

AI assistance was used only to help draft the wording,
and the changes were verified manually.

Author: 24ds1000054-code

README.md

@@ -11,13 +11,13 @@ Welcome to GitHub Docs! GitHub’s documentation is open source, meaning anyone
 
 ## How we sync changes across Docs repositories
 
-There are two GitHub Docs repositories: 
+There are two GitHub Docs repositories:
 
 - **`github/docs`** (public): Open to external contributions
 
 - **`github/docs-internal`** (private): For GitHub employee contributions. 
 
-The two repositories sync frequently. Content changes in one are reflected in the other.  Hubbers might prefer to post in `docs` when working with a customer, but `docs` has limitations on the types of contributions it accepts to safeguard the site and our workflows. Internal contributions should usually go to `docs-internal`.
+The two repositories sync frequently, so content changes in one are reflected in the other.  Hubbers might prefer to post in `docs` when working with a customer, but `docs` has limitations on the types of contributions it accepts to safeguard the site and our workflows. Internal contributions should usually go to `docs-internal`.
 
 **Important:** The `docs` repository accepts contributions to content files (`.md` files in `/content` and select `/data` sections like reusables only). Infrastructure files, workflows, and site-building code are not open for external modification.