Markup Fixes:

  Placed sh, bash, csh, tcsh in <command>
  Placed commands in <command>
  Placed options in <option>
  Placed several commands in man entities
  Placed several applications in <application>
  Placed make vars/targets into <makevar>/<maketarget>
  Placed filenames in <filename>
  <literal>chmod()</literal> -> <function>chmod()</function>

Standardize:
  ATT -> AT&amp;T
  endeavour -> endeavor
  tcl -> Tcl

Reviewed by:	murray

1 files changed, 31 insertions, 21 deletions

diff --git a/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml b/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
index 909ec5f3b5..4fa0e1ae57 100644
--- a/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.130 2001/07/04 18:22:36 jdp Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.131 2001/07/06 13:03:03 dd Exp $
 -->
 
 <appendix id="mirrors">
@@ -1351,7 +1351,7 @@
 	  automatic email.  The sizes of the updates are always kept as
 	  small as possible.  This is typically less than 5K, with an
 	  occasional (one in ten) being 10-50K and every now and then a
-	  biggie of 100K+ or more coming around.</para>
+	  large 100K+ or more coming around.</para>
 
 	<para>You will also need to make yourself aware of the various
 	  caveats related to working directly from the development sources
@@ -1400,7 +1400,7 @@
 
 	<para>Send email to &a.majordomo; to subscribe to one of the
 	  <application>CTM</application> distribution lists.
-	  &ldquo;ctm-cvs-cur&rdquo; supports the entire cvs tree.
+	  &ldquo;ctm-cvs-cur&rdquo; supports the entire CVS tree.
 	  &ldquo;ctm-src-cur&rdquo; supports the head of the development
 	  branch.  &ldquo;ctm-src-2_2&rdquo; supports the 2.2 release
 	  branch, etc..  (If you do not know how to subscribe yourself
@@ -1477,7 +1477,7 @@
 
 	<para><application>CTM</application> understands deltas which have
 	  been put through <command>gzip</command>, so you do not need to
-	  gunzip them first, this saves disk space.</para>
+	  <command>gunzip</command> them first, this saves disk space.</para>
 
 	<para>Unless it feels very secure about the entire process,
 	  <application>CTM</application> will not touch your tree.  To
@@ -1739,7 +1739,8 @@
 	system, which takes a substantial amount of time, memory, and
 	disk space to build.</para>
       
-      <para>If you do not know anything about cvsup at all and want a
+      <para>If you do not know anything about 
+	<application>CVSup</application> at all and want a
 	single package which will install it, set up the configuration
 	file and start the transfer via a pointy-clicky type of
 	interface, then get the <ulink
@@ -1861,9 +1862,10 @@
 
 	  <para>With <application>CVSup</application>, you can receive
 	    virtually any version of the sources that ever existed.
-	    That is possible because the cvsupd server works directly
-	    from the CVS repository, which contains all of the versions.
-	    You specify which one of them you want using the
+	    That is possible because the
+	    <application>cvsupd</application> server works directly from
+	    the CVS repository, which contains all of the versions.  You
+	    specify which one of them you want using the
 	    <literal>tag=</literal> and <option>date=</option> value
 	    fields.</para>
 	  
@@ -1871,7 +1873,8 @@
 	    <para>Be very careful to specify any <literal>tag=</literal>
 	      fields correctly.  Some tags are valid only for certain
 	      collections of files.  If you specify an incorrect or
-	      misspelled tag, CVSup will delete files which you probably
+	      misspelled tag, <application>CVSup</application>
+	      will delete files which you probably
 	      do not want deleted.  In particular, use <emphasis>only
 	      </emphasis> <literal>tag=.</literal> for the
 	      <literal>ports-*</literal> collections.</para>
@@ -2127,7 +2130,8 @@
 	  <programlisting>*default host=cvsup666.FreeBSD.org</programlisting>
 	  
 	  <para>You will need to change the host to one that actually
-	    exists before running CVSup.  On any particular run of
+	    exists before running <application>CVSup</application>.
+	    On any particular run of
 	    <command>cvsup</command>, you can override the host  setting
 	    on the command line, with <option>-h
 	      <replaceable>hostname</replaceable></option>.</para>
@@ -2152,7 +2156,8 @@
 	  <para><anchor id="cvsup-config-status">Where should
 	    <command>cvsup</command> maintain its status files?</para>
 
-	  <para>The cvsup client maintains certain status files in what
+	  <para>The <application>CVSup</application> client maintains
+	    certain status files in what
 	    is called the <quote>base</quote> directory.  These files
 	    help <application>CVSup</application> to work more
 	    efficiently, by keeping track of which updates you have
@@ -2339,11 +2344,13 @@ src-all</programlisting>
       
       <screen>&prompt.root; <userinput>cvsup -g -L 2 supfile</userinput></screen>
 	    
-      <para>The <option>-g</option> tells cvsup not to use its GUI.
-	This is automatic if you are not running X11, but otherwise you
-	have to specify it.</para>
+      <para>The <option>-g</option> tells
+	<application>CVSup</application> not to use its GUI.  This is
+	automatic if you are not running X11, but otherwise you have to
+	specify it.</para>
       
-      <para>The <option>-L 2</option> tells cvsup to print out the
+      <para>The <option>-L 2</option> tells 
+	<application>CVSup</application> to print out the
 	details of all the file updates it is doing.  There are three
 	levels of verbosity, from <option>-L 0</option> to
 	<option>-L 2</option>.  The default is 0, which means total
@@ -2354,9 +2361,10 @@ src-all</programlisting>
 	detailed descriptions, see the manual page.</para>
 
       <para>Once you are satisfied with the way updates are working, you
-	can arrange for regular runs of cvsup using &man.cron.8;.
-	Obviously, you should not let cvsup use its GUI when running it
-	from cron.</para>
+	can arrange for regular runs of <application>CVSup</application>
+	using &man.cron.8;.
+	Obviously, you should not let <application>CVSup</application>
+	use its GUI when running it from &man.cron.8;.</para>
     </sect2>
 
     <sect2 id="cvsup-collec">
@@ -3083,8 +3091,9 @@ src-all</programlisting>
 	  <term><literal>distrib release=self</literal></term>
 
 	  <listitem>
-	    <para>The CVSup server's own configuration files.  Used by
-	      CVSup mirror sites.</para>
+	    <para>The <application>CVSup</application> server's own 
+	      configuration files.  Used by <application>CVSup</application>
+	      mirror sites.</para>
 	  </listitem>
 	</varlistentry>
 
@@ -3118,7 +3127,8 @@ src-all</programlisting>
     <sect2>
       <title>For more information</title>
 
-      <para>For the CVSup FAQ and other information about CVSup, see
+      <para>For the <application>CVSup</application> FAQ and other 
+	information about <application>CVSup</application>, see
 	<ulink url="http://www.polstra.com/projects/freeware/CVSup/">The
 	  CVSup Home Page</ulink>.</para>