@@ -15,18 +15,18 @@ Reference Manual for more information on these types of releases.
The infrastructure behind the test environment is the
:ref:`Yocto Project Autobuilder <test-manual/intro:Yocto Project Autobuilder
-Overview>`. The Autobuilder contains a set of Builders that are associated to an
+Overview>`. The Autobuilder contains a set of Builders that are associated with an
architecture or a feature to test. For example, the ``qemuarm64`` builder
corresponds to testing the ARM 64-bit architecture.
Below is a comprehensive list of target architectures and features that are
supported, as well as their level of support. For each architecture or feature,
-their corresponding builders are also listed.
+the corresponding builders are also listed.
Primary Supported
=================
-The term "primary" means that dedicated builds for these architectures or
+The qualifier "primary" means that dedicated builds for these architectures or
features are being run on a daily basis on the Yocto Project Autobuilder and
also tested with incoming changes before they merge. These changes are usually
on the "-next" Git branches of the :term:`OpenEmbedded-Core (OE-Core)`
@@ -158,10 +158,10 @@ Below is a list of primary tested features, their maintainer(s) and builder(s):
Secondary Supported
===================
-The term "secondary" means that in some cases there is code/feature/support
+The qualifier "secondary" means that, in some cases, there is code/feature/support
which is desired by people using the project and is in the project's interests
-to support, however there isn't wide enough interest and support to justify
-testing all incoming changes on it. There are however project member
+to support; however, there isn't wide enough interest and support to justify
+testing all incoming changes. There are, however, project member
organisations and maintainers willing to run tests and review fixes.
This category may be applicableï¿œas support/usage in an area develops and grows,
@@ -235,7 +235,7 @@ builder(s):
Untested
========
-"Untested" means that whilst the configurations are present in the project, we
+"Untested" means that, whilst the configurations are present in the project, we
don't currently run the tests on any regular basis and new changes are not
tested against them. We may take patches in these areas if they make sense but
it is on a best effort only basis.
Nothing significant, just grammar and punctuation fixes in Chapter 2. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> --- if none of this justifies churn, i'm fine with antonin just dropping it.