install manual last few sections format needs to be fixed

The last few sections of the manual do not have correct format. So
the document won't show the complete content when it is converted
to the html.

Change-Id: If1b1c64545460a24bf3071b4b3356b26c2478d76

doc/source/install/manual.rst

@@ -159,13 +159,13 @@ Installing the Compute Agent
    $ cd /opt/stack
    $ git clone https://git.openstack.org/openstack/ceilometer.git
 
-4. As a user with ``root`` permissions or ``sudo`` privileges, run the
+3. As a user with ``root`` permissions or ``sudo`` privileges, run the
    ceilometer installer::
 
    $ cd ceilometer
    $ sudo python setup.py install
 
-5. Copy the sample configuration files from the source tree
+4. Copy the sample configuration files from the source tree
    to their final location.
 
    ::
@@ -175,7 +175,7 @@ Installing the Compute Agent
       $ cp etc/ceilometer/*.yaml /etc/ceilometer
       $ cp etc/ceilometer/ceilometer.conf.sample /etc/ceilometer/ceilometer.conf
 
-6. Edit ``/etc/ceilometer/ceilometer.conf``
+5. Edit ``/etc/ceilometer/ceilometer.conf``
 
    1. Configure RPC
 
@@ -204,7 +204,7 @@ Installing the Compute Agent
    Refer to :doc:`/configuration` for details about any other options
    you might want to modify before starting the service.
 
-7. Start the agent.
+6. Start the agent.
 
    ::
 
@@ -360,13 +360,17 @@ Configuring keystone to work with API
 .. note::
    The API server needs to be able to talk to keystone to authenticate.
 
-1. Create a service for ceilometer in keystone::
+1. Create a service for ceilometer in keystone
+
+   ::
 
       $ keystone service-create --name=ceilometer \
                                 --type=metering \
                                 --description="Ceilometer Service"
 
-2. Create an endpoint in keystone for ceilometer::
+2. Create an endpoint in keystone for ceilometer
+
+   ::
 
       $ keystone endpoint-create --region RegionOne \
                                  --service_id $CEILOMETER_SERVICE \
@@ -396,12 +400,11 @@ Ceilometer, you should configure a separate queue that listens for the same
 messages.
 
 Using multiple dispatchers
-========================
+================================
 
 .. index::
    double: installing; multiple dispatchers
 
-.. note::
 The Ceilometer collector allows multiple dispatchers to be configured so that
 metering data can be easily sent to multiple internal and external systems.
 
@@ -416,14 +419,14 @@ Using multiple dispatchers
 eventually metering data will be saved in database. File dispatcher sends
 metering data into a file. The location, name, size of the file can be
 configured in ceilometer configuration file. These two dispatchers are
-   shipped in the Ceilometer egg and defined in the entry_points as follows:
+shipped in the Ceilometer egg and defined in the entry_points as follows::
 
    [ceilometer.dispatcher]
    file = ceilometer.collector.dispatcher.file:FileDispatcher
    database = ceilometer.collector.dispatcher.database:DatabaseDispatcher
 
 To use both dispatchers on a Ceilometer collector service, add the following
-   line in file ceilometer.conf
+line in file ceilometer.conf::
 
    [collector]
    dispatcher=database
@@ -431,7 +434,7 @@ Using multiple dispatchers
 
 If there is no dispatcher present, database dispatcher is used as the
 default. If in some cases such as traffic tests, no dispatcher is needed,
-   one can configure the line like the following:
+one can configure the line like the following::
 
    dispatcher=
 
@@ -440,7 +443,7 @@ Using multiple dispatchers
 
 
 Using other databases
-===================
+=========================
 .. index::
    double: installing; database, hbase, mysql, db2
 
@@ -455,6 +458,7 @@ Using other databases
    [database]
    connection = db2://username:password@host:27017/ceilometer
 
-   To use mongodb as the data reporitoy, make the section look like this::
+To use mongodb as the data repository, make the section look like this::
+
    [database]
    connection = mongodb://username:password@host:27017/ceilometer