aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/handbook
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/books/handbook')
-rw-r--r--en_US.ISO8859-1/books/handbook/basics/chapter.xml6
-rw-r--r--en_US.ISO8859-1/books/handbook/boot/chapter.xml2
-rw-r--r--en_US.ISO8859-1/books/handbook/config/chapter.xml4
-rw-r--r--en_US.ISO8859-1/books/handbook/geom/chapter.xml16
-rw-r--r--en_US.ISO8859-1/books/handbook/multimedia/chapter.xml2
-rw-r--r--en_US.ISO8859-1/books/handbook/security/chapter.xml4
-rw-r--r--en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml4
-rw-r--r--en_US.ISO8859-1/books/handbook/zfs/chapter.xml6
8 files changed, 22 insertions, 22 deletions
diff --git a/en_US.ISO8859-1/books/handbook/basics/chapter.xml b/en_US.ISO8859-1/books/handbook/basics/chapter.xml
index bc31008871..1be3270b7e 100644
--- a/en_US.ISO8859-1/books/handbook/basics/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/basics/chapter.xml
@@ -2867,7 +2867,7 @@ Swap: 2048M Total, 2048M Free
</step>
<step>
- <para>Use &man.kill.1; to send the signal. Because
+ <para>Use &man.kill.1; to send the signal. As
&man.inetd.8; is owned by
<systemitem class="username">root</systemitem>, use
&man.su.1; to become
@@ -3218,8 +3218,8 @@ Swap: 2048M Total, 2048M Free
<primary>editors</primary>
</indexterm>
- <para>Most &os; configuration is done by editing text files.
- Because of this, it is a good idea to become familiar with a
+ <para>Most &os; configuration is done by editing text files, so
+ it is a good idea to become familiar with a
text editor. &os; comes with a few as part of the base system,
and many more are available in the Ports Collection.</para>
diff --git a/en_US.ISO8859-1/books/handbook/boot/chapter.xml b/en_US.ISO8859-1/books/handbook/boot/chapter.xml
index aa0c741acb..2eead109e5 100644
--- a/en_US.ISO8859-1/books/handbook/boot/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/boot/chapter.xml
@@ -217,7 +217,7 @@ Default: F2</screen>
<title>Stage One and Stage Two</title>
<para>Conceptually, the first and second stages are part of the
- same program on the same area of the disk. Because of space
+ same program on the same area of the disk. Due to space
constraints, they have been split into two, but are always
installed together. They are copied from the combined
<filename>/boot/boot</filename> by the &os; installer or
diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.xml b/en_US.ISO8859-1/books/handbook/config/chapter.xml
index dd0a3d7bc3..f7f24a65f4 100644
--- a/en_US.ISO8859-1/books/handbook/config/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/config/chapter.xml
@@ -748,7 +748,7 @@ linuxemu/chapter.xml -->
Network Driver Interface Specification
(<acronym>NDIS</acronym>). It includes &man.ndisgen.8;
which can be used to convert a &windowsxp; driver into a
- format that can be used on &os;. Because the &man.ndis.4;
+ format that can be used on &os;. As the &man.ndis.4;
driver uses a &windowsxp; binary, it only runs on &i386;
and amd64 systems. <acronym>PCI</acronym>, CardBus,
<acronym>PCMCIA</acronym>, and <acronym>USB</acronym>
@@ -2344,7 +2344,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
referred to as <emphasis>journaling</emphasis>.
Meta-data updates are still written synchronously, but only
into a small region of the disk. Later on, they are moved
- to their proper location. Because the logging area is a
+ to their proper location. Since the logging area is a
small, contiguous region on the disk, there are no long
distances for the disk heads to move, even during heavy
operations, so these operations are quicker than synchronous
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
diff --git a/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml b/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
index 53dc3c06b2..e1ae696ce9 100644
--- a/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
@@ -839,7 +839,7 @@ kern.ipc.shmall=32768</programlisting>
an <application>&xorg;</application> extension which
allows a program to bypass the
<application>&xorg;</application> server and directly
- alter the framebuffer. Because it relies on a low level
+ alter the framebuffer. As it relies on a low-level
memory mapping, programs using it must be run as
<systemitem class="username">root</systemitem>. The
<acronym>DGA</acronym> extension can be tested and
diff --git a/en_US.ISO8859-1/books/handbook/security/chapter.xml b/en_US.ISO8859-1/books/handbook/security/chapter.xml
index 4bc3279737..d3b277a978 100644
--- a/en_US.ISO8859-1/books/handbook/security/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/security/chapter.xml
@@ -696,7 +696,7 @@ cat changed
The authentication system keeps track of the last one-time
password used, and the user is authenticated if the hash of the
user-provided password is equal to the previous password.
- Because a one-way hash is used, it is impossible to generate
+ Since a one-way hash is used, it is impossible to generate
future one-time passwords if a successfully used password is
captured. The iteration count is decremented after each
successful login to keep the user and the login program in sync.
@@ -1196,7 +1196,7 @@ sendmail : PARANOID : deny</programlisting>
<quote>trusted third party</quote> of the system. It is the
computer that issues <application>Kerberos</application>
tickets, which are used for clients to authenticate to
- servers. Because the <acronym>KDC</acronym> is considered
+ servers. As the <acronym>KDC</acronym> is considered
trusted by all other computers in the
<application>Kerberos</application> realm, it has heightened
security concerns. Direct access to the KDC should be
diff --git a/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml b/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml
index 9913ad3755..db13e71ef6 100644
--- a/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml
@@ -1031,7 +1031,7 @@ ttyu5 "/usr/libexec/getty std.19200" vt100 on insecure</programlisting>
device provides a 16-character buffer, which allows for better
system performance. Bugs in plain 16550 devices prevent the use
of the 16-character buffer, so use 16550A devices if possible.
- Because single-character-buffer devices require more work by the
+ As single-character-buffer devices require more work by the
operating system than the 16-character-buffer devices,
16550A-based serial interface cards are preferred. If the
system has many active serial ports or will have a heavy load,
@@ -1081,7 +1081,7 @@ ttyu5 "/usr/libexec/getty std.19200" vt100 on insecure</programlisting>
<para>The second method is to configure the
<acronym>RS-232</acronym> interface to vary its speed based on
- the remote user's connection speed. Because
+ the remote user's connection speed. As
<command>getty</command> does not understand any particular
modem's connection speed reporting, it gives a
<prompt>login:</prompt> message at an initial speed and
diff --git a/en_US.ISO8859-1/books/handbook/zfs/chapter.xml b/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
index c6d89f091a..ef1064a438 100644
--- a/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
@@ -1282,7 +1282,7 @@ errors: No known data errors</screen>
2&nbsp;TB drive. The usable space is 1&nbsp;TB. When the
1&nbsp;TB drive is replaced with another 2&nbsp;TB drive, the
resilvering process copies the existing data onto the new
- drive. Because
+ drive. As
both of the devices now have 2&nbsp;TB capacity, the mirror's
available space can be grown to 2&nbsp;TB.</para>
@@ -4045,7 +4045,7 @@ vfs.zfs.vdev.cache.size="5M"</programlisting>
Clones can be <emphasis>promoted</emphasis>, reversing
this dependency and making the clone the parent and the
previous parent the child. This operation requires no
- additional space. Because the amount of space used by
+ additional space. Since the amount of space used by
the parent and child is reversed, existing quotas and
reservations might be affected.</entry>
</row>
@@ -4201,7 +4201,7 @@ vfs.zfs.vdev.cache.size="5M"</programlisting>
blocks will be checked byte-for-byte to ensure it is
actually identical. If the data is not identical, the
hash collision will be noted and the two blocks will be
- stored separately. Because <acronym>DDT</acronym> must
+ stored separately. As <acronym>DDT</acronym> must
store the hash of each unique block, it consumes a very
large amount of memory. A general rule of thumb is
5-6&nbsp;GB of ram per 1&nbsp;TB of deduplicated data).