1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/content/en/articles/gjournal-desktop/_index.adoc b/documentation/content/en/articles/gjournal-desktop/_index.adoc
index 1f8c15f843..164c92985b 100644
--- a/documentation/content/en/articles/gjournal-desktop/_index.adoc
+++ b/documentation/content/en/articles/gjournal-desktop/_index.adoc
@@ -61,7 +61,7 @@ On rare occasions, file system corruption reaches a point where user interventio
 
 The new journaling capability provided by GEOM can greatly assist in such scenarios, by virtually eliminating the time required for file system checking, and ensuring that the file system is quickly restored to a consistent state.
 
-This article describes a procedure for implementing UFS journaling on a typical desktop PC scenario (one hard disk used for both operating system and data). 
+This article describes a procedure for implementing UFS journaling on a typical desktop PC scenario (one hard disk used for both operating system and data).
 It should be followed during a fresh installation of FreeBSD.
 The steps are simple enough and do not require overly complex interaction with the command line.
 
@@ -106,14 +106,14 @@ For example:
 * You reserved some free disk space in a partition in [.filename]#/dev/ad0s1g#.
 * Using `gjournal`, a new [.filename]#/dev/ad0s1f.journal# device is created where [.filename]#/dev/ad0s1f# is the data provider, and [.filename]#/dev/ad0s1g# is the journal provider. This new device is then used for all subsequent file operations.
 
-The amount of disk space you need to reserve for the journal provider depends on the usage load of the file system and not on the size of the data provider. 
+The amount of disk space you need to reserve for the journal provider depends on the usage load of the file system and not on the size of the data provider.
 For example on a typical office desktop, a 1 GB journal provider for the [.filename]#/usr# file system will suffice, while a machine that deals with heavy disk I/O (i.e. video editing) may need more.
 A kernel panic will occur if the journal space is exhausted before it has a chance to be committed.
 
 [NOTE]
 ====
 The journal sizes suggested here, are highly unlikely to cause problems in typical desktop use (such as web browsing, word processing and playback of media files).
-If your workload includes intense disk activity, use the following rule for maximum reliability: Your RAM size should fit in 30% of the journal provider's space. 
+If your workload includes intense disk activity, use the following rule for maximum reliability: Your RAM size should fit in 30% of the journal provider's space.
 For example, if your system has 1 GB RAM, create an approximately 3.3 GB journal provider.
 (Multiply your RAM size with 3.3 to obtain the size of the journal).
 ====
@@ -197,7 +197,7 @@ We would however suggest you postpone installation of third party software (pack
 [[first-boot]]
 === Booting for the first time
 
-Your system will come up normally, but you will need to edit [.filename]#/etc/fstab# and remove the extra swap partitions you created for the journals. 
+Your system will come up normally, but you will need to edit [.filename]#/etc/fstab# and remove the extra swap partitions you created for the journals.
 Normally, the swap partition you will actually use is the one with the "b" suffix (i.e. ad0s1b in our example).
 Remove all other swap space entries and reboot so that FreeBSD will stop using them.
 
@@ -371,7 +371,7 @@ options UFS_GJOURNAL # Note: This is already in GENERIC
 options GEOM_JOURNAL # You will have to add this one
 ....
 
-Rebuild and reinstall your kernel following the relevant extref:{handbook}[instructions in the FreeBSD Handbook., kernelconfig]
+Rebuild and reinstall your kernel following the relevant extref:{handbook}kernelconfig[instructions in the FreeBSD Handbook., kernelconfig]
 
 Do not forget to remove the relevant "load" entry from [.filename]#/boot/loader.conf# if you have previously used it.
 
@@ -504,7 +504,7 @@ Finally, edit [.filename]#/boot/loader.conf#, remove the entry that loads the `g
 Journaling is a fairly new feature of FreeBSD, and as such, it is not very well documented yet.
 You may however find the following additional references useful:
 
-* A extref:{handbook}[new section on journaling, geom-gjournal] is now part of the FreeBSD Handbook.
+* A extref:{handbook}geom[new section on journaling, geom-gjournal] is now part of the FreeBSD Handbook.
 * https://lists.freebsd.org/pipermail/freebsd-current/2006-June/064043.html[This post] in {freebsd-current} by man:gjournal[8]'s developer, `{pjd}`.
 * https://lists.freebsd.org/pipermail/freebsd-questions/2008-April/173501.html[This post] in {freebsd-questions} by `{ivoras}`.
 * The manual pages of man:gjournal[8] and man:geom[8].