1 files changed, 3 insertions, 3 deletions

diff --git a/documentation/content/en/books/handbook/geom/_index.adoc b/documentation/content/en/books/handbook/geom/_index.adoc
index d0667b683f..b220487080 100644
--- a/documentation/content/en/books/handbook/geom/_index.adoc
+++ b/documentation/content/en/books/handbook/geom/_index.adoc
@@ -247,7 +247,7 @@ Create the mirror with the two new drives:
 After the mirror has been started, this device name appears in [.filename]#/dev/mirror/#.
 
 MBR and bsdlabel partition tables can now be created on the mirror with man:gpart[8].
-This example uses a traditional file system layout, with partitions for [.filename]#/#, swap, [.filename]#/var#, [.filename]#/tmp#, and [.filename]#/usr#. 
+This example uses a traditional file system layout, with partitions for [.filename]#/#, swap, [.filename]#/var#, [.filename]#/tmp#, and [.filename]#/usr#.
 A single [.filename]#/# and a swap partition will also work.
 
 Partitions on the mirror do not have to be the same size as those on the existing disk, but they must be large enough to hold all the data already present on [.filename]#ada0#.
@@ -555,7 +555,7 @@ Each file system dumped with `dump -L` will create a snapshot first, which can t
 ....
 
 Restart the system, booting from [.filename]#ada1#.
-If everything is working, the system will boot from [.filename]#mirror/gm0#, which now contains the same data as [.filename]#ada0# had previously. 
+If everything is working, the system will boot from [.filename]#mirror/gm0#, which now contains the same data as [.filename]#ada0# had previously.
 See <<gmirror-troubleshooting>> if there are problems booting.
 
 At this point, the mirror still consists of only the single [.filename]#ada1# disk.
@@ -1297,7 +1297,7 @@ For instance, if [.filename]#ad4s1# and [.filename]#ad4s2# are both slices, then
 
 Journaling may also be enabled on current file systems by using `tunefs`.
 However, _always_ make a backup before attempting to alter an existing file system.
-In most cases, `gjournal` will fail if it is unable to create the journal, but this does not protect against data loss incurred as a result of misusing `tunefs`. 
+In most cases, `gjournal` will fail if it is unable to create the journal, but this does not protect against data loss incurred as a result of misusing `tunefs`.
 Refer to man:gjournal[8] and man:tunefs[8] for more information about these commands.
 
 It is possible to journal the boot disk of a FreeBSD system.