Fix Sentence Construction

[Sriparno08]

Why:

The below sentence is hard to understand:

Only pull request authors can give upstream repository maintainers, or those with push access to the upstream repository, permission to make commits to their pull request's compare branch in a user-owned fork.

Hence, I have decided to change the sentence construction to make it a bit easier to understand.

Closes #23021

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

I have changed the sentence to:

Check off the following:

• I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
• For content changes, I have completed the self-review checklist.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md	fpt ghec ghes@ 3.7 3.6 3.5 3.4 3.3 ghae	fpt ghec ghes@ 3.7 3.6 3.5 3.4 3.3 ghae

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

[cmwilson21]

@Sriparno08 Thanks for the PR! The original issue is still waiting for review, so once that happens, someone will review your PR based on the issue's review. ✨

In the mean time, please take a look at our help wanted section to find open issues you can work on. All items on this board have already been approved and have directions or a plan to get contributors started. 👍

[Sriparno08]

Alright, @cmwilson21 👍

[isaacmbrown]

Hi @Sriparno08, thanks for the PR ✨ I think your proposal will clear up a lot of confusion with a small adjustment:

Although it wasn't very clear from the original wording, in this context upstream repository maintainer means anyone with push access to the upstream repository. Your proposal makes it sound like you can choose to give access either only to people with the maintainer role, or to anyone with push access to the upstream. If you look at the instructions on the page, you'll see that this level of granularity isn't available:

On user-owned forks, if you want to allow anyone with push access to the upstream repository to make changes to your pull request, select Allow edits from maintainers.

If you could edit your wording to make that clearer, I think this will be looking great! 🚀

[Sriparno08]

Okay @isaacmbrown! Let me fix it!

[Sriparno08]

Hey @isaacmbrown, I have made some changes. Have a look!

[isaacmbrown]

Hi @Sriparno08, looks good, thanks for making that change ✨

I just made a couple of changes with our style guide and translation workflow in mind. Otherwise this look good to go, and I'll add a label indicating that this can be merged 🚢

[Sriparno08]

Thanks, @isaacmbrown 👍

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡