aboutsummaryrefslogtreecommitdiff
path: root/documentation/content/en/articles/remote-install/_index.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/content/en/articles/remote-install/_index.adoc')
-rw-r--r--documentation/content/en/articles/remote-install/_index.adoc10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/content/en/articles/remote-install/_index.adoc b/documentation/content/en/articles/remote-install/_index.adoc
index f1bd16bb37..9efc5e4165 100644
--- a/documentation/content/en/articles/remote-install/_index.adoc
+++ b/documentation/content/en/articles/remote-install/_index.adoc
@@ -70,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.
@@ -261,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.
@@ -297,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]
@@ -315,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]