1 files changed, 21 insertions, 15 deletions
diff --git a/documentation/content/en/articles/remote-install/_index.adoc b/documentation/content/en/articles/remote-install/_index.adoc
index 5d6a8b5e4a..9efc5e4165 100644
--- a/documentation/content/en/articles/remote-install/_index.adoc
+++ b/documentation/content/en/articles/remote-install/_index.adoc
@@ -18,20 +18,26 @@ tags: ["Remote", "Installation", "FreeBSD"]
 :sectnumlevels: 6
 :source-highlighter: rouge
 :experimental:
+:images-path: articles/remote-install/
 
-ifeval::["{backend}" == "html5"]
+ifdef::env-beastie[]
+ifdef::backend-html5[]
 include::shared/authors.adoc[]
-include::shared/en/urls.adoc[]
+include::shared/mirrors.adoc[]
+include::shared/releases.adoc[]
+include::shared/attributes/attributes-{{% lang %}}.adoc[]
+include::shared/{{% lang %}}/teams.adoc[]
+include::shared/{{% lang %}}/mailing-lists.adoc[]
+include::shared/{{% lang %}}/urls.adoc[]
+:imagesdir: ../../../images/{images-path}
+endif::[]
+ifdef::backend-pdf,backend-epub3[]
+include::../../../../shared/asciidoctor.adoc[]
 endif::[]
-
-ifeval::["{backend}" == "pdf"]
-include::../../../../shared/authors.adoc[]
-include::../../../../shared/en/urls.adoc[]
 endif::[]
 
-ifeval::["{backend}" == "epub3"]
-include::../../../../shared/authors.adoc[]
-include::../../../../shared/en/urls.adoc[]
+ifndef::env-beastie[]
+include::../../../../../shared/asciidoctor.adoc[]
 endif::[]
 
 [.abstract-title]
@@ -64,7 +70,7 @@ The instructions included in this article will benefit those using services prov
 
 [.procedure]
 ====
-. As we have mentioned in the <<background>> section, many of the reputable server hosting companies provide some kind of rescue system, which is booted from their LAN and accessible over SSH. They usually provide this support in order to help their customers fix broken operating systems. As this article will explain, it is possible to install FreeBSD with the help of these rescue systems.
+. As we have mentioned in the <<background>> section, many of the reputable server hosting companies provide some kind of rescue system, which is booted from their LAN and accessible over SSH. They usually provide this support to help their customers fix broken operating systems. As this article will explain, it is possible to install FreeBSD with the help of these rescue systems.
 +
 . The next section of this article will describe how to configure, and build minimalistic FreeBSD on the local machine. That version will eventually be running on the remote machine from a ramdisk, which will allow us to install a complete FreeBSD operating system from an FTP mirror using the sysinstall utility.
 . The rest of this article will describe the installation procedure itself, as well as the configuration of the ZFS file system.
@@ -227,7 +233,7 @@ Repeat the following command for each hard drive:
 
 Next, create slices and label them with your preferred tool.
 While it is considered easier to use `sysinstall`, a powerful and also probably less buggy method will be to use standard text-based UNIX(R) tools, such as man:fdisk[8] and man:bsdlabel[8], which will also be covered in this section.
-The former option is well documented in the link:{handbook}#install-steps[Installing FreeBSD] chapter of the FreeBSD Handbook.
+The former option is well documented in the extref:{handbook}[Installing FreeBSD, install-steps] chapter of the FreeBSD Handbook.
 As it was mentioned in the introduction, this article will present how to set up a system with RAID-1 and ZFS capabilities.
 Our set up will consist of a small man:gmirror[8] mirrored [.filename]#/# (root), [.filename]#/usr# and [.filename]#/var# dataset, and the rest of the disk space will be allocated for a man:zpool[8] mirrored ZFS file system.
 Please note, that the ZFS file system will be configured after the FreeBSD operating system is successfully installed and booted.
@@ -255,7 +261,7 @@ The following example will describe how to create slices and labels, initialize
 
 <.> Write a standard label for each disk including the bootstrap code.
 
-<.> Now, manually edit the label of the given disk. Refer to the man:bsdlabel[8] manual page in order to find out how to create partitions. Create partitions `a` for [.filename]#/# (root) file system, `b` for swap, `d` for [.filename]#/var#, `e` for [.filename]#/usr# and finally `f` which will later be used for ZFS.
+<.> Now, manually edit the label of the given disk. Refer to the man:bsdlabel[8] manual page to find out how to create partitions. Create partitions `a` for [.filename]#/# (root) file system, `b` for swap, `d` for [.filename]#/var#, `e` for [.filename]#/usr# and finally `f` which will later be used for ZFS.
 
 <.> Import the recently created label for the second hard drive, so both hard drives will be labeled in the same way.
 
@@ -291,7 +297,7 @@ Note that this step is very important and if skipped, `sysinstall` will be unabl
 ====
 
 Go to the [.guimenuitem]#Distributions# menu, move the cursor with the arrow keys to `Minimal`, and check it by pressing kbd:[Space].
-This article uses the Minimal distribution in order to save network traffic, because the system itself will be installed over ftp.
+This article uses the Minimal distribution to save network traffic, because the system itself will be installed over ftp.
 Exit this menu by choosing `Exit`.
 
 [NOTE]
@@ -309,9 +315,9 @@ Exit `sysinstall` when it finishes the installation.
 === Post Installation Steps
 
 The FreeBSD operating system should be installed now; however, the process is not finished yet.
-It is necessary to perform some post installation steps in order to allow FreeBSD to boot in the future and to be able to log in to the system.
+It is necessary to perform some post installation steps to allow FreeBSD to boot in the future and to be able to log in to the system.
 
-You must now man:chroot[8] into the freshly installed system in order to finish the installation.
+You must now man:chroot[8] into the freshly installed system to finish the installation.
 Use the following command:
 
 [source,shell]