svn commit: r41915 - head/en_US.ISO8859-1/articles/committers-guide

[Eitan Adler]

Author: eadler
Date: Wed Jun 12 21:01:43 2013
New Revision: 41915
URL: http://svnweb.freebsd.org/changeset/doc/41915

Log:
  Remove leftover references to svk.

Modified:
  head/en_US.ISO8859-1/articles/committers-guide/article.xml

Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/committers-guide/article.xml	Wed Jun 12 20:52:31 2013	(r41914)
+++ head/en_US.ISO8859-1/articles/committers-guide/article.xml	Wed Jun 12 21:01:43 2013	(r41915)
@@ -604,16 +604,13 @@
       <title>Daily Use</title>
 
       <para>This section will explain how to perform common day-to-day
-	operations with Subversion.  There should be no difference
-	between <acronym>SVN</acronym> and <acronym>SVK</acronym> in
-	daily use, except for the revision renumbering mentioned
-	earlier.</para>
+	operations with Subversion.</para>
 
       <sect3>
 	<title>Help</title>
 
-	<para>Both <acronym>SVN</acronym> and <acronym>SVK</acronym>
-	  have built in help documentation.  It can be accessed by
+	<para><acronym>SVN</acronym>
+	  has built in help documentation.  It can be accessed by
 	  typing the following command:</para>
 
 	<screen>&prompt.user; <userinput>svn help</userinput></screen>
@@ -725,7 +722,7 @@
 	<title>Editing and Committing</title>
 
 	<para>Unlike Perforce,
-	  <acronym>SVN</acronym> and <acronym>SVK</acronym> do not
+	  <acronym>SVN</acronym> does not
 	  need to be told in advance about file editing.</para>
 
 	<para><command>svn commit</command> works like the equivalent