git: acce2c6f1c - main - committers-guide: spell checks

The branch main has been updated by ceri:

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

commit acce2c6f1c52fe3bcb23c57717d88143dec5b7e9
Author:     Ceri Davies <ceri@FreeBSD.org>
AuthorDate: 2023-03-05 10:43:22 +0000
Commit:     Ceri Davies <ceri@FreeBSD.org>
CommitDate: 2023-03-05 10:43:22 +0000

    committers-guide: spell checks
---
 .../content/en/articles/committers-guide/_index.adoc       | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
index e4e7a3821b..17d6aed381 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -3123,7 +3123,7 @@ The Tier rules for feature support on architectures at release-time are more str
 [[compilers]]
 === Policy on Multiple Compilers
 
-FreeBSD build with both Clang and GCC.
+FreeBSD builds with both Clang and GCC.
 The project does this in a careful and controlled way to maximize benefits from this extra work, while keeping the extra work to a minimum.
 Supporting both Clang and GCC improves the flexibility our users have.
 These compilers have different strengths and weaknesses, and supporting both allows users to pick the best one for their needs.
@@ -3131,17 +3131,17 @@ Clang and GCC support similar dialects of C and C++, necessitating a relatively
 The project gains increased code coverage and improves the code quality by using features from both compilers.
 The project is able to build in more user environments and leverage more CI environments by supporting this range, increasing convenience for users and giving them more tools to test with.
 By carefully constraining the range of versions supported to modern versions of these compilers, the project avoids unduely increasing the testing matrix.
-Older and obscure compilers, as well as older dialects of the langauges, have extemely limited support that allow user programs to build with them, but without constraining the base system to being built with them.
+Older and obscure compilers, as well as older dialects of the langauges, have extremely limited support that allow user programs to build with them, but without constraining the base system to being built with them.
 The exact balance continues to evolve to ensure the benefits of extra work remain greater than the burdens it imposes.
 The project used to support really old Intel compilers or old GCC versions, but we traded supporting those obsolete compilers for a carefully selected range of modern compilers.
 This section documents where we use different compilers, and the expectations around that.
 
-The FreeBSD project provides an in-tree compiler Clang compiler.
+The FreeBSD project provides an in-tree Clang compiler.
 Due to being in the tree, this compiler is the most supported compiler.
-All changes must to compile with it, prior to commit.
+All changes must compile with it, prior to commit.
 Complete testing, as appropriate for the change, should be done with this compiler.
 
-The FreeBSD project also supports one or more out-of-tree compilers.
+At any moment in time, the FreeBSD project also supports one or more out-of-tree compilers.
 At present, this is GCC 12.x.
 Ideally, committers should test compile with this compiler, especially for large or risky changes.
 This compiler is available as the ${TARGET_ARCH}-gcc package, such as package:aarch64-gcc[] or package:riscv64-gcc[].
@@ -3167,9 +3167,9 @@ The FreeBSD project provides headers and libraries that allow other compilers to
 These headers have support for making the environment as strict as the standard, supporting prior dialects of ANSI-C back to C89, and other edge cases our large ports collection has uncovered.
 This support constrains retirement of older standards in places like header files, but does not constrain updating the base system to newer dialects.
 Nor does it require the base system to compile with these older standards as a whole.
-Breaking this support will cause packages in the ports collection to fail, and should be avoided where possible, and prompty fixed when it is easy to do so.
+Breaking this support will cause packages in the ports collection to fail, so should be avoided where possible, and promptly fixed when it is easy to do so.
 
-The FreeBSD build system currently accomodates these different environments.
+The FreeBSD build system currently accommodates these different environments.
 As new warnings are added to compilers, the project tries to fix them.
 However, sometimes these warnings require extensive rework, so are suppressed in some way by using make variables that evaluate to the proper thing depending on the compiler version.
 Developers should be mindful of this, and ensure any compiler specific flags are properly conditionalized.