vcs: Minor cleanup to some code sections.

bfgroup · May 31, 2021 · d10082f · d10082f
1 parent 98d623d
commit d10082f
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/doc/src/vcs.rst b/doc/src/vcs.rst
@@ -72,9 +72,9 @@ Reference
 
    - Otherwise
 
-      - Git: <nearest-tag-name>-<branch-name>-<commits-since-nearest-tag>-g<commit-id>
+      - Git: ``<nearest-tag-name>-<branch-name>-<commits-since-nearest-tag>-g<commit-id>``
 
-      - Subversion: -<URL>--s<REV>
+      - Subversion: ``-<URL>--s<REV>``
 
    The ``generate-version-string`` rule can be used to generate a version
    string for a program dynamically.
@@ -149,7 +149,7 @@ Design
 
 The Boost.Build ``vcs`` module depends on separate backends to
 implement the interface.  The backend file should be named
-``vcs-BACKEND.jam`` where BACKEND is the name of the backend and
+``vcs-BACKEND.jam`` where ``BACKEND`` is the name of the backend and
 should contain implementations for each of the functions defined
 below.
 

diff --git a/doc/src/vcs.xml b/doc/src/vcs.xml
@@ -136,12 +136,12 @@ assert.equal [ vcs.ref /path/to/desired/root ] : [ vcs.ref /path/to/desired/root
                 <orderedlist>
                   <listitem>
                     <para>
-                      Git: &lt;nearest-tag-name&gt;-&lt;branch-name&gt;-&lt;commits-since-nearest-tag&gt;-g&lt;commit-id&gt;
+                      Git: <code>&lt;nearest-tag-name&gt;-&lt;branch-name&gt;-&lt;commits-since-nearest-tag&gt;-g&lt;commit-id&gt;</code>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      Subversion: -&lt;URL&gt;--s&lt;REV&gt;
+                      Subversion: <code>-&lt;URL&gt;--s&lt;REV&gt;</code>
                     </para>
                   </listitem>
                 </orderedlist>
@@ -312,7 +312,7 @@ assert.equal [ vcs.ref /path/to/desired/root ] : [ vcs.ref /path/to/desired/root
     <para>
       The Boost.Build <code>vcs</code> module depends on separate backends to
       implement the interface.  The backend file should be named
-      <code>vcs-BACKEND.jam</code> where BACKEND is the name of the backend and
+      <code>vcs-BACKEND.jam</code> where <code>BACKEND</code> is the name of the backend and
       should contain implementations for each of the functions defined
       below.
     </para>