Simplified diff for consideration.
I kept the change from "file sets" to "source files" as "file sets" has
special meaning in the OpenBSD installation process.
Also, only href the first instances of cvs(1).
Regards,
Index: anoncvs.html.head
===================================================================
RCS file: /cvs/www/build/mirrors/anoncvs.html.head,v
retrieving revision 1.42
diff -u -p -r1.42 anoncvs.html.head
--- anoncvs.html.head 2 Sep 2015 13:11:30 -0000 1.42
+++ anoncvs.html.head 14 Sep 2015 01:01:28 -0000
@@ -39,7 +39,7 @@ source repositories:
<ul>
<li><b>src</b> - Houses all source code for the OpenBSD Operating System.
<li><b>ports</b> - Houses the <a href="faq/ports/index.html">OpenBSD
Ports</a>.
- <li><b>www</b> - Houses all OpenBSD web pages. (Including this one).
+ <li><b>www</b> - Houses all OpenBSD web pages (including this one).
<li><b>xenocara</b> - Houses OpenBSD's active X.org v7 source tree.
<li><b>X11</b> and <b>XF4</b> - Houses OpenBSD's adaptation of the
<a href="http://www.XFree86.org/";>XFree86-3</a> and XFree86-4
@@ -135,17 +135,18 @@ Assuming the downloaded files, <tt>src.t
</pre>
<p>
-Not all people will wish to unpack all the file sets, but as the system
+Not all people will wish to unpack all the source files, but as the system
must be kept in sync, you will generally need to set up all trees.
<p>
-You can also just use cvs(1) to "<b>checkout</b>" the source repository
+You can also just use
+<a
href="http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/cvs.1?query=cvs
+to "<b>checkout</b>" the source repository
for you. This is discussed in the <a href="#using">next section</a>.
<p>
After this, <tt>/usr/src</tt> will be a nice checkout area where all
-<a
href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html";>
-cvs(1)</a> commands will work properly.
+cvs(1) commands will work properly.
<h3><a name="using"><font color="#0000e0">Using CVS to Get and Update your
Source Tree</font></a></h3>
@@ -166,10 +167,10 @@ CVS server you are going to use. A list
<p>
Once you have chosen which <a href="#CVSROOT">Anonymous CVS Server</a> you will
-use, you can start using cvs. For those of you
+use, you can start using cvs(1). For those of you
who have CDs you can start with the CVS checkout that is on the CD by using
the method <a href="#starting">above</a> to get the sources onto your system.
-If you don't have a CD handy, use the method below to checkout the sources.
+If you don't have a CD handy, use the method below to checkout the sources:
<p>
<ul><li>First, start out by `get'-ing an initial tree:
@@ -210,9 +211,11 @@ Confirm this, and the fingerprint will t
...
</pre>
+<p>
Note that the above format with SHA256 fingerprints was added after the
release of OpenBSD 5.6; older versions only use MD5 fingerprints.
+<p>
<li> Anytime afterwards, to `update' this tree:
<p> (If you are following <i>current</i>):
<pre>
@@ -234,7 +237,7 @@ to merge changes in.
<li> NOTE:
If you are updating a source tree that you initially fetched
from a different server, or from a CD, you <strong>must</strong>
-add the <em>-d [cvsroot]</em> option to cvs.
+add the <em>-d [cvsroot]</em> option to cvs:
<pre>
# <strong>cd /usr/src</strong>
# <strong>cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd</strong>
@@ -299,7 +302,7 @@ operation and get thoroughly involved in
before getting "commit" access -- as a result of showing useful
skills and high quality results they will naturally later be given
developer access.
-As well, people providing patches can create their "diff"s relative
+As well, people providing patches can create their diffs relative
to the CVS tree, which will ease integration.
<h3><a name="EXAMPLE"><font color="#0000e0">Example usages for cvs(1)</font>
