aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/handbook/geom
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/geom')
-rw-r--r--en_US.ISO8859-1/books/handbook/geom/chapter.xml16
1 files changed, 8 insertions, 8 deletions
diff --git a/en_US.ISO8859-1/books/handbook/geom/chapter.xml b/en_US.ISO8859-1/books/handbook/geom/chapter.xml
index dcb1e12e3c..a682799543 100644
--- a/en_US.ISO8859-1/books/handbook/geom/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/geom/chapter.xml
@@ -331,7 +331,7 @@ Done.</screen>
<screen>&prompt.root; <userinput>gmirror clear ada8</userinput></screen>
<para>&man.gmirror.8; stores one block of metadata at the end of
- the disk. Because <acronym>GPT</acronym> partition schemes
+ the disk. As <acronym>GPT</acronym> partition schemes
also store metadata at the end of the disk, mirroring entire
<acronym>GPT</acronym> disks with &man.gmirror.8; is not
recommended. <acronym>MBR</acronym> partitioning is used here
@@ -451,7 +451,7 @@ Done.</screen>
<para>Reboot the system to test the new mirror and verify that
all data has been copied. The <acronym>BIOS</acronym> will
see the mirror as two individual drives rather than a mirror.
- Because the drives are identical, it does not matter which is
+ Since the drives are identical, it does not matter which is
selected to boot.</para>
<para>See <xref linkend="gmirror-troubleshooting"/> if there are
@@ -1431,12 +1431,12 @@ ggate0
<para>A better solution is to use <command>glabel</command> to
label the disk devices and use the labels in
- <filename>/etc/fstab</filename>. Because
- <command>glabel</command> stores the label in the last sector of
- a given provider, the label will remain persistent across
- reboots. By using this label as a device, the file system may
- always be mounted regardless of what device node it is accessed
- through.</para>
+ <filename>/etc/fstab</filename>.
+ Since <command>glabel</command> stores the label in the last
+ sector of a given provider, the label will remain persistent
+ across reboots. By using this label as a device, the
+ file-system may always be mounted regardless of what
+ device node it is accessed through.</para>
<note>
<para><command>glabel</command> can create both transient and