--- 43BSDReno/contrib/rcs/doc/rcs.ms	2018/04/24 16:12:56	1.1
+++ 43BSDReno/contrib/rcs/doc/rcs.ms	2018/04/24 16:12:56	1.1.1.1
@@ -250,19 +250,19 @@ RCS can stamp source and object code wit
 similar to product and serial numbers.
 To obtain such identification, place the marker
 .D(
-$Header: /var/lib/cvsd/CSRG/43BSDReno/contrib/rcs/doc/rcs.ms,v 1.1 2018/04/24 16:12:56 root Exp $
+$Header: /var/lib/cvsd/CSRG/43BSDReno/contrib/rcs/doc/rcs.ms,v 1.1.1.1 2018/04/24 16:12:56 root Exp $
 .D)
 into the text of a revision, for instance inside a comment.
 The check-out operation will replace this marker with a string of the form
 .D(
-$Header: /var/lib/cvsd/CSRG/43BSDReno/contrib/rcs/doc/rcs.ms,v 1.1 2018/04/24 16:12:56 root Exp $
+$Header: /var/lib/cvsd/CSRG/43BSDReno/contrib/rcs/doc/rcs.ms,v 1.1.1.1 2018/04/24 16:12:56 root Exp $
 .D)
 This string need never be touched, because \fIco\fR keeps it
 up to date automatically.
 To propagate the marker into object code, simply put
 it into a literal character string. In C, this is done as follows:
 .D(
-static char rcsid[] = "$Header: /var/lib/cvsd/CSRG/43BSDReno/contrib/rcs/doc/rcs.ms,v 1.1 2018/04/24 16:12:56 root Exp $";
+static char rcsid[] = "$Header: /var/lib/cvsd/CSRG/43BSDReno/contrib/rcs/doc/rcs.ms,v 1.1.1.1 2018/04/24 16:12:56 root Exp $";
 .D)
 The command \fIident\fR extracts such markers from any file, in particular from
 object code.
@@ -273,12 +273,12 @@ from which a copy of the program can be
 This facility is invaluable for program maintenance.
 .PP
 There are several additional identification markers, one for each component
-of $Header: /var/lib/cvsd/CSRG/43BSDReno/contrib/rcs/doc/rcs.ms,v 1.1 2018/04/24 16:12:56 root Exp $.
+of $Header: /var/lib/cvsd/CSRG/43BSDReno/contrib/rcs/doc/rcs.ms,v 1.1.1.1 2018/04/24 16:12:56 root Exp $.
 The marker
 .D(
 $Log: rcs.ms,v $
-Revision 1.1  2018/04/24 16:12:56  root
-Initial revision
+Revision 1.1.1.1  2018/04/24 16:12:56  root
+BSD 4.3reno
 
 .D)
 has a similar function. It accumulates
@@ -295,8 +295,8 @@ and makes it easy to determine what the
 .nf
 .in +0.5i
 /* $Log: rcs.ms,v $
- * Revision 1.1  2018/04/24 16:12:56  root
- * Initial revision
+ * Revision 1.1.1.1  2018/04/24 16:12:56  root
+ * BSD 4.3reno
  *
  * Revision 4.1  83/05/10  17:03:06  wft
  * Added option -d and -w, and updated assignment of date, etc. to new delta.
@@ -317,8 +317,8 @@ and makes it easy to determine what the
 .in 0
 .ce 1
 Figure 1. Log entries produced by the marker $Log: rcs.ms,v $
-Figure 1. Log entries produced by the marker Revision 1.1  2018/04/24 16:12:56  root
-Figure 1. Log entries produced by the marker Initial revision
+Figure 1. Log entries produced by the marker Revision 1.1.1.1  2018/04/24 16:12:56  root
+Figure 1. Log entries produced by the marker BSD 4.3reno
 Figure 1. Log entries produced by the marker.
 .fi
 .nr VS 18pts
@@ -330,8 +330,8 @@ each log message is
 physically stored once,
 independent of the number of revisions present.
 Thus, the $Log: rcs.ms,v $
-Thus, the Revision 1.1  2018/04/24 16:12:56  root
-Thus, the Initial revision
+Thus, the Revision 1.1.1.1  2018/04/24 16:12:56  root
+Thus, the BSD 4.3reno
 Thus, the marker incurs negligible space overhead.
 .NH
 The RCS Revision Tree