docs/72462: [PATCH] A few minor corrections to the hubs article

[Joel Dahl]

The following reply was made to PR docs/72462; it has been noted by GNATS.

From: Joel Dahl <joel at automatvapen.se>
To: freebsd-gnats-submit at FreeBSD.org
Cc:  
Subject: Re: docs/72462: [PATCH] A few minor corrections to the hubs article
Date: Wed, 23 Feb 2005 11:30:26 +0100

 --=-RTmaB6MsP8YcDDb77LtS
 Content-Type: text/plain
 Content-Transfer-Encoding: 7bit
 
 Uhh, I've totally forgot about this PR.  Better patch attached.
 
 --=-RTmaB6MsP8YcDDb77LtS
 Content-Disposition: attachment; filename=hubs.diff
 Content-Type: text/x-patch; name=hubs.diff; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Index: article.sgml
 ===================================================================
 RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/hubs/article.sgml,v
 retrieving revision 1.52
 diff -u -r1.52 article.sgml
 --- article.sgml	30 Sep 2004 09:41:45 -0000	1.52
 +++ article.sgml	23 Feb 2005 10:27:35 -0000
 @@ -335,7 +335,7 @@
            Generally there are two ways
            to access a CVS repository remotely: via
            <emphasis>pserver</emphasis> or via <command>ssh</command>
 -          (we don't consider <command>rsh</command>).
 +          (we do not consider <command>rsh</command>).
            For anonymous access, <emphasis>pserver</emphasis> is
            very well suited, but some still offer <command>ssh</command>
            access as well. There is a custom crafted
 @@ -346,7 +346,7 @@
            anonymous user's home-directory.   This may not be possible
            for all sites. If you just offer <emphasis>pserver</emphasis>
            this restriction does not apply, but you may run with
 -          more security risks. You don't need to install any special
 +          more security risks. You do not need to install any special
            software, since &man.cvs.1; comes with
            FreeBSD. You need to enable access via <command>inetd</command>,
            so add an entry into your <filename>/etc/inetd.conf</filename>
 @@ -602,7 +602,7 @@
          <filename role="package">textproc/docproj</filename> port must be
          installed.</para></note>
        <para>
 -        If you don't have a local repository, you can use
 +        If you do not have a local repository, you can use
          <application>CVSup</application> to maintain an <quote>up to date copy</quote>
          of the www pages. A sample supfile can be found in
          <filename>/usr/share/examples/cvsup/www-supfile</filename> and
 @@ -666,18 +666,18 @@
           environment variables, like
           <literal>SGML_CATALOG_FILES</literal>.
           Also have a look at your <filename>/etc/make.conf</filename>
 -         (copy <filename>/etc/defaults/make.conf</filename> if
 +         (copy <filename>/usr/share/examples/etc/make.conf</filename> if
           you do not have one), and look at the
           <literal>DOC_LANG</literal> variable.
           Now you are probably ready to run <command>make</command>
 -         in you doc directory (<filename>/usr/share/doc</filename>
 +         in your doc directory (<filename>/usr/share/doc</filename>
           by default) and build the documentation.
           Again you need to make it accessible for your web server
           and make sure the links point to the right location.
           <important>
             <para>
               The building of the documentation, as well as lots
 -             of side issues, is documented itself in:
 +             of side issues, is documented itself in the
               <ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/fdp-primer/">fdp-primer</ulink>.
               Please read this piece of documentation, especially if you
               have problems building the documentation.
 @@ -845,7 +845,7 @@
          </procedure>
        </sect3>
        <sect3 id="mirror-where-official">
 -        <title>I'm an official mirror, what is the right site for me?</title>
 +        <title>I am an official mirror, what is the right site for me?</title>
          <para>
            In general the description in <xref linkend="mirror-where-simple">
            still applies. Of course you may want to put some
 @@ -992,7 +992,7 @@
          </para>
          <para>
            It is also important that hub administrators try to keep their mirrors as up-to-date as
 -          possible (again, even more crucial for Tier-1 mirrors). If Mirror1 doesn't update for a
 +          possible (again, even more crucial for Tier-1 mirrors). If Mirror1 does not update for a
            while, lower tier mirrors will begin to mirror old data from Mirror1 and thus begins
            a downward spiral... Keep your mirrors up to date!
          </para>
 
 --=-RTmaB6MsP8YcDDb77LtS--