Index: chapter.xml
===================================================================
--- chapter.xml	(revision 47167)
+++ chapter.xml	(working copy)
@@ -436,13 +436,13 @@
       <title>Introduction</title>
 
       <para>As of July 2012, &os; uses
-	<application>Subversion</application> as the primary version
+	<application>Subversion</application> as the only version
 	control system for storing all of &os;'s source code,
 	documentation, and the Ports Collection.</para>
 
       <note>
 	<para><application>Subversion</application> is generally a
-	  developer tool.  Most users should use
+	  developer tool.  Users may prefer to use
 	  <command>freebsd-update</command> (<xref
 	    linkend="updating-upgrading-freebsdupdate"/>) to update
 	  the &os; base system, and <command>portsnap</command> (<xref
@@ -453,29 +453,54 @@
       <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
+	includes additional information on how to use
 	<application>Subversion</application>.</para>
     </sect2>
 
+    <sect2 xml:id="svn-svnlite">
+      <title>Svnlite</title>
+
+      <para>A fully functional but light weight version of
+	<application>Subversion</application> may be already installed
+	on your &os; system as <command>svnlite</command>.  You do not
+	have to install a separate copy if <command>svnlite</command>
+	is sufficient for your needs.</para>
+
+      <para>If you wish to access <acronym>HTTPS</acronym> servers with
+	<command>svnlite</command> then a root certificate bundle
+	should be installed:</para>
+
+      <screen>&prompt.root; <userinput>pkg install ca_root_nss</userinput></screen>
+
+      <para>Installing a certificate bundle allows
+	<command>svnlite</command> to verify that it is securely
+	communicating with the repository server without tampering.</para>
+
+      <para>If you are using <command>svnlite</command> then you should
+	adjust the examples below.</para>
+    </sect2>
+
     <sect2 xml:id="svn-install">
       <title>Installation</title>
 
-      <para><application>Subversion</application> must be installed
-	before it can be used to check out the contents of any of the
-	repositories.  If a copy of the ports tree is already present,
+      <para>If the <command>svnlite</command> is unavailable or you wish to
+	use the full version of <application>Subversion</application> then
+	it must be installed.</para>
+
+      <para>If a copy of the ports tree is already present,
 	one can install <application>Subversion</application> like
 	this:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/devel/subversion</userinput>
+&prompt.root; <userinput>make install clean</userinput>
+&prompt.root; <userinput>cd /usr/ports/security/ca_root_nss</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
-      <para>If the ports tree is not available,
-	<application>Subversion</application> can be installed as a
-	package:</para>
+      <para><application>Subversion</application> can easily be
+        installed as a package:</para>
 
-      <screen>&prompt.root; <userinput>pkg install devel/subversion</userinput></screen>
+      <screen>&prompt.root; <userinput>pkg install subversion</userinput>
+&prompt.root; <userinput>pkg install ca_root_nss</userinput></screen>
     </sect2>
 
     <sect2 xml:id="svn-usage">
@@ -561,7 +586,7 @@
       </itemizedlist>
 
       <para>This example checks out the Ports Collection from the
-	western US repository using the <acronym>HTTPS</acronym>
+	&os; repository using the <acronym>HTTPS</acronym>
 	protocol, placing the local working copy in
 	<filename>/usr/ports</filename>.  If
 	<filename>/usr/ports</filename> is already