diff --git a/en_US.ISO8859-1/articles/committers-guide/article.xml b/en_US.ISO8859-1/articles/committers-guide/article.xml
index df65cc3dea..5d4ec1a739 100644
--- a/en_US.ISO8859-1/articles/committers-guide/article.xml
+++ b/en_US.ISO8859-1/articles/committers-guide/article.xml
@@ -599,11 +599,14 @@ You need a Passphrase to protect your secret key.</screen>
 	  local repository's UUID has to occur before it is possible
 	  to start using it.</para>
 
-	<para>The hassle of a local
-	  <command>svnsync</command> mirror probably is not worth it
-	  unless the network connectivity situation or other factors
-	  demand it.  If it is needed, see the end of this chapter for
-	  information on how to set one up.</para>
+	<para>The hassle of a local <command>svnsync</command> mirror
+	  probably is not worth it unless the network connectivity
+	  situation or other factors demand it.  Starting
+	  a fresh mirror from empty takes a long time.
+	  Expect a minimum of 10 hours with high speed connectivity.
+	  If international links are involved, expect this to take
+	  four to ten times longer.  Another option is to use the
+	  git mirror.</para>
       </sect3>
 
       <sect3 xml:id="svn-getting-started-base-layout">
@@ -1860,52 +1863,6 @@ U    stable/9/share/man/man4/netmap.4
 	  This is a waste.</para>
       </sect3>
 
-      <sect3 xml:id="svn-advanced-use-setting-up-svnsync">
-	<title>Setting up a <application>svnsync</application>
-	  Mirror</title>
-
-	<para>Avoid setting up a <application>svnsync</application>
-	  mirror unless there is a very good reason for it.  Such
-	  reasons might be to support multiple local read-only client
-	  machines, or if the network bandwidth is limited.  Starting
-	  a fresh mirror from empty would take a very long time.
-	  Expect a minimum of 10 hours for high speed connectivity.
-	  If international links are involved, expect this to take
-	  four to ten times longer.</para>
-
-	<para>A far better option is to grab a seed file.  It is large
-	  (~1GB) but will consume less network traffic and take less
-	  time to fetch than a svnsync will.  There are several ways
-	  to do this:</para>
-
-	<screen>&prompt.user; <userinput>rsync -va --partial --progress freefall:/home/peter/svnmirror-base-r179637.tbz2 .</userinput></screen>
-
-	<screen>&prompt.user; <userinput>rsync -va --partial --progress rsync://repoman.freebsd.org:50873/svnseed/svnmirror-base-r215629.tar.xz .</userinput></screen>
-
-	<screen>&prompt.user; <userinput>fetch ftp://ftp.freebsd.org/pub/FreeBSD/development/subversion/svnmirror-base-r221445.tar.xz</userinput></screen>
-
-	<para>Extract the file to somewhere like
-	  <filename>home/svnmirror/base/</filename>.
-	  Then, update it, so that it fetches changes since the last
-	  revision in the archive:</para>
-
-	<screen>&prompt.user; <userinput>svnsync sync file:///home/svnmirror/base</userinput></screen>
-
-	<para>Now, set that up to run from &man.cron.8;, do
-	  checkouts locally, set up a svnserve server for local
-	  machines to talk to, etc.</para>
-
-	<para>The seed mirror is set to fetch from
-	  <literal>svn://svn.freebsd.org/base</literal>.  The
-	  configuration for the mirror is stored in
-	  <literal>revprop 0</literal> on the local mirror.  To see
-	  the configuration, try:</para>
-
-	<screen>&prompt.user; <userinput>svn proplist -v --revprop -r 0 file:///home/svnmirror/base</userinput></screen>
-
-	<para>Use <literal>propset</literal> to change things.</para>
-      </sect3>
-
       <sect3 xml:id="svn-advanced-use-committing-high-ascii-data">
 	<title>Committing High-<acronym>ASCII</acronym> Data</title>