Fix assorted typos and grammar

30 files changed, 42 insertions, 42 deletions

diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
index f516658001..535131be28 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -1907,7 +1907,7 @@ Once you're done, `git commit` and you'll have the remainder in your tree.
 You can run it multiple times as well, and even over multiple files (though I find it easier to do one file at a time
 and use the `git rebase -i` to fold the related commits together).
 
-===== Joining the FreeBSD GitHub oranization.
+===== Joining the FreeBSD GitHub organization.
 
 **Q:** How do I join the FreeBSD GitHub organization?
 
@@ -2220,7 +2220,7 @@ Add an entry for each additional mentor/mentee relationship in the bottom sectio
 [.filename]#src/.mailmap#, [.filename]#doc/.mailmap#, and [.filename]#ports/.mailmap# - Add an entry for commits you created prior to becoming a FreeBSD committer.
 +
 Mapping to your FreeBSD address allows us to track external committers who may be ready for a commit bit more easily.
-You can also use this to correct old names, mispelled names, etc in the default `git log` output.
+You can also use this to correct old names, misspelled names, etc in the default `git log` output.
 . Generate a Kerberos Password
 +
 See crossref:committers-guide[kerberos-ldap, Kerberos and LDAP web Password for FreeBSD Cluster] to generate or set a Kerberos account for use with other FreeBSD services like the link:https://bugs.freebsd.org/bugzilla/[bug-tracking database] (you get a bug-tracking account as part of that step).
@@ -3850,7 +3850,7 @@ https://gandi.net[Gandi] provides website hosting, cloud computing, domain regis
 
 Gandi offers an E-rate discount to all FreeBSD developers.
 To streamline the process of getting the discount first set up a Gandi account, fill in the billing information and select the currency.
-Then send an mail to mailto:non-profit@gandi.net[non-profit@gandi.net] using your `@freebsd.org` mail address, and indicate your Gandi handle.
+Then send an email to mailto:non-profit@gandi.net[non-profit@gandi.net] using your `@freebsd.org` mail address, and indicate your Gandi handle.
 
 [[benefits-rsync]]
 === `rsync.net`
diff --git a/documentation/content/en/articles/freebsd-releng/_index.adoc b/documentation/content/en/articles/freebsd-releng/_index.adoc
index 074ba54eeb..6f025fcd09 100644
--- a/documentation/content/en/articles/freebsd-releng/_index.adoc
+++ b/documentation/content/en/articles/freebsd-releng/_index.adoc
@@ -476,7 +476,7 @@ Then in the {branchHead} branch, which will now become a new major version:
 [[releng-stable]]
 == Release from {branchStable}
 
-This section describes the general procedures of the FreeBSD release cycle from an extablished {branchStable} branch.
+This section describes the general procedures of the FreeBSD release cycle from an established {branchStable} branch.
 
 [[releng-stable-slush]]
 === FreeBSD `stable` Branch Code Slush
diff --git a/documentation/content/en/articles/freebsd-status-report-process/_index.adoc b/documentation/content/en/articles/freebsd-status-report-process/_index.adoc
index bbee539159..6a254123f7 100644
--- a/documentation/content/en/articles/freebsd-status-report-process/_index.adoc
+++ b/documentation/content/en/articles/freebsd-status-report-process/_index.adoc
@@ -241,7 +241,7 @@ Once all the reports and the introduction are ready, the [.filename]#_index.adoc
 When all the files of the status report are ready, it is time to publish it.
 
 First [.filename]#doc/website/content/en/status/_index.adoc# is edited: the next due date is updated and a link to the new report is added.
-The change is then pushed on the repository and the status team checks that everythings works as expected.
+The change is then pushed on the repository and the status team checks that everything works as expected.
 
 Then the news entry for the main website page is added to [.filename]#doc/website/data/en/news/news.toml#.
 
diff --git a/documentation/content/en/articles/geom-class/_index.adoc b/documentation/content/en/articles/geom-class/_index.adoc
index eacd51a443..233a2f6478 100644
--- a/documentation/content/en/articles/geom-class/_index.adoc
+++ b/documentation/content/en/articles/geom-class/_index.adoc
@@ -364,7 +364,7 @@ The event functions are:
 
 These functions are called from the `g_down` kernel thread and there can be no sleeping in this context, (see definition of sleeping elsewhere) which limits what can be done quite a bit, but forces the handling to be fast.
 
-Of these, the most important function for doing actual useful work is the `.start`() function, which is called when a BIO request arrives for a provider managed by a instance of geom class.
+Of these, the most important function for doing actual useful work is the `.start`() function, which is called when a BIO request arrives for a provider managed by an instance of geom class.
 
 [[geom-threads]]
 === GEOM Threads
@@ -412,7 +412,7 @@ Now, this sounds good, but should be carefully thought out.
 Sleeping is well and very convenient but can very effectively destroy performance of the geom transformation.
 Extremely performance-sensitive classes probably should do all the work in `.start`() function call, taking great care to handle out-of-memory and similar errors.
 
-The other benefit of having a event-handler thread like that is to serialize all the requests and responses coming from different geom threads into one thread.
+The other benefit of having an event-handler thread like that is to serialize all the requests and responses coming from different geom threads into one thread.
 This is also very convenient but can be slow.
 In most cases, handling of `.done`() requests can be left to the `g_up` thread.
 
diff --git a/documentation/content/en/articles/gjournal-desktop/_index.adoc b/documentation/content/en/articles/gjournal-desktop/_index.adoc
index 070397cd9e..c1a1314368 100644
--- a/documentation/content/en/articles/gjournal-desktop/_index.adoc
+++ b/documentation/content/en/articles/gjournal-desktop/_index.adoc
@@ -559,7 +559,7 @@ For example, to create a 2 GB journal, you could use the following command:
 # gjournal label -s 2G /dev/ada1p1
 ....
 
-You can then initialyze a UFS file system on your new partition, enable journaling using `newfs(8)` on the `.journal` device, and disable Soft Updates using `tunefs(8)`:
+You can then initialize a UFS file system on your new partition, enable journaling using `newfs(8)` on the `.journal` device, and disable Soft Updates using `tunefs(8)`:
 
 [source,shell]
 ....
@@ -849,7 +849,7 @@ If journal replay completes successfully, the file system is returned to a consi
 When `fsck_ffs(8)` is later invoked during boot, it reads this state from the superblock and skips the file system check.
 
 For Soft Updates with journaling, recovery is initiated by `fsck_ffs(8)` itself.
-During the file system check phase at boot time, `fsck_ffs(8)` detects that the files ystem supports Soft Updates with journaling and invokes the journal replay logic.
+During the file system check phase at boot time, `fsck_ffs(8)` detects that the file system supports Soft Updates with journaling and invokes the journal replay logic.
 If journal replay reports that the file system is consistent, `fsck_ffs(8)` terminates early without performing a full check.
 If journal replay cannot complete successfully, a traditional file system check is performed.
 
diff --git a/documentation/content/en/articles/hubs/_index.adoc b/documentation/content/en/articles/hubs/_index.adoc
index 21ad08e9d1..46845ef9f6 100644
--- a/documentation/content/en/articles/hubs/_index.adoc
+++ b/documentation/content/en/articles/hubs/_index.adoc
@@ -245,7 +245,7 @@ Notice the website was split into www.FreeBSD.org and docs.FreeBSD.org, and ther
 === Mirroring Packages
 
 Due to very high requirements of bandwidth, storage and administration the FreeBSD Project has decided not to allow public mirrors of packages.
-For sites with lots of machines, it might be advantagous to run a caching HTTP proxy for the man:pkg[8] process.
+For sites with lots of machines, it might be advantageous to run a caching HTTP proxy for the man:pkg[8] process.
 Alternatively specific packages and their dependencies can be fetched by running something like the following:
 
 [source,shell]
diff --git a/documentation/content/en/articles/license-guide/_index.adoc b/documentation/content/en/articles/license-guide/_index.adoc
index 4fb86d1537..3afbef7742 100644
--- a/documentation/content/en/articles/license-guide/_index.adoc
+++ b/documentation/content/en/articles/license-guide/_index.adoc
@@ -66,7 +66,7 @@ The FreeBSD Project uses this text as the preferred license:
 
 The preferred order is the copyright notice first, followed by the SPDX-License-Identifier, but either order is acceptable.
 When both SPDX-License-Identifier and the full text of the license are present, the full text takes priority and the SPDX-License-Identifier is informational only.
-When both are present, the SPDX-License-Identifier will often preceed the copyright and license text.
+When both are present, the SPDX-License-Identifier will often precede the copyright and license text.
 
 The FreeBSD project does not allow using the "advertising clause" in new code.
 Due to the large number of contributors to the FreeBSD project, complying with this clause for many commercial vendors has become difficult.
diff --git a/documentation/content/en/articles/serial-uart/_index.adoc b/documentation/content/en/articles/serial-uart/_index.adoc
index 25e9d695d1..6fa57abf7e 100644
--- a/documentation/content/en/articles/serial-uart/_index.adoc
+++ b/documentation/content/en/articles/serial-uart/_index.adoc
@@ -1013,7 +1013,7 @@ One could conclude that wiring both ports for IRQ 3 using a handcrafted wire-mad
 You cannot duplicate IRQ 3 because the output drivers of each UART are wired in a "totem pole" fashion, so if one of the UARTs drives IRQ 3, the output signal will not be what you would expect.
 Depending on the implementation of the extension board or your motherboard, the IRQ 3 line will continuously stay up, or always stay low.
 
-You need to decouple the IRQ drivers for the two UARTs, so that the IRQ line of the board only goes up if (and only if) one of the UARTs asserts a IRQ, and stays low otherwise.
+You need to decouple the IRQ drivers for the two UARTs, so that the IRQ line of the board only goes up if (and only if) one of the UARTs asserts an IRQ, and stays low otherwise.
 The solution was proposed by Joerg Wunsch mailto:j@ida.interface-business.de[j@ida.interface-business.de]: To solder up a wired-or consisting of two diodes (Germanium or Schottky-types strongly preferred) and a 1 kOhm resistor.
 Here is the schematic, starting from the 4 by 3 jumper field above:
 
diff --git a/documentation/content/en/articles/solid-state/_index.adoc b/documentation/content/en/articles/solid-state/_index.adoc
index 998eae9da3..eed4c9afef 100644
--- a/documentation/content/en/articles/solid-state/_index.adoc
+++ b/documentation/content/en/articles/solid-state/_index.adoc
@@ -59,7 +59,7 @@ toc::[]
 
 The scope of this article will be limited to solid state disk devices made from flash memory.
 Flash memory is a solid state memory (no moving parts) that is non-volatile (the memory maintains data even after all power sources have been disconnected).
-Flash memory can withstand tremendous physical shock and is reasonably fast (the flash memory solutions covered in this article are slightly slower than a EIDE hard disk for write operations, and much faster for read operations).
+Flash memory can withstand tremendous physical shock and is reasonably fast (the flash memory solutions covered in this article are slightly slower than an EIDE hard disk for write operations, and much faster for read operations).
 One very important aspect of flash memory, the ramifications of which will be discussed later in this article, is that each sector has a limited rewrite capacity.
 You can only write, erase, and write again to a sector of flash memory a certain number of times before the sector becomes permanently unusable.
 Although many flash memory products automatically map bad blocks, and although some even distribute write operations evenly throughout the unit, the fact remains that there exists a limit to the amount of writing that can be done to the device.
diff --git a/documentation/content/en/articles/x86-assembly/_index.adoc b/documentation/content/en/articles/x86-assembly/_index.adoc
index c6d91aaaa9..612b8bface 100644
--- a/documentation/content/en/articles/x86-assembly/_index.adoc
+++ b/documentation/content/en/articles/x86-assembly/_index.adoc
@@ -2799,7 +2799,7 @@ Their sizes were chosen according to the above formula in such a way that the re
 For example, a very old Kodak Duaflex IV camera in my possession has three such holes for f-numbers 8, 11, and 16.
 
 A more recently made camera may offer f-numbers of 2.8, 4, 5.6, 8, 11, 16, 22, and 32 (as well as others).
-These numbers were not chosen arbitrarily: They all are powers of the square root of 2, though they may be rounded somewha.
+These numbers were not chosen arbitrarily: They all are powers of the square root of 2, though they may be rounded somewhat.
 
 [[x86-f-stop]]
 ==== The F-Stop
@@ -4034,7 +4034,7 @@ It is converting the text representation of a number into that number: The text
 To solve the conflict, we use the `std` op code early on.
 We cancel it with `cld` later on: It is quite important we do not `call` anything that may depend on the default setting of the _direction flag_ while `std` is active.
 
-Everything else in this code should be quit eclear, providing you have read the entire article that precedes it.
+Everything else in this code should be quite clear, providing you have read the entire article that precedes it.
 
 It is a classical example of the adage that programming requires a lot of thought and only a little coding.
 Once we have thought through every tiny detail, the code almost writes itself.
diff --git a/documentation/content/en/books/accessibility/development/_index.adoc b/documentation/content/en/books/accessibility/development/_index.adoc
index aeebad3d22..52acdb4829 100644
--- a/documentation/content/en/books/accessibility/development/_index.adoc
+++ b/documentation/content/en/books/accessibility/development/_index.adoc
@@ -188,5 +188,5 @@ To install it, run:
 ....
 
 For detailed usage and features, refer to man:accerciser[1].
-Additional documentation is available in the https://gitlab.gnome.org/GNOME/accerciser/-/blob/master/README.md[REAMDE.md]
+Additional documentation is available in the https://gitlab.gnome.org/GNOME/accerciser/-/blob/master/README.md[README.md]
 and the https://help.gnome.org/users/accerciser/stable/index.html.en[Accerciser User Guide].
diff --git a/documentation/content/en/books/accessibility/lowvision/_index.adoc b/documentation/content/en/books/accessibility/lowvision/_index.adoc
index 9ecf8324d8..8b886c79ff 100644
--- a/documentation/content/en/books/accessibility/lowvision/_index.adoc
+++ b/documentation/content/en/books/accessibility/lowvision/_index.adoc
@@ -336,7 +336,7 @@ Interaction is keyboard-driven, refer to man:xzoom[1] for available commands and
 == Mouse
 
 [[mouse-apparance]]
-=== Apparance
+=== Appearance
 
 Some desktop environments allow you to change the size, color, and other graphical properties of the mouse cursor.
 
@@ -378,7 +378,7 @@ Some themes, included the _Default_, do not support cursor size customization.
 ====
 
 Alternatively, you can achieve the same result via the `xfconf-query` command.
-The following example set the current theme cursur to size 50:
+The following example sets the current theme cursor to size 50:
 
 [source,shell]
 ....
@@ -388,7 +388,7 @@ The following example set the current theme cursur to size 50:
 [[find-mouse-cursor]]
 === Find Cursor
 
-Some desktop environments provide a visul feedback of the mouse pointer's current position.
+Some desktop environments provide visual feedback of the mouse pointer's current position.
 
 [[kde-find-mouse-cursor]]
 ==== KDE Plasma
diff --git a/documentation/content/en/books/design-44bsd/_index.adoc b/documentation/content/en/books/design-44bsd/_index.adoc
index 989fa3c67f..7a851b5bfb 100644
--- a/documentation/content/en/books/design-44bsd/_index.adoc
+++ b/documentation/content/en/books/design-44bsd/_index.adoc
@@ -845,7 +845,7 @@ When the login validation is successful, a login shell is created from which the
 
 [[biblio-cheriton]] Cheriton, 1988 The V Distributed System D. R.Cheriton 314-333 Comm ACM, 31, 3 March 1988
 
-[[biblio-ewens]] Ewens et al, 1985 Tunis: A Distributed Multiprocessor Operating System P.Ewens D. R.Blythe M.Funkenhauser R. C.Holt 247-254 USENIX Assocation Conference Proceedings USENIX Association June 1985
+[[biblio-ewens]] Ewens et al, 1985 Tunis: A Distributed Multiprocessor Operating System P.Ewens D. R.Blythe M.Funkenhauser R. C.Holt 247-254 USENIX Association Conference Proceedings USENIX Association June 1985
 
 [[biblio-gingell]] Gingell et al, 1987 Virtual Memory Architecture in SunOS R.Gingell J.Moran W.Shannon 81-94 USENIX Association Conference Proceedings USENIX Association June 1987
 
@@ -853,7 +853,7 @@ When the login validation is successful, a login shell is created from which the
 
 [[biblio-macklem]] Macklem, 1994 The 4.4BSD NFS Implementation R.Macklem 6:1-14 4.4BSD System Manager's Manual O'Reilly & Associates, Inc. Sebastopol CA 1994
 
-[[biblio-mckusick-2]] McKusick & Karels, 1988 Design of a General Purpose Memory Allocator for the 4.3BSD UNIX Kernel M. K.McKusick M. J.Karels 295-304 USENIX Assocation Conference Proceedings USENIX Assocation June 1998
+[[biblio-mckusick-2]] McKusick & Karels, 1988 Design of a General Purpose Memory Allocator for the 4.3BSD UNIX Kernel M. K.McKusick M. J.Karels 295-304 USENIX Association Conference Proceedings USENIX Association June 1998
 
 [[biblio-mckusick-1]] McKusick et al, 1994 Berkeley Software Architecture Manual, 4.4BSD Edition M. K.McKusick M. J.Karels S. J.Leffler W. N.Joy R. S.Faber 5:1-42 4.4BSD Programmer's Supplementary Documents O'Reilly & Associates, Inc. Sebastopol CA 1994
 
diff --git a/documentation/content/en/books/developers-handbook/ipv6/_index.adoc b/documentation/content/en/books/developers-handbook/ipv6/_index.adoc
index 09286a23b3..aa4a4f50ab 100644
--- a/documentation/content/en/books/developers-handbook/ipv6/_index.adoc
+++ b/documentation/content/en/books/developers-handbook/ipv6/_index.adoc
@@ -425,8 +425,8 @@ To name a few:
 If we would like to support jumbogram properly, the field must be expanded to hold 4G + IPv6 header + link-layer header.
 Therefore, it must be expanded to at least int64_t (u_int32_t is NOT enough).
 
-* We mistakingly use "int" to hold packet length in many places. We need to convert them into larger integral type. It needs a great care, as we may experience overflow during packet length computation.
-* We mistakingly check for ip6_plen field of IPv6 header for packet payload length in various places. We should be checking mbuf pkthdr.len instead. ip6_input() will perform sanity check on jumbo payload option on input, and we can safely use mbuf pkthdr.len afterwards.
+* We mistakenly use "int" to hold packet length in many places. We need to convert them into larger integral type. It needs a great care, as we may experience overflow during packet length computation.
+* We mistakenly check for ip6_plen field of IPv6 header for packet payload length in various places. We should be checking mbuf pkthdr.len instead. ip6_input() will perform sanity check on jumbo payload option on input, and we can safely use mbuf pkthdr.len afterwards.
 * TCP code needs a careful update in bunch of places, of course.
 
 ==== Loop Prevention in Header Processing
@@ -665,7 +665,7 @@ As an userland programmer, the most portable way of dealing with it is to:
 Now following two items are required to be supported by standard drivers:
 
 . mbuf clustering requirement. In this stable release, we changed MINCLSIZE into MHLEN+1 for all the operating systems in order to make all the drivers behave as we expect.
-. multicast. If man:ifmcstat[8] yields no multicast group for a interface, that interface has to be patched.
+. multicast. If man:ifmcstat[8] yields no multicast group for an interface, that interface has to be patched.
 
 If any of the drivers do not support the requirements, then the drivers cannot be used for IPv6 and/or IPsec communication.
 If you find any problem with your card using IPv6/IPsec, then, please report it to the {freebsd-bugs}.
diff --git a/documentation/content/en/books/developers-handbook/testing/_index.adoc b/documentation/content/en/books/developers-handbook/testing/_index.adoc
index 8c6047f059..9ed0c55283 100644
--- a/documentation/content/en/books/developers-handbook/testing/_index.adoc
+++ b/documentation/content/en/books/developers-handbook/testing/_index.adoc
@@ -79,7 +79,7 @@ If the system must be connected to a public network, watch out for spikes of bro
 * Put each file system on its own disk. This minimizes jitter from head-seek optimizations.
 * Minimize output to serial or VGA consoles. Running output into files gives less jitter. (Serial consoles easily become a bottleneck.) Do not touch keyboard while the test is running, even kbd:[space] or kbd:[back-space] shows up in the numbers.
 * Make sure the test is long enough, but not too long. If the test is too short, timestamping is a problem. If it is too long temperature changes and drift will affect the frequency of the quartz crystals in the computer. Rule of thumb: more than a minute, less than an hour.
-* Try to keep the temperature as stable as possible around the machine. This affects both quartz crystals and disk drive algorithms. To get real stable clock, consider stabilized clock injection. E.g., get a OCXO + PLL, inject output into clock circuits instead of motherboard xtal. Contact {phk} for more information about this.
+* Try to keep the temperature as stable as possible around the machine. This affects both quartz crystals and disk drive algorithms. To get real stable clock, consider stabilized clock injection. E.g., get an OCXO + PLL, inject output into clock circuits instead of motherboard xtal. Contact {phk} for more information about this.
 * Run the test at least 3 times but it is better to run more than 20 times both for "before" and "after" code. Try to interleave if possible (i.e.: do not run 20 times before then 20 times after), this makes it possible to spot environmental effects. Do not interleave 1:1, but 3:3, this makes it possible to spot interaction effects.
 +
 A good pattern is: `bababa{bbbaaa}*`.
diff --git a/documentation/content/en/books/handbook/config/_index.adoc b/documentation/content/en/books/handbook/config/_index.adoc
index 20db96e7dc..22482b80b5 100644
--- a/documentation/content/en/books/handbook/config/_index.adoc
+++ b/documentation/content/en/books/handbook/config/_index.adoc
@@ -1416,7 +1416,7 @@ Graphics cards have become a fundamental part of computing in recent years.
 Some graphics cards may have excessive power consumption.
 FreeBSD allows certain configurations to improve power consumption.
 
-In case of using a Intel(R) graphics card with the package:graphics/drm-kmod[] driver these options can be added to [.filename]#/boot/loader.conf#:
+In case of using an Intel(R) graphics card with the package:graphics/drm-kmod[] driver these options can be added to [.filename]#/boot/loader.conf#:
 
 [.programlisting]
 ....
diff --git a/documentation/content/en/books/handbook/desktop/_index.adoc b/documentation/content/en/books/handbook/desktop/_index.adoc
index b24ec3793b..6db52b6130 100644
--- a/documentation/content/en/books/handbook/desktop/_index.adoc
+++ b/documentation/content/en/books/handbook/desktop/_index.adoc
@@ -101,7 +101,7 @@ A desktop environment can range from a simple window manager to a complete suite
 [[kde-environment]]
 === Plasma
 
-Plasma is a easy-to-use desktop environment made by the KDE community.
+Plasma is an easy-to-use desktop environment made by the KDE community.
 This desktop provides a suite of applications with a consistent look and feel, a standardized menu and toolbars, keybindings, color-schemes, internationalization, and a centralized, dialog-driven desktop configuration.
 
 More information on Plasma can be found at the link:https://kde.org/plasma-desktop[Plasma homepage].
diff --git a/documentation/content/en/books/handbook/virtualization/_index.adoc b/documentation/content/en/books/handbook/virtualization/_index.adoc
index d4cfec6839..c725defa9a 100644
--- a/documentation/content/en/books/handbook/virtualization/_index.adoc
+++ b/documentation/content/en/books/handbook/virtualization/_index.adoc
@@ -1166,7 +1166,7 @@ QEMU 9.0.1 monitor - type 'help' for more information
 Next, in the main console window, install a package, such as man:zip[1] which has no dependencies.
 Once that completes, renter the monitor and create another snapshot (`snap1_pkg+zip`).
 
-crossref:virtualization[qemu-after-monitor-snapshots,Figure {counter:figure}] shows the results of the above commands and the output of the `info shapshots` command.
+crossref:virtualization[qemu-after-monitor-snapshots,Figure {counter:figure}] shows the results of the above commands and the output of the `info snapshots` command.
 
 [[qemu-after-monitor-snapshots]]
 .QEMU Using Monitor Commands for Snapshots
diff --git a/documentation/content/en/books/handbook/wayland/_index.adoc b/documentation/content/en/books/handbook/wayland/_index.adoc
index d9e78df6b1..475995403c 100644
--- a/documentation/content/en/books/handbook/wayland/_index.adoc
+++ b/documentation/content/en/books/handbook/wayland/_index.adoc
@@ -143,7 +143,7 @@ It is recommended that an alias be configured for each compositor to load the de
 ====
 It has been reported that ZFS users may experience issues with some Wayland clients because they need access to `posix_fallocate()` in the runtime directory.
 While the author could not reproduce this issue on their ZFS system, a recommended workaround is not to use ZFS for the runtime directory and instead use `tmpfs` for the [.filename]#/var/run# directory.
-In this case, the `tmpfs` file system is used for [.filename]#/var/run# and mounted through the command `mount -t tmpfs tmpfs /var/run` command and then make this change persist across reboots through [.filename]#/etc/fstab#.
+In this case, the `tmpfs` file system is used for [.filename]#/var/run# and mounted through the command `mount -t tmpfs tmpfs /var/run` and then make this change persist across reboots through [.filename]#/etc/fstab#.
 The XDG_RUNTIME_DIR environment variable could be configured to use [.filename]#/var/run/user/$UID# and avoid potential pitfalls with ZFS.
 Consider that scenario when reviewing the configuration examples in the following sections.
 ====
diff --git a/documentation/content/en/books/handbook/wine/_index.adoc b/documentation/content/en/books/handbook/wine/_index.adoc
index b01e1c4580..47e6b13620 100644
--- a/documentation/content/en/books/handbook/wine/_index.adoc
+++ b/documentation/content/en/books/handbook/wine/_index.adoc
@@ -191,7 +191,7 @@ For FreeBSD users, some alternatives to using WINE are as follows:
 WINE can be installed via the pkg tool, or by compiling the port(s).
 
 [[wine-prerequistes]]
-=== WINE Prerequistes
+=== WINE Prerequisites
 
 Before installing WINE itself, it is useful to have the following pre-requisites installed.
 
diff --git a/documentation/content/en/books/porters-handbook/makefiles/_index.adoc b/documentation/content/en/books/porters-handbook/makefiles/_index.adoc
index 72aa3c5f0a..dff50499cd 100644
--- a/documentation/content/en/books/porters-handbook/makefiles/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/makefiles/_index.adoc
@@ -1589,7 +1589,7 @@ GH_TAGNAME=	c472d66b70dd603bf9e67607f0869639276796ce
 ....
 
 This creates a versioning scheme that increases over time, and that is still before version `0`.
-See crossref:makefiles[makefile-versions-ex-pkg-version, this secion on how to compare versions] using man:pkg-version[8]:
+See crossref:makefiles[makefile-versions-ex-pkg-version, this section on how to compare versions] using man:pkg-version[8]:
 
 [source,shell]
 ....
diff --git a/documentation/content/en/books/porters-handbook/special/_index.adoc b/documentation/content/en/books/porters-handbook/special/_index.adoc
index e6eb036783..940b318645 100644
--- a/documentation/content/en/books/porters-handbook/special/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/special/_index.adoc
@@ -4961,7 +4961,7 @@ The package:devel/rclint[] port can check for most of these, but it is not a sub
 [.procedure]
 . If this is a new file, does it have a [.filename]#.sh# extension? If so, that must be changed to just [.filename]#file.in# since [.filename]#rc.d# files may not end with that extension.
 . Do the name of the file (minus [.filename]#.in#), the `PROVIDE` line, and `$` _name_ all match? The file name matching `PROVIDE` makes debugging easier, especially for man:rcorder[8] issues. Matching the file name and `$`_name_ makes it easier to figure out which variables are relevant in [.filename]#rc.conf[.local]#. It is also a policy for all new scripts, including those in the base system.
-. Is the `REQUIRE` line set to `LOGIN`? This is mandatory for scripts that run as a non-root user. If it runs as root, is there a good reason for it to run prior to `LOGIN`? If not, it must run after so that local scrips can be loosely grouped to a point in man:rcorder[8] after most everything in the base is already running.
+. Is the `REQUIRE` line set to `LOGIN`? This is mandatory for scripts that run as a non-root user. If it runs as root, is there a good reason for it to run prior to `LOGIN`? If not, it must run after so that local scripts can be loosely grouped to a point in man:rcorder[8] after most everything in the base is already running.
 . Does the script start a persistent service? If so, it must have `KEYWORD: shutdown`.
 . Make sure there is no `KEYWORD: FreeBSD` present. This has not been necessary nor desirable for years. It is also an indication that the new script was copy/pasted from an old script, so extra caution must be given to the review.
 . If the script uses an interpreted language like `perl`, `python`, or `ruby`, make certain that `command_interpreter` is set appropriately, for example, for Perl, by adding `PERL=${PERL}` to `SUB_LIST` and using `%%PERL%%`. Otherwise,
diff --git a/documentation/content/en/books/porters-handbook/uses/_index.adoc b/documentation/content/en/books/porters-handbook/uses/_index.adoc
index e30285d720..6754b4749d 100644
--- a/documentation/content/en/books/porters-handbook/uses/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/uses/_index.adoc
@@ -2800,7 +2800,7 @@ BROKEN_SSL_REASON_libressl=	needs features only available in OpenSSL
 
 Possible arguments: (none)
 
-Adds a run time dependecy on package:security/sudo[].
+Adds a run time dependency on package:security/sudo[].
 
 [[uses-tar]]
 == `tar`
diff --git a/website/content/en/applications.adoc b/website/content/en/applications.adoc
index a4e9a4478a..2da30872c4 100644
--- a/website/content/en/applications.adoc
+++ b/website/content/en/applications.adoc
@@ -23,7 +23,7 @@ Here are some examples of the environments in which FreeBSD is used:
 
 * *Internet services.* Many Internet Service Providers (ISPs) find FreeBSD ideal, running WWW, Usenet news, FTP, Email, and other services. Ready-to-run software like the http://nginx.org[NGINX] or http://www.apache.org/[Apache] web server or the http://proftpd.org/[ProFTPD] or http://security.appspot.com/vsftpd.html[vsftpd] FTP server make it easy to set up a business or community-centered ISP. Of course, with FreeBSD's unbeatable link:../internet/[networking], your users will enjoy high speed, reliable services.
 * *X Window workstation.* From an inexpensive X terminal to an advanced X display, FreeBSD works quite well. Free X software (https://x.org/[X.Org](T)) comes with the system. https://www.nvidia.com/[NVIDIA] offers native drivers for their high-performance graphics hardware, and the industry standard https://www.opengroup.org/motif/[Motif](R) and https://www.opengl.org/[OpenGL](R) libraries are supported. The https://xfce.org/[Xfce] and https://lxde.org/[LXDE] products provide a desktop environment. The https://www.kde.org[KDE] and https://www.gnome.org[GNOME] desktop environments also enjoy full support and provide office suite functionality, with further good functionality available in the https://www.libreoffice.org/[LibreOffice] and https://www.openoffice.org/[OpenOffice.Org] products.
-* *Networking.* From packet filtering to routing to name service, FreeBSD can turn any PC into a Internet firewall, email host, print server, PC/NFS server, and more.
+* *Networking.* From packet filtering to routing to name service, FreeBSD can turn any PC into an Internet firewall, email host, print server, PC/NFS server, and more.
 * *Software development.* A suite of https://docs.freebsd.org/en/books/developers-handbook/tools/[development tools] comes with FreeBSD, including the LLVM-based clang C/C++ compiler and debugger. Java(R) and Tcl/Tk development are also possible for example. And FreeBSD's shared libraries have always been easy to make and use. You can also choose from a wide range of popular and powerful editors, such as Emacs and Vim.
 * *Net surfing.* A real UNIX workstation makes a great Internet surfboard. FreeBSD versions of http://www.chromium.org/Home[Chromium] and http://www.mozilla.org/firefox/[Firefox] are available for serious web users. Surf the web, publish your own web pages, read Usenet news, and send and receive email with a FreeBSD system on your desktop.
 * *Education and research.* FreeBSD makes an excellent research platform because it includes complete source code. Students and researchers of operating systems or other computer science fields can benefit greatly from such an open and well-documented system.
diff --git a/website/content/en/internal/clusteradm.adoc b/website/content/en/internal/clusteradm.adoc
index e4e8feab3e..3c69c86240 100644
--- a/website/content/en/internal/clusteradm.adoc
+++ b/website/content/en/internal/clusteradm.adoc
@@ -15,7 +15,7 @@ Lead cluster administrator is a delegated officer role (aka. "hat") that answers
 * Take measures to ensure that a competent administrator would be expected to be able to adopt a predecessor's work in a reasonable amount of time.
 * Contingency planning and implementation to ensure continuity across site specific problems (including donated site withdrawal or outages).
 * Keep the interested parties (Core Team, Security Team, FreeBSD Foundation, Ports Management Team, etc), project members and community members appropriately informed.
-* Give timely and authoritive answers to questions, or a direct referral to the appropriate party.
+* Give timely and authoritative answers to questions, or a direct referral to the appropriate party.
 * Aid other hat wearers and cluster administrators to get their job done.
 * Where practical and appropriate, use the Project's own product as a proving ground.
 * Make sure that it is easy for developers to know what hardware resources they have access to for project purposes.
diff --git a/website/content/en/internal/working-with-hats.adoc b/website/content/en/internal/working-with-hats.adoc
index 44eb069179..c2060cf31e 100644
--- a/website/content/en/internal/working-with-hats.adoc
+++ b/website/content/en/internal/working-with-hats.adoc
@@ -11,7 +11,7 @@ include::shared/authors.adoc[]
 
 This is not an official statement from core, but rather one core member's personal interpretation of core's position, both as a sitting member of core and as a former security officer. This is only a guideline, not as a cudgel for grievances. Much like style(9) is a guideline for the source code, this document is not intended as an absolute straight jacket.
 
-When core appoints someone to a hat, they expect that person to be responsible for an area of the source code tree. Core expects that person to be the final authority in that area of the tree, or have enough self knowledge to know that they are not and to seek qualified help. Core expects that person to guide development in that area of the tree. Sometimes this means taking an pro-active role in day to day affairs, while other times this means taking a reactive role in reviewing committed code.
+When core appoints someone to a hat, they expect that person to be responsible for an area of the source code tree. Core expects that person to be the final authority in that area of the tree, or have enough self knowledge to know that they are not and to seek qualified help. Core expects that person to guide development in that area of the tree. Sometimes this means taking a pro-active role in day to day affairs, while other times this means taking a reactive role in reviewing committed code.
 
 When people submit patches that potentially impact this area of the tree, core expects the hat or his appointed deputies to review the patches appropriately. Core expects that the hat will work with the patch submitter to correct issues that there may be with the patches. Core expects the hat to offer solutions and work with the submitter to reach a compromise. Core expects the hat to be courteous. It is reasonable for hats to request that normal project rules be followed when reviewing patches (for example, that they generally conform to style(9) or the prevailing style of the file, that style and content changes be separated.).
 
diff --git a/website/content/en/platforms/ppc.adoc b/website/content/en/platforms/ppc.adoc
index ad357d0b75..5c17e969a9 100644
--- a/website/content/en/platforms/ppc.adoc
+++ b/website/content/en/platforms/ppc.adoc
@@ -37,7 +37,7 @@ The most up-to-date information about supported hardware is currently being main
 == Latest News
 
 * *13 Apr, 2021*: FreeBSD 13.0 was released introducing new target powerpc64le and LLVM as main compiler. Supports disk, network and video controller drivers for modern POWER machines from Raptor Computing (Blackbird and Talos II) and IBM (LC922 and IC922). https://www.freebsd.org/releases/13.0R/relnotes/[Release Notes]
-* *22 Sep, 2020*: new target powerpc64le (64-bit little endian) was introduced targetting POWER8 and newer processors.
+* *22 Sep, 2020*: new target powerpc64le (64-bit little endian) was introduced targeting POWER8 and newer processors.
 * *29 Dec, 2019*: Release 13.0 for powerpc, powerpcspe and powerpc64 targets will replace GCC4 by LLVM compiler and powerpc64 will use the modern OpenPower 64-Bit ELF V2 ABI Specification.
 * *05 May, 2019*: FreeBSD has been tested and seems to work on the https://wiki.freebsd.org/powerpc/Raptor/Blackbird[Raptor Blackbird].
 
@@ -67,7 +67,7 @@ Refer to the Handbook: link:{handbook}ports#ports-using[use the Ports Collection
 
 * 64-bit
 
-** *Users of 64-bit bi-endian CPUs POWER8 and POWER9*: can choose between FreeBSD/powerpc64 and FreeBSD/powerpc64le (big endian and little endian, respectively). The FreeBSD/powerpc64 (big endian) also supports running 32-bit binaries nativelly like other 64-bit platforms.
+** *Users of 64-bit bi-endian CPUs POWER8 and POWER9*: can choose between FreeBSD/powerpc64 and FreeBSD/powerpc64le (big endian and little endian, respectively). The FreeBSD/powerpc64 (big endian) also supports running 32-bit binaries natively like other 64-bit platforms.
 ** *Users of 64-bit big endian CPUs Apple G5 and POWER7*: FreeBSD/powerpc64 should be installed. Apple G5 users also have a choice of using the 32-bit FreeBSD/powerpc but FreeBSD/powerpc64 provides ZFS support and the ability of use more than 2 GB of RAM.
 
 * 32-bit
diff --git a/website/content/en/search/opensearch/_index.adoc b/website/content/en/search/opensearch/_index.adoc
index 0ba9adf841..505b510a9b 100644
--- a/website/content/en/search/opensearch/_index.adoc
+++ b/website/content/en/search/opensearch/_index.adoc
@@ -5,7 +5,7 @@ sidenav: about
 
 = FreeBSD OpenSearch Plugins
 
-Firefox put a few popular search sites in the Search Bar in the upper-right corner of Firefox. Click on a item to add the _FreeBSD Search Services_ to your Firefox Search Bar.
+Firefox put a few popular search sites in the Search Bar in the upper-right corner of Firefox. Click on an item to add the _FreeBSD Search Services_ to your Firefox Search Bar.
 
 == By the FreeBSD.org web site
 
diff --git a/website/content/en/srcmgr/charter.adoc b/website/content/en/srcmgr/charter.adoc
index 2605480850..2bfed49c0c 100644
--- a/website/content/en/srcmgr/charter.adoc
+++ b/website/content/en/srcmgr/charter.adoc
@@ -16,7 +16,7 @@ To support this goal, the srcmgr team has the following responsibilities (_Inlin
 * Approve new and returning commit bits for the source repositories.
 * Reclaim idle commit bits for the source repositories.
 * Define and manage recruiting activities for both new committers and mentors.
-  _This includes identifing active contributors who are not yet committers and soliciting mentors for new contributors from existing committers. We can manage any subcomittee that does the recruiting._
+  _This includes identifying active contributors who are not yet committers and soliciting mentors for new contributors from existing committers. We can manage any subcommittee that does the recruiting._
 * Arbitrate disputes related to the source repository between FreeBSD community members.
 * Define and encourage healthy norms for interactions between committers and external contributors.
   _For example, guidelines and best practices for reviewing patches and working with bugmeister@ to develop source-specific bug triage workflows._
diff --git a/website/content/en/usergroups/_index.adoc b/website/content/en/usergroups/_index.adoc
index e6701e482f..c0d8c80101 100644
--- a/website/content/en/usergroups/_index.adoc
+++ b/website/content/en/usergroups/_index.adoc
@@ -92,7 +92,7 @@ Feel free to visit our regular meetings (every four weeks) or join the mailing l
 For more information visit the link:http://bse.42.org/[BSE web site].
 
 link:http://www.fug-fr.org/[FUG-FR]::
-The FreeBSD User Group France (FUG-FR) is an group of FreeBSD enthusiasts in France currently involved translating marketing papers etc.
+The FreeBSD User Group France (FUG-FR) is a group of FreeBSD enthusiasts in France currently involved translating marketing papers etc.
 They are also active in helping out FOSDEM (held in Brussels).
 For more information please visit our web page link:http://www.fug-fr.org/[http://www.fug-fr.org] or contact link:mailto:rodrigo@bebik.net[Rodrigo Osorio].
 
@@ -104,7 +104,7 @@ For more information please visit our link:https://www.meetup.com/Dublin-BSD-Use
 link:http://www.lissyara.su[Lissyara.su]::
 We are a Russian FreeBSD community.
 On our site we offer several articles for setting up FreeBSD and various other applications.
-In addtition to the articles we also provide a link:http://forum.lissyara.su/[user forum] where experienced users of FreeBSD are pleased to be able to help other users.
+In addition to the articles we also provide a link:http://forum.lissyara.su/[user forum] where experienced users of FreeBSD are pleased to be able to help other users.
 
 link:http://bsdportal.ru[Russian FreeBSD User Group (RFUG)]::
 The Russian FreeBSD User Group (RFUG) is a Russian language oriented user group for the Russian and ex-USSR users.