bug 1177: auto generated man pages have error

doc/manual/source/attributes.rst

@@ -767,8 +767,8 @@ Ubuntu installation command is:::
 
     sudo apt-get install libgtk2.0-0 libgtk2.0-dev
 
-To check whether it is configured or not, check the output of the
-./waf configure --enable-examples --enable-tests step:::
+To check whether it is configured or not, check the output of the step:::
+./waf configure --enable-examples --enable-tests 
 
     ---- Summary of optional NS-3 features:
     Threading Primitives          : enabled

src/click/doc/click.rst

@@ -119,7 +119,7 @@ From any point within a Click graph, you may use the Print (http://read.cs.ucla.
    -> ToDump(out_arpquery,PER_NODE 1)
    -> ethout;
 
-...will print the contents of packets that flow out of the ArpQuerier, then generate a pcap trace file which will have a suffix 'out_arpquery', for each node using the Click file, before pushing packets onto 'ethout'.
+and ...will print the contents of packets that flow out of the ArpQuerier, then generate a pcap trace file which will have a suffix 'out_arpquery', for each node using the Click file, before pushing packets onto 'ethout'.
 
 Helper
 ======

src/mpi/doc/distributed.rst

@@ -125,7 +125,7 @@ Configure |ns3| with the --enable-mpi option:::
 Ensure that MPI is enabled by checking the optional features shown from the
 output of configure.
 
-Next, build |ns3|:
+Next, build |ns3|:::
 
     ./waf
 

src/network/doc/sockets-api.rst

@@ -125,16 +125,16 @@ sending of more data until a function registered at the
 :cpp:func:`ns3::Socket::SetSendCallback` callback is invoked.  
 An application can also ask the socket how much space is available 
 by calling :cpp:func:`ns3::Socket::GetTxAvailable`.  A typical sequence 
-of events for sending data (ignoring connection setup) might be:
+of events for sending data (ignoring connection setup) might be:::
 
-* ``SetSendCallback (MakeCallback(&HandleSendCallback));``
-* ``Send ();``
-* ``Send ();``
-* ...
-* Send fails because buffer is full
-* wait until :cpp:func:`HandleSendCallback` is called
-* :cpp:func:`HandleSendCallback` is called by socket, since space now available
-* ``Send (); // Start sending again``
+    * ``SetSendCallback (MakeCallback(&HandleSendCallback));``
+    * ``Send ();``
+    * ``Send ();``
+    * ...
+    * Send fails because buffer is full
+    * wait until :cpp:func:`HandleSendCallback` is called
+    * :cpp:func:`HandleSendCallback` is called by socket, since space now available
+    * ``Send (); // Start sending again``
 
 Similarly, on the receive side, the socket user does not block on
 a call to ``recv()``.  Instead, the application sets a callback