Begin editorial review of Subversion chapter.

Move mirrors into this chapter and rename rsync chapter to match the
rest of the ToC for this section.
Add an introductory paragraph on what this chapter covers.
More commits to come.

Sponsored by:	iXsystems

1 files changed, 45 insertions, 37 deletions

diff --git a/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml b/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml
index f9a4f9996c..bed0b76841 100644
--- a/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml
@@ -422,35 +422,28 @@ Comment out for now until these can be verified.
     <sect2 xml:id="svn-intro">
       <title>Introduction</title>
 
-      <para>As of July 2012, &os; uses <link
-	  xlink:href="http://subversion.apache.org/">Subversion</link>
-	(<emphasis>svn</emphasis>) as the primary version control
+      <para>As of July 2012, &os; uses
+	<application>Subversion</application>
+	as the primary version control
 	system for storing all of &os;'s source code, documentation,
 	and the Ports Collection.</para>
 
       <note>
-	<para>Subversion is generally a developer tool.  Most users
-	  should use <link
-	    linkend="updating-upgrading-freebsdupdate">FreeBSD
-	    Update</link> to update the &os; base system, and <link
-	    linkend="ports-using">Portsnap</link> to
+	<para><application>Subversion</application> is generally a developer tool.  Most users
+	  should use <command>freebsd-update</command> (<xref
+	    linkend="updating-upgrading-freebsdupdate"/>) to update
+	  the &os; base system, and <command>portsnap</command> (<link
+	    linkend="ports-using"/> to
 	  update the &os; Ports Collection.</para>
       </note>
 
-      <para>In <application>Subversion</application>, URLs are used to
-	designate a repository, taking the form of
-	<replaceable>protocol://hostname/path</replaceable>.  Mirrors
-	may support different protocols as specified below.  The first
-	component of the path is the &os; repository to access.  There
-	are three different repositories, <literal>base</literal> for
-	the &os; base system source code, <literal>ports</literal> for
-	the Ports Collection, and <literal>doc</literal> for
-	documentation.  For example, the URL
-	<literal>svn://svn0.us-east.FreeBSD.org/ports/head/</literal>
-	specifies the main branch of the ports repository on the
-	<systemitem
-	  class="fqdomainname">svn0.us-east.FreeBSD.org</systemitem>
-	mirror, using the <literal>svn</literal> protocol.</para>
+      <para>This chapter demonstrates how to install
+	<application>Subversion</application> on a &os; system and then
+	use it to create a local copy of a &os; repository.  It
+	includes a list of the available &os;
+	<application>Subversion</application> mirrors and resources to
+	additional information on how to use
+	<application>Subversion</application>.</para>
     </sect2>
 
     <sect2 xml:id="svn-install">
@@ -495,6 +488,21 @@ Comment out for now until these can be verified.
 	  repository.</para>
       </warning>
 
+      <para><application>Subversion</application> uses
+	<acronym>URL</acronym>s to designate a repository, taking the form of
+	<replaceable>protocol://hostname/path</replaceable>.  Mirrors
+	may support different protocols as specified below.  The first
+	component of the path is the &os; repository to access.  There
+	are three different repositories, <literal>base</literal> for
+	the &os; base system source code, <literal>ports</literal> for
+	the Ports Collection, and <literal>doc</literal> for
+	documentation.  For example, the URL
+	<literal>svn://svn0.us-east.FreeBSD.org/ports/head/</literal>
+	specifies the main branch of the ports repository on the
+	<systemitem
+	  class="fqdomainname">svn0.us-east.FreeBSD.org</systemitem>
+	mirror, using the <literal>svn</literal> protocol.</para>
+
       <para>A checkout from a given repository is performed with a
 	command like this:</para>
 
@@ -586,20 +594,7 @@ Comment out for now until these can be verified.
 &prompt.root; <userinput>make update SVN_UPDATE=yes</userinput></screen>
     </sect2>
 
-    <sect2>
-      <title>For More Information</title>
-
-      <para>For other information about using
-	<application>Subversion</application>, please see the
-	<quote>Subversion Book</quote>, titled
-	<link xlink:href="http://svnbook.red-bean.com/">Version
-	  Control with Subversion</link>, or the <link
-	  xlink:href="http://subversion.apache.org/docs/">Subversion
-	  Documentation</link>.</para>
-    </sect2>
-  </sect1>
-
-  <sect1 xml:id="svn-mirrors">
+  <sect2 xml:id="svn-mirrors">
     <title><application>Subversion</application> Mirror Sites</title>
 
     <indexterm>
@@ -730,10 +725,23 @@ Certificate information:
       or other problems, <literal>svn</literal> is the next choice,
       with slightly faster transfers.  When neither can be used, use
       <literal>http</literal>.</para>
+  </sect2>
+
+    <sect2>
+      <title>For More Information</title>
+
+      <para>For other information about using
+	<application>Subversion</application>, please see the
+	<quote>Subversion Book</quote>, titled
+	<link xlink:href="http://svnbook.red-bean.com/">Version
+	  Control with Subversion</link>, or the <link
+	  xlink:href="http://subversion.apache.org/docs/">Subversion
+	  Documentation</link>.</para>
+    </sect2>  
   </sect1>
 
   <sect1 xml:id="mirrors-rsync">
-    <title><application>rsync</application> Sites</title>
+    <title>Using <application>rsync</application></title>
 
     <para>The following sites make &os; available through the rsync
       protocol.  The <application>rsync</application> utility works in