Minor fixes and corrections to tutorial formatting.
authorVedran Miletić <rivanvx@gmail.com>
Tue, 04 Dec 2012 13:56:31 +0100
changeset 9163 950db74a6484
parent 9162 b587372eb2de
child 9164 347452534b2e
Minor fixes and corrections to tutorial formatting.
doc/tutorial/source/conceptual-overview.rst
doc/tutorial/source/getting-started.rst
doc/tutorial/source/tracing.rst
--- a/doc/tutorial/source/conceptual-overview.rst	Tue Dec 04 13:55:59 2012 +0100
+++ b/doc/tutorial/source/conceptual-overview.rst	Tue Dec 04 13:56:31 2012 +0100
@@ -313,7 +313,7 @@
 ``Debugging`` book and then select the ``Logging`` page.
 
 You should now be looking at the Doxygen documentation for the Logging module.
-In the list of ``#define``s at the top of the page you will see the entry
+In the list of ``#define`` s at the top of the page you will see the entry
 for ``NS_LOG_COMPONENT_DEFINE``.  Before jumping in, it would probably be 
 good to look for the "Detailed Description" of the logging module to get a 
 feel for the overall operation.  You can either scroll down or select the
--- a/doc/tutorial/source/getting-started.rst	Tue Dec 04 13:55:59 2012 +0100
+++ b/doc/tutorial/source/getting-started.rst	Tue Dec 04 13:56:31 2012 +0100
@@ -53,6 +53,7 @@
 following into your Linux shell (assuming you have installed Mercurial):
 
 ::
+
   cd
   mkdir repos
   cd repos
@@ -220,7 +221,7 @@
 As mentioned above, one practice is to create a directory called ``repos``
 in one's home directory under which one can keep local Mercurial repositories.
 One could also keep a ``tarballs`` directory.  *Hint:  the tutorial
-will assume you downloaded into a ``repos`` directory, so remember the
+will assume you downloaded into a* ``repos`` *directory, so remember the
 placekeeper.*  If you adopt the ``tarballs`` directory approach, you can 
 get a copy of a release by typing the following into your Linux shell 
 (substitute the appropriate version numbers, of course):
--- a/doc/tutorial/source/tracing.rst	Tue Dec 04 13:55:59 2012 +0100
+++ b/doc/tutorial/source/tracing.rst	Tue Dec 04 13:56:31 2012 +0100
@@ -2342,7 +2342,7 @@
 
 The signature of this method reflects the device-centric view of the situation
 at this level.  All of the public methods inherited from class 
-2``PcapUserHelperForDevice`` reduce to calling this single device-dependent
+``PcapUserHelperForDevice`` reduce to calling this single device-dependent
 implementation method.  For example, the lowest level pcap method,
 
 ::