Some more rewording around "you", more to come.

Remove booting with NTloader and LILO entries.

Sponsored by:	iXsystems

1 files changed, 229 insertions, 373 deletions

diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml
index b493e2ad9f..f9831ea55d 100644
--- a/en_US.ISO8859-1/books/faq/book.xml
+++ b/en_US.ISO8859-1/books/faq/book.xml
@@ -210,11 +210,10 @@
 	      Collection</link>.</para>
 
 	  <para>If an application is only
-	    available on one operating system, you cannot just
-	    replace that operating system.  Chances are, there is a
-	    very similar application on &os;, however.  If you want a
-	    solid office or Internet server, a reliable workstation,
-	    or just the ability to do your job without interruptions,
+	    available on one operating system,
+	    that operating system cannot just be replaced.  Chances are, there is a
+	    very similar application on &os;, however.  As a
+	    solid office or Internet server or a reliable workstation,
 	    &os; will almost certainly do everything you need.  Many
 	    computer users across the world, including both novices
 	    and experienced &unix; administrators, use &os; as their
@@ -984,7 +983,7 @@
 		a general help channel with many users at any time.
 		The conversations have been known to run off-topic for
 		a while, but priority is given to users with &os;
-		questions.  Other users can help you understand
+		questions.  Other users can help with
 		the basics, referring to the Handbook whenever
 		possible and providing links for learning more about
 		the topic you need help with.  This is primarily an
@@ -1714,8 +1713,8 @@
 	  <answer>
 	    <para>&os; supports SCSI changers using the &man.ch.4;
 	      device and the &man.chio.1; command.  The details of how
-	      you actually control the changer can be found in the
-	      &man.chio.1; manual page.</para>
+	      to control the changer can be found in
+	      &man.chio.1;.</para>
 
 	    <para>While
 	      <application>AMANDA</application> and some other products
@@ -1749,10 +1748,8 @@
 	      drive.  See &man.burncd.8; for details.</para>
 
 	    <para>&os; also supports any SCSI CD-R or CD-RW drives.
-	      Install and use <command>cdrecord</command> from the
-	      ports or packages system, and make sure that you have
-	      the <filename>pass</filename> device compiled in your
-	      kernel.</para>
+	      Install the <package>sysutils/cdrtools</package>
+	      port or package, then use <command>cdrecord</command>.</para>
 	  </answer>
 	</qandaentry>
       </qandaset>
@@ -1769,8 +1766,8 @@
 	  </question>
 
 	  <answer>
-	    <para>If you are using the default console driver,
-	      &man.syscons.4;, you can use a mouse pointer in text
+	    <para>The default console driver,
+	      &man.syscons.4;, provides the ability to use a mouse pointer in text
 	      consoles to cut &amp; paste text.  Run the mouse daemon,
 	      &man.moused.8;, and turn on the mouse pointer in the
 	      virtual console:</para>
@@ -1788,10 +1785,10 @@
 	      the &man.moused.8; manual page for a list of supported
 	      protocol types.</para>
 
-	    <para>If you have a PS/2 mouse, just add
+	    <para>For a PS/2 mouse, add
 	      <literal>moused_enable="YES"</literal> to
 	      <filename>/etc/rc.conf</filename> to start the mouse
-	      daemon at boot-time.  Additionally, if you would like to
+	      daemon at boot time.  Additionally, to
 	      use the mouse daemon on all virtual terminals instead of
 	      just the console, add <literal>allscreens_flags="-m
 		on"</literal> to
@@ -1813,9 +1810,9 @@
 
 	  <answer>
 	    <para>It is not possible to remove data using the mouse.
-	      However, it is possible to <quote>copy and
-		paste</quote>.
-	      Once you get the mouse daemon running as described in the <link
+	      However, it is possible to copy and
+		paste.
+	      Once the mouse daemon is running as described in the <link
 		linkend="moused">previous question</link>, hold down
 	      button 1 (left button) and move the mouse to select a
 	      region of text.  Then, press button 2 (middle button) to
@@ -1823,8 +1820,8 @@
 	      button) will <quote>extend</quote> the selected region
 	      of text.</para>
 
-	    <para>If your mouse does not have a middle button, you may
-	      wish to emulate one or remap buttons using mouse daemon
+	    <para>If the mouse does not have a middle button, it is possible
+	      to emulate one or remap buttons using mouse daemon
 	      options.  See the &man.moused.8; manual page for
 	      details.</para>
 	  </answer>
@@ -1858,14 +1855,14 @@
 
 	  <answer>
 	    <para>For the <application>Bourne Shell</application>, add
-	      the following lines to your <filename>.shrc</filename>.
+	      the following lines to <filename>~/.shrc</filename>.
 	      See &man.sh.1; and &man.editrc.5;.</para>
 
 	    <programlisting>bind ^? ed-delete-next-char # for console
 bind ^[[3~ ed-delete-next-char # for xterm</programlisting>
 
 	    <para>For the <application>C Shell</application>, add the
-	      following lines to your <filename>.cshrc</filename>.
+	      following lines to <filename>~/.cshrc</filename>.
 	      See &man.csh.1;.</para>
 
 	    <programlisting>bindkey ^? delete-char # for console
@@ -1935,13 +1932,13 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
 	    memory can not be accessed by that address space.</para>
 
 	  <para>What happens to the memory that should appear in that
-	    location is dependent on your hardware.  Unfortunately,
+	    location is hardware dependent.  Unfortunately,
 	    some hardware does nothing and the ability to use that
 	    last 500&nbsp;MB of RAM is entirely lost.</para>
 
 	  <para>Luckily, most hardware remaps the memory to a higher
 	    location so that it can still be used.  However, this can
-	    cause some confusion if you watch the boot
+	    cause some confusion when watching the boot
 	    messages.</para>
 
 	  <para>On a 32-bit version of &os;, the memory appears lost,
@@ -1971,11 +1968,11 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
 	</question>
 
 	<answer>
-	  <para>Signal 11 errors are caused when your process has
+	  <para>Signal 11 errors are caused when a process has
 	    attempted to access memory which the operating system has
 	    not granted it access to.  If something like this is
-	    happening at seemingly random intervals then you need to
-	    start investigating things very carefully.</para>
+	    happening at seemingly random intervals,
+	    start investigating the cause.</para>
 
 	  <para>These problems can usually be attributed to
 	    either:</para>
@@ -1983,8 +1980,8 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
 	  <orderedlist>
 	    <listitem>
 	      <para>If the problem is occurring only in a specific
-		application that you are developing yourself it is
-		probably a bug in your code.</para>
+		custom application, it is
+		probably a bug in the code.</para>
 	    </listitem>
 
 	    <listitem>
@@ -1996,103 +1993,97 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
 	    </listitem>
 	  </orderedlist>
 
-	  <para>In particular, a dead giveaway that this is
-	    <emphasis>not</emphasis> a &os; bug is if you see the
-	    problem when you are compiling a program, but the activity
+	  <para>It is probably
+	    not a &os; bug if the
+	    problem occurs compiling a program, but the activity
 	    that the compiler is carrying out changes each
 	    time.</para>
 
-	  <para>For example, suppose you are running <command>make
-	      buildworld</command>, and the compile fails while trying
+	  <para>For example, if <command>make
+	      buildworld</command> fails while trying
 	    to compile <filename>ls.c</filename> into
-	    <filename>ls.o</filename>.  If you then run <command>make
-	      buildworld</command> again, and the compile fails in the
-	    same place then this is a broken build &mdash; try
-	    updating your sources and try again.  If the compile fails
-	    elsewhere then this is almost certainly hardware.</para>
-
-	  <para>What you should do:</para>
+	    <filename>ls.o</filename> and, when run again, it fails in the
+	    same place, this is a broken build.  Try
+	    updating source and try again.  If the compile fails
+	    elsewhere, it is almost certainly due to hardware.</para>
 
-	  <para>In the first case you can use a debugger e.g.,
+	  <para>In the first case, use a debugger such as
 	    &man.gdb.1; to find the point in the program which is
-	    attempting to access a bogus address and then fix
+	    attempting to access a bogus address and fix
 	    it.</para>
 
-	  <para>In the second case you need to verify that it is not
-	    your hardware at fault.</para>
+	  <para>In the second case, verify which piece of
+	    hardware is at fault.</para>
 
 	  <para>Common causes of this include:</para>
 
 	  <orderedlist>
 	    <listitem>
-	      <para>Your hard disks might be overheating: Check the
-		fans in your case are still working, as your disk (and
-		perhaps other hardware might be overheating).</para>
+	      <para>The hard disks might be overheating: Check that the
+		fans are still working, as the disk and
+		other hardware might be overheating.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>The processor running is overheating: This might
 		be because the processor has been overclocked, or the
-		fan on the processor might have died.  In either case
-		you need to ensure that you have hardware running at
+		fan on the processor might have died.  In either case,
+		ensure that the hardware is running at
 		what it is specified to run at, at least while trying
-		to solve this problem (in other words, clock it back
+		to solve this problem.  If it is not, clock it back
 		to the default settings.)</para>
 
-	      <para>If you are overclocking then note that it is far
+	      <para>Regarding overclocking, it is far
 		cheaper to have a slow system than a fried system that
-		needs replacing!  Also the wider community is not
-		often sympathetic to problems on overclocked systems,
-		whether you believe it is safe or not.</para>
+		needs replacing!  Also the community is not
+		sympathetic to problems on overclocked systems.</para>
 	    </listitem>
 
 	    <listitem>
-	      <para>Dodgy memory: If you have multiple memory
-		SIMMS/DIMMS installed then pull them all out and try
+	      <para>Dodgy memory: if multiple memory
+		SIMMS/DIMMS are installed, pull them all out and try
 		running the machine with each SIMM or DIMM
-		individually and narrow the problem down to either the
+		individually to narrow the problem down to either the
 		problematic DIMM/SIMM or perhaps even a
 		combination.</para>
 	    </listitem>
 
 	    <listitem>
-	      <para>Over-optimistic Motherboard settings: In your BIOS
-		settings, and some motherboard jumpers you have
-		options to set various timings, mostly the defaults
-		will be sufficient, but sometimes, setting the wait
+	      <para>Over-optimistic motherboard settings: the BIOS
+		settings, and some motherboard jumpers, provide
+		options to set various timings.  The defaults
+		are often sufficient, but sometimes setting the wait
 		states on RAM too low, or setting the <quote>RAM
-		  Speed: Turbo</quote> option, or similar in the BIOS
+		  Speed: Turbo</quote> option
 		will cause strange behavior.  A possible idea is to
-		set to BIOS defaults, but it might be worth noting
-		down your settings first!</para>
+		set to BIOS defaults, after noting
+		the current settings first.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Unclean or insufficient power to the motherboard.
-		If you have any unused I/O boards, hard disks, or
-		CD-ROMs in your system, try temporarily removing them
-		or disconnecting the power cable from them, to see if
-		your power supply can manage a smaller load.  Or try
+		Remove any unused I/O boards, hard disks, or
+		CD-ROMs,
+		or disconnect the power cable from them, to see if
+		the power supply can manage a smaller load.  Or try
 		another power supply, preferably one with a little
-		more power (for instance, if your current power supply
-		is rated at 250&nbsp;Watts try one rated at
-		300&nbsp;Watts).</para>
+		more power.  For instance, if the current power supply
+		is rated at 250&nbsp;Watts, try one rated at
+		300&nbsp;Watts.</para>
 	    </listitem>
 	  </orderedlist>
 
-	  <para>You should also read the SIG11 <acronym>FAQ</acronym> (listed below)
-	    which has excellent explanations of all these problems,
-	    albeit from a &linux; viewpoint.  It also discusses how
+	  <para>Read the section on <link linkend="signal11">Signal 11</link>
+	    for a further explanation and a discussion on how
 	    memory testing software or hardware can still pass faulty
-	    memory.</para>
-
-	  <para>Finally, if none of this has helped it is possible
-	    that you have just found a bug in &os;, and you should
-	    follow the instructions to send a problem report.</para>
-
-	  <para>There is an extensive <acronym>FAQ</acronym> on this at <link
+	    memory.  There is an extensive <acronym>FAQ</acronym> on this at <link
 	      xlink:href="http://www.bitwizard.nl/sig11/">the SIG11
 	      problem <acronym>FAQ</acronym></link>.</para>
+
+	  <para>Finally, if none of this has helped, it is possibly
+	    a bug in &os;.
+	    Follow <link linkend="access-pr">these instructions</link>
+	    to send a problem report.</para>
 	</answer>
       </qandaentry>
 
@@ -2105,21 +2096,21 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
 	</question>
 
 	<answer>
-	  <para>The &os; developers are very interested in these
-	    errors, but need some more information than just the error
-	    you see.  Copy your full crash message.  Then consult the
+	  <para>The &os; developers are interested in these
+	    errors, but need more information than just the error
+	    message.  Copy the full crash message.  Then consult the
 	    <acronym>FAQ</acronym> section on <link
 	      linkend="kernel-panic-troubleshooting">kernel
 	      panics</link>, build a debugging kernel, and get a
-	    backtrace.  This might sound difficult, but you do not
-	    need any programming skills; you just have to follow the
+	    backtrace.  This might sound difficult, but does not require
+	    any programming skills.  Just follow the
 	    instructions.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="proc-table-full">
-	  <para>Why do I get the error <errorname>maxproc limit
+	  <para>What is the meaning of the error <errorname>maxproc limit
 	      exceeded by uid %i, please see tuning(7) and
 	      login.conf(5)</errorname>?</para>
 	</question>
@@ -2130,31 +2121,30 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
 	    the <varname>kern.maxusers</varname> &man.sysctl.8;
 	    variable.  <varname>kern.maxusers</varname> also affects
 	    various other in-kernel limits, such as network buffers.
-	    If your machine is heavily loaded, you probably want to
+	    If the machine is heavily loaded,
 	    increase <varname>kern.maxusers</varname>.  This will
 	    increase these other system limits in addition to the
 	    maximum number of processes.</para>
 
-	  <para>To adjust your <varname>kern.maxusers</varname> value,
+	  <para>To adjust the <varname>kern.maxusers</varname> value,
 	    see the <link
 	      xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">File/Process
-	      Limits</link> section of the Handbook.  (While that
+	      Limits</link> section of the Handbook.  While that
 	    section refers to open files, the same limits apply to
-	    processes.)</para>
+	    processes.</para>
 
-	  <para>If the machine is lightly loaded and you are
-	    running a very large number of processes, you can adjust
-	    this with the <varname>kern.maxproc</varname> tunable.  If
-	    this tunable needs adjustment it needs to be defined in
+	  <para>If the machine is lightly loaded but
+	    running a very large number of processes, adjust
+	    the <varname>kern.maxproc</varname> tunable by defining it in
 	    <filename>/boot/loader.conf</filename>.  The tunable will
 	    not get adjusted until the system is rebooted.  For more
 	    information about tuning tunables, see
 	    &man.loader.conf.5;.  If these processes are being run by
-	    a single user, you will also need to adjust
+	    a single user, adjust
 	    <varname>kern.maxprocperuid</varname> to be one less than
-	    your new <varname>kern.maxproc</varname> value.  (It must
+	    the new <varname>kern.maxproc</varname> value.  It must
 	    be at least one less because one system program,
-	    &man.init.8;, must always be running.)</para>
+	    &man.init.8;, must always be running.</para>
 	</answer>
       </qandaentry>
 
@@ -2196,7 +2186,7 @@ to /etc/mail/sendmail.cf.</programlisting>
 	</question>
 
 	<answer>
-	  <para>The remote machine may be setting your terminal type
+	  <para>The remote machine may be setting the terminal type
 	    to something other than the <literal>cons25</literal>
 	    terminal type required by the &os; console.</para>
 
@@ -2215,9 +2205,9 @@ to /etc/mail/sendmail.cf.</programlisting>
 	    <listitem>
 	      <para>Use a VT100 emulator like
 		<application>screen</application> at the &os; console.
-		<application>screen</application> offers you the
+		<application>screen</application> provides the
 		ability to run multiple concurrent sessions from one
-		terminal, and is a neat program in its own right.
+		terminal.
 		Each <application>screen</application> window behaves
 		like a VT100 terminal, so the <envar>TERM</envar>
 		variable at the remote end should be set to
@@ -2228,8 +2218,8 @@ to /etc/mail/sendmail.cf.</programlisting>
 	      <para>Install the <literal>cons25</literal> terminal
 		database entry on the remote machine.  The way to do
 		this depends on the operating system on the remote
-		machine.  The system administration manuals for the
-		remote system should be able to help you here.</para>
+		machine.  Refer to the system administration manuals for the
+		remote system.</para>
 	    </listitem>
 
 	    <listitem>
@@ -2267,29 +2257,28 @@ to /etc/mail/sendmail.cf.</programlisting>
 	    &os;, do this to store the hostname in a log file for
 	    future reference by the administrator.</para>
 
-	  <para>The remedy: if the problem occurs whenever you connect
-	    from your computer (the client) to any server, the problem
-	    is with the client; likewise, if the problem only occurs
-	    when someone connects to your computer (the server) the
+	  <para>The remedy: if the problem occurs whenever connecting
+	    the client computer to any server, the problem
+	    is with the client.  If the problem only occurs
+	    when someone connects to the server computer, the
 	    problem is with the server.</para>
 
 	  <para>If the problem is with the client, the only remedy is
 	    to fix the DNS so the server can resolve it.  If this is
 	    on a local network, consider it a server problem and keep
-	    reading; conversely, if this is on the global Internet,
-	    you will most likely need to contact your ISP and ask them
-	    to fix it for you.</para>
-
-	  <para>If the problem is with the server, and this is on a
-	    local network, you need to configure the server to be able
-	    to resolve address-to-hostname queries for your local
-	    address range.  See the &man.hosts.5; and &man.named.8;
-	    manual pages for more information.  If this is on the
-	    global Internet, the problem may be that your server's
+	    reading.  If this is on the Internet,
+	    contact your ISP.</para>
+
+	  <para>If the problem is with the server on a
+	    local network, configure the server
+	    to resolve address-to-hostname queries for the local
+	    address range.  See &man.hosts.5; and &man.named.8;
+	    for more information.  If this is on the
+	    Internet, the problem may be that the local server's
 	    resolver is not functioning correctly.  To check, try to
-	    look up another host &mdash; say,
+	    look up another host such as
 	    <systemitem>www.yahoo.com</systemitem>.  If it does not
-	    work, that is your problem.</para>
+	    work, that is the problem.</para>
 
 	  <para>Following a fresh install of &os;, it is also possible
 	    that domain and name server information is missing from
@@ -2298,7 +2287,7 @@ to /etc/mail/sendmail.cf.</programlisting>
 	    option <literal>UseDNS</literal> is set to
 	    <literal>yes</literal> by default in
 	    <filename>/etc/ssh/sshd_config</filename>.  If this is
-	    causing the problem, you will either need to fill in the
+	    causing the problem, either fill in the
 	    missing information in
 	    <filename>/etc/resolv.conf</filename> or set
 	    <literal>UseDNS</literal> to <literal>no</literal> in
@@ -2314,8 +2303,8 @@ to /etc/mail/sendmail.cf.</programlisting>
 	</question>
 
 	<answer>
-	  <para>This error message indicates you have exhausted the
-	    number of available file descriptors on your system.
+	  <para>This error message indicates that the
+	    number of available file descriptors have been exhausted on the system.
 	    Refer to the <link
 	      xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">kern.maxfiles</link>
 	    section of the <link
@@ -2395,9 +2384,9 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	    disk for more than 20 seconds.  It might be caused by bad
 	    blocks on the disk drive, disk wiring, cables, or any
 	    other disk I/O-related hardware.  If the drive itself is
-	    actually bad, you will also see disk errors in
+	    bad, disk errors will appear in
 	    <filename>/var/log/messages</filename> and in the output
-	    of <command>dmesg</command>.  Otherwise, check your cables
+	    of <command>dmesg</command>.  Otherwise, check the cables
 	    and connections.</para>
 	</answer>
       </qandaentry>
@@ -2434,8 +2423,8 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	    &man.witness.4; is conservative.  A true positive report
 	    <emphasis>does not</emphasis> mean that a system is
 	    dead-locked; instead it should be understood as a warning
-	    of the form <quote>if you were unlucky, a deadlock would
-	      have happened here</quote>.</para>
+	    that a deadlock could
+	      have happened here.</para>
 
 	  <note>
 	    <para>Problematic <acronym>LOR</acronym>s tend to get
@@ -2493,7 +2482,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	  <para>This error does not mean that the &man.touch.1;
 	    utility is missing.  The error is instead probably due to
 	    the dates of the files being set sometime in the future.
-	    If your CMOS-clock is set to local time, run
+	    If the CMOS clock is set to local time, run
 	    <command>adjkerntz&nbsp;-i</command> to adjust
 	    the kernel clock when booting into single-user
 	    mode.</para>
@@ -2526,21 +2515,11 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	    of release in also included in the
 	    <filename>ports/</filename> directory.</para>
 
-	  <para>We also support the concept of a
-	    <quote>package</quote>, essentially no more than a
-	    compressed binary distribution with a little extra
-	    intelligence embedded in it for doing whatever custom
-	    installation work is required.  A package can be installed
-	    and uninstalled again easily without having to know the
-	    gory details of which files it includes.</para>
-
-	  <para>Use &man.pkg.7; on the specific package files you are
-	    interested in installing.  Package files can usually be
-	    identified by their <filename>.txz</filename> suffix and
-	    CD-ROM distribution people will have a
-	    <filename>packages/All</filename> directory on their CD
-	    which contains such files.  They can also be downloaded
-	    over the net for various versions of &os;.</para>
+	  <para>&os; supports
+	    packages, which provide a
+	    compressed binary distribution.  Package can be installed
+	    and uninstalled again easily.  On &os;,
+	    &man.pkg.7; to install packages.</para>
 	</answer>
       </qandaentry>
 
@@ -2555,20 +2534,24 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 
 	  <itemizedlist>
 	    <listitem>
-	      <para>Use portsnap for most use cases.</para>
+	      <para>Use portsnap for most use cases.  Refer to <link
+		  xlink:href="&url.books.handbook;/ports-using.html">Using
+		the Ports Collection</link> for instructions on how to
+		use this tool.</para>
 	    </listitem>
 	    <listitem>
-	      <para>Use SVN directly if you need custom patches to the
-		ports tree.</para>
+	      <para>Use SVN if custom patches to the
+		ports tree are needed.  Refer to <link
+		  xlink:href="&url.books.handbook;/svn.html">Using
+		Subversion</link> for details.</para>
 	    </listitem>
 	    <listitem>
-	      <para>Use CTM if you prefer getting patches by email
-		(this is a rarer use case).</para>
+		<para>Use <acronym>CTM</acronym>, as described in <link
+		  xlink:href="&url.books.handbook;/ctm.html">Using
+		  <acronym>CTM</acronym></link> to receive patches by
+		email over an unreliable Internet connection.</para>
 	    </listitem>
 	  </itemizedlist>
-
-	  <para>Any other method should be considered a legacy method.
-	    If you do not already use them, do not start.</para>
 	</answer>
       </qandaentry>
 
@@ -2592,14 +2575,13 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	</question>
 
 	<answer>
-	  <para>If you are running a &os; version that lags
+	  <para>If the installed &os; version lags
 	    significantly behind <emphasis>-CURRENT</emphasis> or
-	    <emphasis>-STABLE</emphasis>, you may need to update your
-	    Ports Collection; see the <link
-	      xlink:href="&url.books.porters-handbook;/keeping-up.html">Keeping
-	      Up</link> section of the Porter's Handbook for further
-	    information on how to do this.  If you are up to date,
-	    then someone might have committed a change to the port
+	    <emphasis>-STABLE</emphasis>, update the
+	    Ports Collection using the instructions in <link
+	      xlink:href="&url.books.handbook;/ports-using.html">Using
+	      the Ports Collection</link>.  If the system is up-to-date,
+	    someone might have committed a change to the port
 	    which works for <emphasis>-CURRENT</emphasis> but which
 	    broke the port for <emphasis>-STABLE</emphasis>.
 	    Submit a bug report with the &man.send-pr.1;
@@ -2616,8 +2598,8 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	</question>
 
 	<answer>
-	  <para>First, always make sure that you have a complete
-	    up-to-date Ports Collection.  Errors that affect building
+	  <para>First, make sure that the
+	    Ports Collection is up-to-date.  Errors that affect building
 	    <filename>INDEX</filename> from an up-to-date copy of the
 	    Ports Collection are high-visibility and are thus almost
 	    always fixed immediately.</para>
@@ -2656,11 +2638,10 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	</question>
 
 	<answer>
-	  <para>By all means!  While a recent system will run with
-	    software compiled under an older release, you will end up
-	    with things randomly crashing and failing to work once you
-	    start installing other ports or updating a portion of what
-	    you already have.</para>
+	  <para>Yes!  While a recent system will run with
+	    software compiled under an older release,
+	    things will randomly crash and fail to work once
+	    other ports are installed or updated.</para>
 
 	  <para>When the system is upgraded, various shared libraries,
 	    loadable modules, and other parts of the system will be
@@ -2717,10 +2698,10 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	    shells have.  That is why other more featureful shells
 	    like <command>bash</command>, <command>scsh</command>,
 	    &man.tcsh.1;, and <command>zsh</command> are available.
-	    (You can compare for yourself the memory utilization of
-	    all these shells by looking at the <quote>VSZ</quote> and
+	    You can compare the memory utilization of
+	    these shells by looking at the <quote>VSZ</quote> and
 	    <quote>RSS</quote> columns in a <command>ps -u</command>
-	    listing.)</para>
+	    listing.</para>
 	</answer>
       </qandaentry>
 
@@ -2772,13 +2753,12 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	</question>
 
 	<answer>
-	  <para>Short answer: it is not possible.</para>
+	  <para>Short answer: no.</para>
 
-	  <para>Longer answer: if you have made any changes using
-	    <command>pkg</command> converting back is non-trivial and
+	  <para>Longer answer: converting back is non-trivial and
 	    requires lots of manual editing of internal package
-	    database files.  However, if you have just run
-	    <command>pkg2ng</command> then you may remove
+	    database files.  However, if
+	    <command>pkg2ng</command> has just been run, remove
 	    <filename>/var/db/pkg/local.sqlite</filename> and extract
 	    <filename>/var/backups/pkgdb.bak.tbz</filename>.</para>
 	</answer>
@@ -2806,9 +2786,9 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	      installed to the <filename>/boot/kernel</filename>
 	      directory along with its modules, while the old kernel
 	      and its modules will be moved to the
-	      <filename>/boot/kernel.old</filename> directory, so if
-	      you make a mistake the next time you play with your
-	      configuration you can boot the previous version of your
+	      <filename>/boot/kernel.old</filename> directory.  If
+	      a mistake is made in the
+	      configuration, simply boot the previous version of the
 	      kernel.</para>
 	  </note>
 	</answer>
@@ -2829,12 +2809,12 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 	    running a debug kernel, and it is useful to keep one
 	    around in case of a system panic.</para>
 
-	  <para>However, if you are running low on disk space, there
+	  <para>However, when running low on disk space, there
 	    are different options to reduce the size of
 	    <filename>/boot/kernel/</filename>.</para>
 
-	  <para>If you do not want the symbol files to be installed,
-	    make sure you have the following line present in
+	  <para>To not install the symbol files,
+	    make sure the following line exists in
 	    <filename>/etc/src.conf</filename>:</para>
 
 	  <programlisting>WITHOUT_KERNEL_SYMBOLS=yes</programlisting>
@@ -2846,44 +2826,42 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 
 	  <itemizedlist>
 	    <listitem>
-	      <para>You do not have a line in your kernel
-		configuration file that reads:</para>
+	      <para>This line does not exist in the kernel
+		configuration file:</para>
 
 	      <programlisting>makeoptions DEBUG=-g</programlisting>
 	    </listitem>
 
 	    <listitem>
-	      <para>You are not running &man.config.8; with
+	      <para>Do not run &man.config.8; with
 		<option>-g</option>.</para>
 	    </listitem>
 	  </itemizedlist>
 
-	  <para>Either of the above settings will cause your kernel to
-	    be built in debug mode.  As long as you make sure you
-	    follow the steps above, you can build your kernel
-	    normally.</para>
+	  <para>Either of the above settings will cause the kernel to
+	    be built in debug mode.</para>
 
-	  <para>If you want only the modules you use to be built and
-	    installed, make sure you have a line like below in
+	  <para>To build and install only the specified modules, list
+	    them in
 	    <filename>/etc/make.conf</filename>:</para>
 
 	  <programlisting>MODULES_OVERRIDE= <replaceable>accf_http ipfw</replaceable></programlisting>
 
 	  <para>Replace <emphasis>accf_httpd ipfw</emphasis> with a
-	    list of modules you need.  Only these modules will be
-	    built.  This does not only reduce the size of the kernel
-	    directory but also decreases the amount of time needed to
-	    build your kernel.  For more information see
+	    list of needed modules.  Only the listed modules will be
+	    built.  This reduces the size of the kernel
+	    directory and decreases the amount of time needed to
+	    build the kernel.  For more information, read
 	    <filename>/usr/share/examples/etc/make.conf</filename>.</para>
 
-	  <para>You can also remove unneeded devices from your kernel
+	  <para>Unneeded devices can be removed from the kernel
 	    to further reduce the size.  See <xref
 	      linkend="make-kernel"/> for more information.</para>
 
-	  <para>To put any of these options into effect you will have
+	  <para>To put any of these options into effect, follow the instructions
 	    to <link
 	      xlink:href="&url.books.handbook;/kernelconfig-building.html">build
-	      and install</link> your new kernel.</para>
+	      and install</link> the new kernel.</para>
 
 	  <para>Most kernels
 	    (<filename>/boot/kernel/kernel</filename>) tend to be
@@ -2899,45 +2877,38 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 
 	<answer>
 	  <para>There are a number of possible causes for this
-	    problem.  They are, in no particular order:</para>
+	    problem:</para>
 
 	  <itemizedlist>
 	    <listitem>
-	      <para>You are not using the <command>make
-		  buildkernel</command> and <command>make
-		  installkernel</command> targets, and your source
+	      <para>The source
 		tree is different from the one used to build the
-		currently running system (e.g., you are compiling
-		&rel.current;-RELEASE on a &rel2.current;-RELEASE
-		system).  If you are attempting an upgrade,
+		currently running system.  When attempting an upgrade,
 		read <filename>/usr/src/UPDATING</filename>, paying
 		particular attention to the <quote>COMMON
 		  ITEMS</quote> section at the end.</para>
 	    </listitem>
 
 	    <listitem>
-	      <para>You are using the <command>make
-		  buildkernel</command> and <command>make
-		  installkernel</command> targets, but you failed to
-		assert the completion of the <command>make
-		  buildworld</command> target.  The <command>make
+	      <para>The <command>make
+		  buildkernel</command> command did not complete
+		  successfuly.  The <command>make
 		  buildkernel</command> target relies on files
 		generated by the <command>make buildworld</command>
 		target to complete its job correctly.</para>
 	    </listitem>
 
 	    <listitem>
-	      <para>Even if you are trying to build <link
+	      <para>Even when building <link
 		  linkend="stable">&os;-STABLE</link>, it is possible
-		that you fetched the source tree at a time when it was
-		either being modified, or broken for other reasons;
-		only releases are absolutely guaranteed to be
+		that the source tree was fetched at a time when it was
+		either being modified or it was broken.
+		Only releases are guaranteed to be
 		buildable, although <link
 		  linkend="stable">&os;-STABLE</link> builds fine the
-		majority of the time.  If you have not already done
-		so, try re-fetching the source tree and see if the
-		problem goes away.  Try using a different server in
-		case the one you are using is having problems.</para>
+		majority of the time.  Try re-fetching the source tree and see if the
+		problem goes away.  Try using a different mirror in
+		case the previous one is having problems.</para>
 	    </listitem>
 	  </itemizedlist>
 	</answer>
@@ -2945,7 +2916,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
 
       <qandaentry>
 	<question xml:id="scheduler-in-use">
-	  <para>How can I verify which scheduler is in use on a
+	  <para>Which scheduler is in use on a
 	    running system?</para>
 	</question>
 
@@ -2997,38 +2968,37 @@ kern.sched.name: ULE</screen>
 	</question>
 
 	<answer>
-	  <para>The best way is to reinstall the OS on the new disk,
+	  <para>The best way is to reinstall the operating system on the new disk,
 	    then move the user data over.  This is highly recommended
-	    if you have been tracking <emphasis>-STABLE</emphasis> for
-	    more than one release, or have updated a release instead
-	    of installing a new one.  You can install booteasy on both
-	    disks with &man.boot0cfg.8;, and dual boot them until you
+	    when tracking <emphasis>-STABLE</emphasis> for
+	    more than one release or when updating a release instead
+	    of installing a new one.  Install booteasy on both
+	    disks with &man.boot0cfg.8; and dual boot until you
 	    are happy with the new configuration.  Skip the next
 	    paragraph to find out how to move the data after doing
 	    this.</para>
 
 	  <para>Alternatively, partition and label the new disk with
 	    either &man.sade.8; or &man.gpart.8;.  If the disks are
-	    MBR-formatted, you can also install booteasy on both disks
-	    with &man.boot0cfg.8;, so that you can dual boot to the
+	    MBR-formatted, booteasy can be installed on both disks
+	    with &man.boot0cfg.8; so that the computer can dual boot to the
 	    old or new system after the copying is done.</para>
 
-	  <para>Now you have the new disk set up, and are ready to
-	    move the data.  Unfortunately, you cannot just blindly
-	    copy the data.  Things like device files (in
-	    <filename>/dev</filename>), flags, and links tend to screw
-	    that up.  You need to use tools that understand these
-	    things, which means &man.dump.8;.  Although it is
-	    suggested that you move the data in single-user mode, it
+	  <para>Once the new disk set up,
+	    the data cannot just be copied.  Instead, use tools that
+	    understand device files and syste flags, such as
+	    &man.dump.8;.  Although it is recommended
+	    to move the data while in single-user mode, it
 	    is not required.</para>
 
-	  <para>You should never use anything but &man.dump.8; and
-	    &man.restore.8; to move the root file system.  The
-	    &man.tar.1; command may work &mdash; then again, it may
-	    not.  You should also use &man.dump.8; and &man.restore.8;
-	    if you are moving a single partition to another empty
+	  <para>When the disks are formatted with
+	    <acronym>UFS</acronym>, never use anything but &man.dump.8; and
+	    &man.restore.8; to move the root file system.  These
+	    commands should also be used when
+	    moving a single partition to another empty
 	    partition.  The sequence of steps to use
-	    <command>dump</command> to move a partitions data to a new
+	    <command>dump</command> to move the data from one
+	    <acronym>UFS</acronym> partitions to a new
 	    partition is:</para>
 
 	  <procedure>
@@ -3051,17 +3021,16 @@ kern.sched.name: ULE</screen>
 	    </step>
 	  </procedure>
 
-	  <para>For example, if you are going to move root to
-	    <filename>/dev/ada1s1a</filename>, with
-	    <filename>/mnt</filename> as the temporary mount point, it
-	    is:</para>
+	  <para>For example, to move
+	    <filename>/dev/ada1s1a</filename> with
+	    <filename>/mnt</filename> as the temporary mount point, type:</para>
 
 	  <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput>
 &prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput>
 &prompt.root; <userinput>cd /mnt</userinput>
 &prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen>
 
-	  <para>Rearranging your partitions with
+	  <para>Rearranging partitions with
 	    <command>dump</command> takes a bit more work.  To merge a
 	    partition like <filename>/var</filename> into its parent,
 	    create the new partition large enough for both, move the
@@ -3105,7 +3074,7 @@ kern.sched.name: ULE</screen>
 	</question>
 
 	<answer>
-	  <para>Short answer: you can usually use Soft Updates safely
+	  <para>Short answer: Soft Updates can usually be safely used
 	    on all partitions.</para>
 
 	  <para>Long answer:  Soft Updates has two characteristics
@@ -3119,17 +3088,15 @@ kern.sched.name: ULE</screen>
 	    thirty seconds to write changes to the physical disk.
 	    When a large file is deleted the file still resides on
 	    disk until the kernel actually performs the deletion.
-	    This can cause a very simple race condition.  Suppose you
-	    delete one large file and immediately create another large
-	    file.  The first large file is not yet actually removed
+	    This can cause a very simple race condition.  Suppose
+	    one large file is deleted and another large file is immediately created.
+	    The first large file is not yet actually removed
 	    from the physical disk, so the disk might not have enough
-	    room for the second large file.  You get an error that the
-	    partition does not have enough space, although you know
-	    perfectly well that you just released a large chunk of
-	    space!  When you try again mere seconds later, the file
-	    creation works as you expect.  This has left more than one
-	    user scratching his head and doubting his sanity, the &os;
-	    file system, or both.</para>
+	    room for the second large file.  This will produce an error that the
+	    partition does not have enough space, even though
+	    a large chunk of
+	    space has just been released.  A few seconds later, the file
+	    creation works as expected.</para>
 
 	  <para>If a system should crash after the kernel accepts a
 	    chunk of data for writing to disk, but before that data is
@@ -3143,15 +3110,14 @@ kern.sched.name: ULE</screen>
 	    rarely.  If the system crashed during the thirty-second
 	    window after such a change is made, it is possible that
 	    data could be lost.  This risk is negligible for most
-	    applications, but you should be aware that it exists.  If
-	    your system cannot tolerate this much risk, do not use
+	    applications, but be aware that it exists.  If
+	    the system cannot tolerate this much risk, do not use
 	    Soft Updates on the root file system!</para>
 
 	  <para><filename>/</filename> is traditionally one of the
-	    smallest partitions.  If you put the
-	    <filename>/tmp</filename> directory on
-	    <filename>/</filename> and you have a busy
-	    <filename>/tmp</filename>, you might see intermittent
+	    smallest partitions.  If
+	    <filename>/tmp</filename> is on
+	    <filename>/</filename>, there may be intermittent
 	    space problems.  Symlinking <filename>/tmp</filename> to
 	    <filename>/var/tmp</filename> will solve this
 	    problem.</para>
@@ -3241,10 +3207,10 @@ kern.sched.name: ULE</screen>
 	<answer>
 	  <para>The secondary DOS partitions are found after
 	    <emphasis>all</emphasis> the primary partitions.  For
-	    example, if you have an <quote>E</quote> partition as the
+	    example, if <literal>E</literal> is the
 	    second DOS partition on the second SCSI drive, there will
 	    be a device file for <quote>slice 5</quote> in
-	    <filename>/dev</filename>, so mount it:</para>
+	    <filename>/dev</filename>. To mount it:</para>
 
 	  <screen>&prompt.root; <userinput>mount -t msdosfs /dev/da1s5 /dos/e</userinput></screen>
 	</answer>
@@ -3256,8 +3222,8 @@ kern.sched.name: ULE</screen>
 	</question>
 
 	<answer>
-	  <para>Yes.  You can use either &man.gbde.8; or &man.geli.8;,
-	    see the <link
+	  <para>Yes, &man.gbde.8; and &man.geli.8;.
+	    See the <link
 	      xlink:href="&url.books.handbook;/disks-encrypting.html">Encrypting
 	      Disk Partitions</link> section of the &os;
 	    Handbook.</para>
@@ -3265,116 +3231,6 @@ kern.sched.name: ULE</screen>
       </qandaentry>
 
       <qandaentry>
-	<question xml:id="nt-bootloader">
-	  <para>How can I use the &windowsnt; loader to boot
-	    &os;?</para>
-	</question>
-
-	<answer>
-	  <para>The general idea is that you copy the first sector of
-	    your native root &os; partition into a file in the
-	    DOS/&windowsnt; partition.  Assuming you name that file
-	    something like <filename>c:\bootsect.bsd</filename>
-	    (inspired by <filename>c:\bootsect.dos</filename>), you
-	    can then edit <filename>c:\boot.ini</filename> to come up
-	    with something like this:</para>
-
-	  <programlisting>[boot loader]
-timeout=30
-default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
-[operating systems]
-multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT"
-C:\BOOTSECT.BSD="&os;"
-C:\="DOS"</programlisting>
-
-	  <para>If &os; is installed on the same disk as the
-	    &windowsnt; boot partition, copy
-	    <filename>/boot/boot1</filename> to
-	    <filename>C:\BOOTSECT.BSD</filename>.  However, if &os; is
-	    installed on a different disk
-	    <filename>/boot/boot1</filename> will not work,
-	    <filename>/boot/boot0</filename> is needed.</para>
-
-	  <para><filename>/boot/boot0</filename> needs to be installed
-	    using &man.sysinstall.8; by selecting the &os; boot
-	    manager on the screen which asks if you wish to use a boot
-	    manager.  This is because <filename>/boot/boot0</filename>
-	    has the partition table area filled with NULL characters
-	    but &man.sysinstall.8; copies the partition table before
-	    copying <filename>/boot/boot0</filename> to the
-	    MBR.</para>
-
-	  <warning>
-	    <para><emphasis>Do not copy
-		<filename>/boot/boot0</filename> instead of
-		<filename>/boot/boot1</filename> as this will overwrite
-		the partition table and render the computer
-		unbootable!</emphasis></para>
-	  </warning>
-
-	  <para>When the &os; boot manager runs it records the last OS
-	    booted by setting the active flag on the partition table
-	    entry for that OS and then writes the whole 512-bytes of
-	    itself back to the MBR so if you just copy
-	    <filename>/boot/boot0</filename> to
-	    <filename>C:\BOOTSECT.BSD</filename> then it writes an
-	    empty partition table, with the active flag set on one
-	    entry, to the MBR.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question xml:id="lilo-bootloader">
-	  <para>How do I boot &os; and &linux; from LILO?</para>
-	</question>
-
-	<answer>
-	  <para>If you have &os; and &linux; on the same disk, just
-	    follow LILO's installation instructions for booting a
-	    non-&linux; operating system.  Very briefly, these
-	    are:</para>
-
-	  <para>Boot &linux;, and add the following lines to
-	    <filename>/etc/lilo.conf</filename>:</para>
-
-	  <programlisting>other=/dev/hda2
-        table=/dev/hda
-        label=&os;</programlisting>
-
-	  <para>(the above assumes that your &os; slice is known to
-	    &linux; as <filename>/dev/hda2</filename>; tailor to
-	    suit your setup).  Then, run <command>lilo</command> as
-	    <systemitem class="username">root</systemitem> and you
-	    should be done.</para>
-
-	  <para>If &os; resides on another disk, you need to add
-	    <literal>loader=/boot/chain.b</literal> to the LILO entry.
-	    For example:</para>
-
-	  <programlisting>other=/dev/dab4
-        table=/dev/dab
-        loader=/boot/chain.b
-        label=&os;</programlisting>
-
-	  <para>In some cases you may need to specify the BIOS drive
-	    number to the &os; boot loader to successfully boot off
-	    the second disk.  For example, if your &os; SCSI disk is
-	    probed by BIOS as BIOS disk 1, at the &os; boot loader
-	    prompt you need to specify:</para>
-
-	  <screen>Boot: <userinput>1:da(0,a)/boot/kernel/kernel</userinput></screen>
-
-	  <para>You can configure &man.boot.8; to automatically do
-	    this for you at boot time.</para>
-
-	  <para>The <link
-	      xlink:href="http://tldp.org/HOWTO/Linux+FreeBSD.html">&linux;+&os;
-	      mini-HOWTO</link> is a good reference for &os; and
-	    &linux; interoperability issues.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question xml:id="grub-loader">
 	  <para>How do I boot &os; and &linux; using GRUB?</para>
 	</question>