docs: Fix typos and wording issues

src/config/containers-and-vms/lxc.md

@@ -39,7 +39,7 @@ In each colon-delimited entry:
 - the third field is the number of consecutive IDs in the range.
 
 The [usermod(8)](https://man.voidlinux.org/usermod.8) program may also be used
-to manipulate suborinated IDs.
+to manipulate subordinated IDs.
 
 Generally, the number of consecutive IDs should be an integer multiple of 65536;
 the starting value is not important, except to ensure that the various ranges

src/config/cron.md

@@ -15,8 +15,8 @@ implementations are available, including
 Once you have chosen and installed an implementation,
 [enable](./services/index.md#enabling-services) the corresponding service. There
 is also a generic `crond` service which is maintained by the alternatives
-system, but there is no real benefit in using it and just makes your setup
-harder to follow.
+system, but there is no real benefit in using it because it just makes your
+setup harder to follow.
 
 As an alternative to the standard cron implementations, you can use
 [snooze(1)](https://man.voidlinux.org/snooze.1) together with the

src/config/external-applications.md

@@ -12,7 +12,7 @@ request for it. The contribution instructions can be found
 To keep packages smaller, Void has separate `devel` packages for header files
 and development tools. If you install a library or application via a language's
 package manager (e.g. `pip`, `gem`), or compile one from source, you may need to
-install the programming language's `-devel` package. This is specially relevant
+install the programming language's `-devel` package. This is especially relevant
 for `musl` libc users, due to pre-built binaries usually targeting `glibc`
 instead.
 

src/config/graphical-session/gnome.md

@@ -3,7 +3,7 @@
 ## Pre-installation
 
 GNOME supports both X and Wayland sessions. Follow the "[Wayland](./wayland.md)"
-or "[Xorg](./xorg.md)" sections to setup your preferred environment.
+or "[Xorg](./xorg.md)" sections to set up your preferred environment.
 
 Install the `dbus` package, ensure the `dbus` service is enabled, and reboot for
 the changes to take effect.

src/config/media/index.md

@@ -2,7 +2,7 @@
 
 ## Audio setup
 
-To setup audio on your Void Linux system you have to decide if you want to use
+To set up audio on your Void Linux system you have to decide if you want to use
 [PulseAudio](./pulseaudio.md), [PipeWire](./pipewire.md) or just
 [ALSA](./alsa.md). Sndio is also available, but is neither supported nor
 recommended.

src/config/media/pulseaudio.md

@@ -21,6 +21,6 @@ desired. To inhibit this behavior, the `autospawn` directive from
 [pulse-client.conf(5)](https://man.voidlinux.org/pulse-client.conf.5) can be set
 to `no`.
 
-There are several methods of allowing PulseAudio to access to audio devices. The
+There are several methods of allowing PulseAudio to access audio devices. The
 simplest one is to add your user to the `audio` group. Alternatively, you can
 use a session manager, like `elogind`.

src/config/network/index.md

@@ -27,7 +27,7 @@ ip route add default via 192.168.1.1
 
 To configure bridge interfaces at boot, the `/etc/rc.local` file can be used to
 run [ip(8)](https://man.voidlinux.org/ip.8) commands to add the bridge `br0` and
-set it as the master for the `eth0` interface as example:
+set it as the master for the `eth0` interface, for example:
 
 ```
 ip link add name br0 type bridge

src/config/openpgp.md

@@ -15,7 +15,7 @@ its internal CCID driver. For this to work, your smartcard needs to be one of
 the smartcards in the udev rules
 [here](https://github.com/void-linux/void-packages/blob/master/srcpkgs/gnupg/files/60-scdaemon.rules)
 and you need to either be using elogind or be a member of the plugdev group. If
-these two condition are fulfilled and you don't have pcscd running, `gpg
+these two conditions are fulfilled and you don't have pcscd running, `gpg
 --card-status` should successfully print your current card status.
 
 ## scdaemon with pcscd backend

src/installation/guides/zfs.md

@@ -66,11 +66,10 @@ using [mkswap(8)](https://man.voidlinux.org).
 > It is possible to put Linux swap space on a ZFS zvol, although there may be a
 > risk of deadlocking the kernel when under high memory pressure. This guide
 > takes no position on the matter of swap space on a zvol. However, if you wish
-> to use suspension-to-disk (hibernation), note that the kernel is not capable
-> of resuming from memory images stored on a zvol. You will need a dedicated
-> swap partition to use hibernation. Apart from this caveat, there are no
-> special considerations required to resume a suspended image when using a ZFS
-> root.
+> to use suspend-to-disk (hibernation), note that the kernel is not capable of
+> resuming from memory images stored on a zvol. You will need a dedicated swap
+> partition to use hibernation. Apart from this caveat, there are no special
+> considerations required to resume a suspended image when using a ZFS root.
 
 ### Create a ZFS pool
 

src/xbps/repositories/custom.md

@@ -4,7 +4,7 @@ Void supports user-created repositories, both local and remote. This is only
 recommended for serving custom packages created personally, or packages from
 another trusted source. The Void project does not support *any* third-party
 package repositories - the use of third-party software packages poses very
-serious security concerns, and risks serious damage your system.
+serious security concerns, and risks serious damage to your system.
 
 ## Adding custom repositories
 

src/xbps/troubleshooting/static.md

@@ -5,9 +5,9 @@ longer function. This usually happens while trying to do unsupported things with
 libc, but can also happen when an update contains a corrupt glibc archive or
 otherwise fails to unpack and configure fully.
 
-Another issue that can present itself is in systems with a XBPS version before
+Another issue that can present itself is in systems with an XBPS version before
 `0.54` (released June 2019). These systems will be impossible to update from the
-official repositories using the regular update procedure, due a change in the
+official repositories using the regular update procedure, due to a change in the
 compression format used for repository data, which was made in March 2020.
 
 In these cases it is possible to recover your system with a separate, statically