Index: ch04-branching-and-merging.xml
===================================================================
--- ch04-branching-and-merging.xml	(revision 4831)
+++ ch04-branching-and-merging.xml	(working copy)
@@ -3858,12 +3858,26 @@
         let these same files live on in unused obscurity!)  Finally,
         once our <filename>current</filename> working copy contains
         only the libcomplex 1.1 code, we commit the changes we made to
-        get it looking that way.</para>
+        get it looking that way:</para>
 
+        <informalexample>
+        <screen>
+&hellip; # navigate to current libcomplex code which is from libcomplex-1.1.
+$ cd working-copies/vendor/libcomplex/current
+&hellip; # update files and somehow ensure everything matchs the libcomplex-1.1 vendor drop exactly. 
+$ svn commit -m "importing 1.1 vendor drop"
+&hellip; # tag the libcomplex-1.1 vendor drop
+$ svn copy http://svn.example.com/repos/vendor/libcomplex/current  \
+           http://svn.example.com/repos/vendor/libcomplex/1.1      \
+           -m "tagging libcomplex-1.1"
+&hellip;
+</screen>
+      </informalexample>
+
       <para>Our <filename>current</filename> branch now contains the
-        new vendor drop.  We tag the new version as 1.1 (in the same
-        way we previously tagged the version 1.0 vendor drop), and
-        then merge the differences between the tag of the previous
+        new vendor drop which was tagged with the new version as 1.1 (in the same
+        way we previously tagged the version 1.0 vendor drop). Now we will
+        merge the differences between the tag of the previous
         version and the new current version into our main development
         branch:</para>