src/: fix formatting via vmdfmt.

Author: ericonr

src/config/kernel.md

@@ -82,9 +82,10 @@ initramfs.
 ## Kernel hardening
 
 Void Linux ships with some kernel security options enabled by default. This was
-originally provided by kernel command line arguments `slub_debug=P page_poison=1`,
-but since kernel series 5.3, these have been replaced with `init_on_alloc` and
-`init_on_free` (see [this commit](https://github.com/torvalds/linux/commit/6471384af)).
+originally provided by kernel command line arguments `slub_debug=P
+page_poison=1`, but since kernel series 5.3, these have been replaced with
+`init_on_alloc` and `init_on_free` (see [this
+commit](https://github.com/torvalds/linux/commit/6471384af)).
 
 Void's kernels come with the `init_on_alloc` option enabled by default where
 available (i.e. `linux5.4` and greater). In most cases you should usually not
@@ -97,8 +98,8 @@ need to disable `init_on_alloc`, you can do that similarly by passing
 There is a chance that your existing system still has the old options enabled.
 They still work in newer kernels, but have a performance impact more in line
 with `init_on_free=1`. On older hardware this can be quite noticeable. If you
-are running a kernel series older than 5.4, you can keep them (or add them)
-for extra security at the cost of speed; otherwise you should remove them.
+are running a kernel series older than 5.4, you can keep them (or add them) for
+extra security at the cost of speed; otherwise you should remove them.
 
 ## Kernel modules
 

src/installation/index.md

@@ -38,19 +38,19 @@ date.
 ### Verifying images
 
 Each image release's directory contains two files used to verify the image(s)
-you download. First, there is a `sha256sum.txt` file containing image checksums to
-verify the integrity of the downloaded images. Second is the `sha256sum.sig` file,
-used to verify the authenticity of the checksums.
+you download. First, there is a `sha256sum.txt` file containing image checksums
+to verify the integrity of the downloaded images. Second is the `sha256sum.sig`
+file, used to verify the authenticity of the checksums.
 
 It is necessary to verify both the image's integrity and authenticity. It is,
 therefore, recommended that you download both files.
 
 #### Verifying image integrity
 
 You can verify the integrity of a downloaded file using
-[sha256sum(1)](https://man.voidlinux.org/sha256sum.1) with the `sha256sum.txt` file
-downloaded above. The following command will check the integrity of only the
-image(s) you have downloaded:
+[sha256sum(1)](https://man.voidlinux.org/sha256sum.1) with the `sha256sum.txt`
+file downloaded above. The following command will check the integrity of only
+the image(s) you have downloaded:
 
 ```
 $ sha256sum -c --ignore-missing sha256sum.txt
@@ -104,9 +104,9 @@ use it! Please alert the Void Linux team of where you got the image and how you
 verified it, and we will follow up on it.
 
 For verification with `minisign`, it is necessary to rename the `sha256sum.sig`
-file to `sha256sum.txt.minisig` and remove the first line from the `.pub` release
-key. The following example demonstrates the verification of the `sha256sum.txt`
-file from the 20191109 release:
+file to `sha256sum.txt.minisig` and remove the first line from the `.pub`
+release key. The following example demonstrates the verification of the
+`sha256sum.txt` file from the 20191109 release:
 
 ```
 $ minisign -Vm sha256sum.txt -f -p void-release-20191109.pub