Arch handbook and articles: Reword sentences beginning with 'Because...'

These sentences can either be or be mistaken for being sentence
fragments. While it is perfectly reasonable to use subordinate
conjunctions conversationally, as long as both clauses are explicitly
used in the same sentence, the handbook or articles are not written
in this style.

PR:		252493
Submitted by:	Ceri Davies (ceri AT submonkey.net)
Reviewed by:	0mp, pauamma (pauamma AT gundo.com)

6 files changed, 17 insertions, 17 deletions

diff --git a/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml
index 65f8c6cfd0..798b7bc6d9 100644
--- a/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml
@@ -404,7 +404,7 @@ FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610</screen></entr
       jmp main-0x7c00+0x600	# Jump to relocated code</programlisting>
     </figure>
 
-    <para>Because <filename>boot0</filename> is loaded by the
+    <para>As <filename>boot0</filename> is loaded by the
       <acronym>BIOS</acronym> to address <literal>0x7C00</literal>, it
       copies itself to address <literal>0x600</literal> and then
       transfers control there (recall that it was linked to execute at
@@ -1021,7 +1021,7 @@ main.3:
       bytes of <filename>boot</filename> and, because
       <filename>boot</filename> is written to the first sector of the
       &os; slice, <filename>boot1</filename> fits exactly in this
-      first sector.  Because <literal>nread</literal> reads the first
+      first sector.  When <literal>nread</literal> reads the first
       16 sectors of the &os; slice, it effectively reads the entire
       <filename>boot</filename> file
       <footnote>
@@ -1440,7 +1440,7 @@ init:		cli				# Disable interrupts
       flags in the EFLAGS register.  Note that the
       <literal>popfl</literal> instruction pops out a doubleword (4
       bytes) from the stack and places it in the EFLAGS register.
-      Because the value actually popped is <literal>2</literal>, the
+      As the value actually popped is <literal>2</literal>, the
       EFLAGS register is effectively cleared (IA-32 requires that bit
       2 of the EFLAGS register always be 1).</para>
 
@@ -1583,7 +1583,7 @@ init.3:		lea 0x8(%di),%di		# Next entry
       abstraction.  The IA-32 architecture demands the creation and
       use of <emphasis>at least</emphasis> one <acronym>TSS</acronym>
       if multitasking facilities are used or different privilege
-      levels are defined.  Because the <filename>boot2</filename>
+      levels are defined.  Since the <filename>boot2</filename>
       client is executed in privilege level 3, but the
       <acronym>BTX</acronym> server does in privilege level 0, a
       <acronym>TSS</acronym> must be defined:</para>
diff --git a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
index 6e5551873b..9826e3a1d9 100644
--- a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
@@ -397,10 +397,10 @@ Closing device "echo".</screen>
     <para>For this reason, no serious applications rely on block
       devices, and in fact, almost all applications which access
       disks directly take great pains to specify that character
-      (or <quote>raw</quote>) devices should always be used.  Because
+      (or <quote>raw</quote>) devices should always be used.  As
       the implementation of the aliasing of each disk (partition) to
       two devices with different semantics significantly complicated
-      the relevant kernel code &os; dropped support for cached disk
+      the relevant kernel code, &os; dropped support for cached disk
       devices as part of the modernization of the disk I/O
       infrastructure.</para>
   </sect1>
diff --git a/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
index 97bd2822c5..04de498a3f 100644
--- a/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
@@ -375,7 +375,7 @@
         with PnP. This feature is not implemented in any existing
         driver and is not considered further in this document.</para>
 
-      <para>Because the PnP devices are disabled when probing the
+      <para>As the PnP devices are disabled when probing the
         legacy devices they will not be attached twice (once as legacy
         and once as PnP).  But in case of device-dependent identify
         routines it is the responsibility of the driver to make sure
@@ -1019,7 +1019,7 @@
               Free the memory allocated by
               <function>bus_dmamem_alloc()</function>. At present,
               freeing of the memory allocated with ISA restrictions is
-              not implemented.  Because of this the recommended model
+              not implemented.  Due to this the recommended model
               of use is to keep and re-use the allocated areas for as
               long as possible. Do not lightly free some area and then
               shortly allocate it again. That does not mean that
@@ -1322,11 +1322,11 @@
           Before calling the callback function from
           <function>bus_dmamap_load()</function> the segment array is
           stored in the stack. And it gets pre-allocated for the
-          maximal number of segments allowed by the tag. Because of
+          maximal number of segments allowed by the tag. As a result of
           this the practical limit for the number of segments on i386
           architecture is about 250-300 (the kernel stack is 4KB minus
           the size of the user structure, size of a segment array
-          entry is 8 bytes, and some space must be left). Because the
+          entry is 8 bytes, and some space must be left). Since the
           array is allocated based on the maximal number this value
           must not be set higher than really needed. Fortunately, for
           most of hardware the maximal supported number of segments is
@@ -2192,7 +2192,7 @@
           int error = 0;</programlisting>
 
         <para>Then allocate and activate all the necessary
-          resources. Because normally the port range will be released
+          resources. As normally the port range will be released
           before returning from probe, it has to be allocated
           again. We expect that the probe routine had properly set all
           the resource ranges, as well as saved them in the structure
diff --git a/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml
index a9a2753d9a..59261a9568 100644
--- a/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml
@@ -52,7 +52,7 @@
       <indexterm><primary>Linksys</primary></indexterm>
       <indexterm><primary>D-Link</primary></indexterm>
 
-      <para>Because of this practice, FreeBSD drivers usually rely on
+      <para>Due to this practice, FreeBSD drivers usually rely on
 	numeric IDs for device identification.  Using numeric IDs and
 	a centralized database complicates adding IDs and support for
 	cards to the system.  One must carefully check to see who
diff --git a/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml
index c325840bed..7de627b5b9 100644
--- a/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml
@@ -103,7 +103,7 @@
       then also converting the SCSI commands to the native commands of
       the hardware).</para>
 
-    <para>Because we are interested in writing a SCSI adapter driver
+    <para>As we are interested in writing a SCSI adapter driver
       here, from this point on we will consider everything from the
       SIM standpoint.</para>
 
@@ -1076,7 +1076,7 @@
 	  the timeout to make sure that the target is not sleeping
 	  forever.  If the command would not get aborted in some
 	  reasonable time like 10 seconds the timeout routine would go
-	  ahead and reset the whole SCSI bus.  Because the command
+	  ahead and reset the whole SCSI bus.  Since the command
 	  will be aborted in some reasonable time we can just return
 	  the abort request now as successfully completed, and mark
 	  the aborted CCB as aborted (but not mark it as done
@@ -1116,7 +1116,7 @@
     return;</programlisting>
 
 	<para>That is all for the ABORT request, although there is one
-	  more issue.  Because the ABORT message cleans all the
+	  more issue.  As the ABORT message cleans all the
 	  ongoing transactions on a LUN we have to mark all the other
 	  active transactions on this LUN as aborted.  That should be
 	  done in the interrupt routine, after the transaction gets
@@ -1634,7 +1634,7 @@
       routine (or the other way around, the poll routine may be doing
       the real action and the interrupt routine would just call the
       poll routine).  Why bother about a separate function then?
-      Because of different calling conventions.  The
+      Due to different calling conventions.  The
       <function>xxx_poll</function> routine gets the struct cam_sim
       pointer as its argument when the PCI interrupt routine by common
       convention gets pointer to the struct
diff --git a/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml
index 6fa02b2d59..1d34c3192b 100644
--- a/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml
@@ -668,7 +668,7 @@ This part is unclear, is it an unformatted code example?
 
     <para>Example: Firmware download Many devices that have been
       developed are based on a general purpose processor with an
-      additional USB core added to it.  Because the development of
+      additional USB core added to it.  Since the development of
       drivers and firmware for USB devices is still very new, many
       devices require the downloading of the firmware after they have
       been connected.</para>