- Grammar fixes;

- Many rewordings and punctuation changes to improve the content of
  this chapter;
- s/Berkeley Internet Name Daemon/Berkeley Internet Name Domain
- s/colon separated/colon-separated

PR:		docs/114265
Submitted by:	Ben Kaduk <minimarmot@gmail.com>

en_US.ISO8859-1/books/handbook/basics/chapter.sgml

@@ -558,7 +558,7 @@ total 530
 
     <para>A comma separated list can be provided when more than one set
       of changes to a file must be made.  For example the following command
-      will remove the groups and <quote>world</quote> write permission
+      will remove the group and <quote>world</quote> write permission
       on <replaceable>FILE</replaceable>, then it adds the execute
       permissions for everyone:</para>
 
@@ -618,7 +618,7 @@ total 530
 
       <para>Several flags may only added or removed to files by the
 	<username>root</username> user.  In other cases, the file owner
-	may set these flags.  It is recommended an administrator read
+	may set these flags.  It is recommended that administrators read
 	over the &man.chflags.1; and &man.chflags.2; manual pages for
 	more information.</para>
     </sect2>
@@ -634,11 +634,12 @@ total 530
       <quote>/</quote>.  This directory is the first one mounted at
       boot time and it contains the base system necessary to prepare
       the operating system for multi-user operation.  The root
-      directory also contains mount points for every other file system
+      directory also contains mount points for other file systems
-      that you may want to mount.</para>
+      that are mounted during the transition to multi-user
+      operation.</para>
 
     <para>A mount point is a directory where additional file systems can
-      be grafted onto the root file system.
+      be grafted onto a parent file system (usually the root file system).
       This is further described in <xref linkend="disk-organization">.
       Standard mount points include
       <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>,
@@ -1250,7 +1251,8 @@ total 530
 
       <para>When referring to a partition FreeBSD requires that you also name
 	the slice and disk that contains the partition, and when referring to
-	a slice you should also refer to the disk name.  Do this by listing
+	a slice you must also refer to the disk name.
+	Thus, you refer to a partition by listing
 	the disk name, <literal>s</literal>, the slice number, and then the
 	partition letter.  Examples are shown in 
 	<xref linkend="basics-disk-slice-part">.</para>
@@ -1357,7 +1359,7 @@ total 530
 	  two 2&nbsp;GB slices (&ms-dos; partitions).  The first slice contains a &ms-dos;
 	  disk, <devicename>C:</devicename>, and the second slice contains a
 	  FreeBSD installation.  This example FreeBSD installation has three
-	  partitions, and a swap partition.</para>
+	  data partitions, and a swap partition.</para>
 
 	<para>The three partitions will each hold a file system.  Partition
 	  <literal>a</literal> will be used for the root file system,
@@ -1738,7 +1740,8 @@ total 530
     <para>As you can see in this example, the output from &man.ps.1; is
       organized into a number of columns.  <literal>PID</literal> is the
       process ID discussed earlier.  PIDs are assigned starting from 1, go up
-      to 99999, and wrap around back to the beginning when you run out.
+      to 99999, and wrap around back to the beginning when you run out
+      (a PID is not reassigned if it is already in use).
       The <literal>TT</literal> column shows the tty the program is running on, and can
       safely be ignored for the moment.  <literal>STAT</literal> shows the
       program's state, and again, can be safely ignored.
@@ -1755,7 +1758,8 @@ total 530
       about all the running processes, not just your own.  <option>u</option>
       displays the username of the process' owner, as well as memory usage.
       <option>x</option> displays information about daemon processes, and
-      <option>ww</option> causes &man.ps.1; to display the full command line,
+      <option>ww</option> causes &man.ps.1; to display the full command line
+      for each process,
       rather than truncating it once it gets too long to fit on the
       screen.</para>
 
@@ -1815,32 +1819,32 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
       example of this class of application.</para>
 
     <para>We call these programs <firstterm>daemons</firstterm>.  Daemons were
-      characters in Greek mythology; neither good or evil, they were little
+      characters in Greek mythology: neither good or evil, they were little
-      attendant spirits that, by and large, did useful things for mankind.
+      attendant spirits that, by and large, did useful things for mankind,
-      Much like the web servers and mail servers of today do useful things.
+      much like the web servers and mail servers of today do useful things.
-      This is why the BSD mascot has, for a long time, been the cheerful
+      This is why the BSD mascot has, for a long time, been the
-      looking daemon with sneakers and a pitchfork.</para>
+      cheerful-looking daemon with sneakers and a pitchfork.</para>
 
     <para>There is a convention to name programs that normally run as daemons
       with a trailing <quote>d</quote>. <application>BIND</application> is the
-      Berkeley Internet Name Daemon (and the actual program that executes is called
+      Berkeley Internet Name Domain, but the actual program that executes is called
-      <command>named</command>), the <application>Apache</application> web
+      <command>named</command>; the <application>Apache</application> web
-      server program is called <command>httpd</command>, the line printer
+      server program is called <command>httpd</command>; the line printer
       spooling daemon is <command>lpd</command> and so on.  This is a
       convention, not a hard and fast rule; for example, the main mail daemon
       for the <application>Sendmail</application> application is called
       <command>sendmail</command>, and not <command>maild</command>, as you
       might imagine.</para>
 
-    <para>Sometimes you will need to communicate with a daemon process.  These
+    <para>Sometimes you will need to communicate with a daemon process.
-      communications are called <firstterm>signals</firstterm>, and you can
+      One way to do so is to send it (or any other running process),
-      communicate with a daemon (or with any other running process) by sending it a
+      what is known as a <firstterm>signal</firstterm>.
-      signal.  There are a number of different signals that you can
+      There are a number of different signals that you can
       send&mdash;some of them have a specific meaning, others are interpreted
       by the application, and the application's documentation will tell you
       how that application interprets signals.  You can only send a signal to
       a process that you own.  If you send a signal to someone else's
-      process with &man.kill.1; or &man.kill.2; permission will be denied.
+      process with &man.kill.1; or &man.kill.2;, permission will be denied.
       The exception to this is the
       <username>root</username> user, who can send signals to everyone's
       processes.</para>
@@ -1918,7 +1922,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
   198  ??  IWs    0:00.00 inetd -wW</screen>
 
 	<para>So the &man.inetd.8; PID is 198.  In some cases the
-	  <literal>grep inetd</literal> command might also occur in this
+	  <literal>grep inetd</literal> command might also appear in this
 	  output.  This is because of the way &man.ps.1; has to find the list
 	  of running processes.</para>
       </step>
@@ -1979,7 +1983,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
     <para>In FreeBSD, a lot of everyday work is done in a command line
       interface called a shell.  A shell's main job is to take commands
       from the input channel and execute them.  A lot of shells also have
-      built in functions to help everyday tasks such as file management,
+      built in functions to help with everyday tasks such as file management,
       file globbing, command line editing, command macros, and environment
       variables.  FreeBSD comes with a set of shells, such as 
       <command>sh</command>, the Bourne Shell, and <command>tcsh</command>, 
@@ -2018,7 +2022,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
     <indexterm><primary>environment variables</primary></indexterm>
 
     <para>Another feature of the shell is the use of environment variables.
-      Environment variables are a variable key pair stored in the shell's
+      Environment variables are a variable/key pair stored in the shell's
       environment space.  This space can be read by any program invoked by
       the shell, and thus contains a lot of program configuration.  Here
       is a list of common environment variables and what they mean:</para>
@@ -2041,7 +2045,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
 
 	  <row>
 	    <entry><envar>PATH</envar></entry>
-	    <entry>Colon separated list of directories to search for
+	    <entry>Colon-separated list of directories to search for
 	      binaries.</entry>
 	  </row>
 
@@ -2058,7 +2062,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
 
 	  <row>
 	    <entry><envar>TERM</envar></entry>
-	    <entry>The name of the user's terminal.  Used to determine the
+	    <entry>The name of the user's type of terminal.  Used to determine the
 	      capabilities of the terminal.</entry>
 	  </row>
 
@@ -2091,7 +2095,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
 
 	  <row>
 	    <entry><envar>MANPATH</envar></entry>
-	    <entry>Colon separated list of directories to search for
+	    <entry>Colon-separated list of directories to search for
 	      manual pages.</entry>
 	  </row>
 	</tbody>