git: 588168db0e - main - 2024q2 report: Copyedit github.adoc

The branch main has been updated by imp:

URL: https://cgit.FreeBSD.org/doc/commit/?id=588168db0ea3e262e4a2cc3ccbe2d85cf880c783

commit 588168db0ea3e262e4a2cc3ccbe2d85cf880c783
Author:     Warner Losh <imp@FreeBSD.org>
AuthorDate: 2024-07-09 02:37:20 +0000
Commit:     Warner Losh <imp@FreeBSD.org>
CommitDate: 2024-07-09 02:37:20 +0000

    2024q2 report: Copyedit github.adoc
    
    Apply the edits Pau submitted, and fix a few problems that I noticed while doing so.
    
    Submitted by: Pau Amma
    Sponsored by: Netflix
---
 .../en/status/report-2024-04-2024-06/github.adoc   | 30 ++++++++++++----------
 1 file changed, 16 insertions(+), 14 deletions(-)

diff --git a/website/content/en/status/report-2024-04-2024-06/github.adoc b/website/content/en/status/report-2024-04-2024-06/github.adoc
index 38314811ca..5ea8718009 100644
--- a/website/content/en/status/report-2024-04-2024-06/github.adoc
+++ b/website/content/en/status/report-2024-04-2024-06/github.adoc
@@ -1,28 +1,30 @@
-=== FreeBSD Github Pull Request Report
+=== FreeBSD GitHub Pull Request Report
 
 Links: +
-link:https://wiki.freebsd.org/WorkingGroup/Github[Github Working Group wiki page] URL: link:https://wiki.freebsd.org/WorkingGroup/Github[]
+link:https://wiki.freebsd.org/WorkingGroup/Github[GitHub Working Group wiki page] URL: link:https://wiki.freebsd.org/WorkingGroup/GitHub[] +
+link:https://github.com/freebsd/freebsd-src/pulls[FreeBSD Base System Pull Requests] URL: link:https://github.com/freebsd/freebsd-src/pulls[]
 
 Contact: Warner Losh <imp@FreeBSD.org>
 
-The FreeBSD Project has been trying an experiment to accpet contributions via github pull requests.
-We've leared a lot in the last year that we've been doing this.
-We've created a number of rules relating to the pull requests.
+The FreeBSD Project has been trying an experiment to accept contributions via GitHub pull requests.
+We have learned a lot in the last year that we've been doing this.
+We have created a number of rules relating to the pull requests.
 In general, pull requests should only be for things that are user-visible, add value to the project and are ready to go, modulo final review.
 
-At this point, we're able to keep up with the pull requests doing everything by hand.
-This has proven to be tedious and error prone.
-While the vast majority of the pull requests have been fine, but we have introduced a few problems.
-We've started working on scripting to automate staging and landing in the tree.
+At this point, we are able to keep up with the pull requests doing everything by hand.
+However, this has proven to be tedious and error-prone.
+While the vast majority of the pull requests have been fine, we have introduced a few problems.
+We have started working on scripting to automate staging and landing in the tree.
 
 We need help with automating the process:
-* Adding the ability to batch multiple pull requests
-* Add automated testing that's context specific (eg, run igor over man pages)
+* Add the ability to batch multiple pull requests
+* Add automated testing that's context specific (for example, run igor over man pages)
 * Add build/install tests that test boot the resulting image
 * Integrate CI we currently do post-commit so we can do it before for these changes.
 
-We are coordinating on FreeBSD's Discord in the #githib-hacking channel.
+We are coordinating on FreeBSD's Discord in the #github-hacking channel.
 
-Once we have things finded tuned, we'll be looking to expand this by doing publicity to steer contributors to at least the base system to github.
-We'll also need more developers to review and land pull requests once it's automated that the automation has matured.
+Once we have things fine-tuned, we will be looking to expand this by doing publicity to steer contributors to at least the base system to GitHub.
+We need more developers looking at the FreeBSD GitHub pull requests
+We will also need more developers to review and land pull requests once it is automated and the automation has matured.
 We sincerely hope that we can improve the FreeBSD contribution experience with this, as well as gain useful fixes from the community.