git: 74813b1356 - main - portmgr/qa: Pet vale

The branch main has been updated by bofh:

URL: https://cgit.FreeBSD.org/doc/commit/?id=74813b13562efa2e3a71f2b781f5a4ae548c9c5e

commit 74813b13562efa2e3a71f2b781f5a4ae548c9c5e
Author:     Muhammad Moinur Rahman <bofh@FreeBSD.org>
AuthorDate: 2023-12-24 23:20:40 +0000
Commit:     Muhammad Moinur Rahman <bofh@FreeBSD.org>
CommitDate: 2023-12-24 23:22:38 +0000

    portmgr/qa: Pet vale
    
    - Remove pronouns like our
    - Utilize conscious words
    - Remove references to portupgrade
    
    Approved by:    portmgr
---
 website/content/en/portmgr/qa.adoc | 24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)

diff --git a/website/content/en/portmgr/qa.adoc b/website/content/en/portmgr/qa.adoc
index 291c7a3a0c..ed944861e4 100644
--- a/website/content/en/portmgr/qa.adoc
+++ b/website/content/en/portmgr/qa.adoc
@@ -5,7 +5,8 @@ sidenav: about
 
 = Quality Assurance Tasks for the Ports Management Team
 
-There are a number of tasks that the Ports Management Team undertakes to try to improve the quality of the Ports Collection. These fall into two main categories: link:#qa-before-release[activities during a release cycle] and link:#qa-between-releases[activities between release cycles].
+There are a number of tasks that the Ports Management Team undertakes to try to improve the quality of the Ports Collection.
+These fall into two main categories: link:#qa-before-release[activities during a release cycle] and link:#qa-between-releases[activities between release cycles].
 
 [[qa-before-release]]
 == Activities During a Release Cycle
@@ -17,13 +18,17 @@ There are a number of tasks that the Ports Management Team undertakes to try to
 [[qa-between-releases]]
 == Activities Between Release Cycles
 
-* Manage the https://pkg-status.freebsd.org/[Ports Build Cluster] machines. These machines continually build packages on all possible combinations of OS release and CPU architecture (in our terminology, `build environments`.)
+* Manage the https://pkg-status.freebsd.org/[Ports Build Cluster] machines.
+* These machines continually build packages on all possible combinations of OS release and CPU architecture (in FreeBSD terminology, `build environments`.)
 
-These builds also produce error logs for packages that do not build correctly (see the above URL). Periodically, the team marks these ports as BROKEN so that maintainers may be notified. (See below.)
+These builds also produce error logs for packages that do not build correctly (see the above URL).
+Periodically, the team marks these ports as BROKEN so that maintainers may be notified. (See below.)
 
-Successfully built packages (at least, the ones that are freely redistributable) are also copied to the master FTP server and thus become the default "latest package" for installations that use packages rather than ports.
+Successfully built packages (at least, the ones that are freely redistributable) are also copied to the primary FTP server and thus become the default "latest package" for installations that use packages rather than ports.
 
-* Notify the FreeBSD community of problems within the Ports Collection so that problems do not get overlooked. To do this, there are a number of emailed reports. Ones marked `public` are posted to freebsd-ports.
+* Notify the FreeBSD community of problems within the Ports Collection so that problems do not get overlooked.
+To do this, there are a number of emailed reports.
+Ones marked `public` are posted to freebsd-ports.
 
 ** a public list of all ports to be removed due to security problems, build failures, or general obsolescence, unless they are fixed first.
 
@@ -35,10 +40,13 @@ Successfully built packages (at least, the ones that are freely redistributable)
 
 ** public email about port commits that break building of INDEX.
 
-** public email about port commits that send the revision metadata backwards (and thus confuse tools like portupgrade).
+** public email about port commits that send the revision metadata backwards
 
 ** private email to an affected port maintainer when a port is about to be marked BROKEN, Cc:ed to the last committer to the port. (This email is not automated but it should be sent as a courtesy.)
 
-* Remove expired ports. Ports that have been marked BROKEN for some time are marked DEPRECATED (with an EXPIRATION_DATE) and then are removed if no one has fixed them by that time. The intent of this process is to try to ensure that if a user installs a port, there is the best possible chance that it can be made to work.
+* Remove expired ports.
+Ports that have been marked BROKEN for some time are marked DEPRECATED (with an EXPIRATION_DATE) and then are removed if no one has fixed them by that time.
+The intent of this process is to try to ensure that if a user installs a port, there is the best possible chance that it can be made to work.
 
-In other cases, ports are marked DEPRECATED when they have been replaced by a newer version and the older version is no longer maintained by the authors. The EXPIRATION_DATE should generally be set at least two months in the future to allow everyone sufficient time to upgrade.
+In other cases, ports are marked DEPRECATED when they have been replaced by a newer version and the older version is no longer maintained by the authors.
+The EXPIRATION_DATE should generally be set at least two months in the future to allow everyone sufficient time to upgrade.