Fix the spec format for dragonflow

Change-Id: I2bce060013a95c5901ec4f2f87f1a5ebe74a033b

doc/source/containers.rst

@@ -1,4 +1,4 @@
-============
+==========
 Containers
-============
+==========
 

doc/source/features.rst

@@ -1,6 +1,6 @@
-=========
+========
 Features
-=========
+========
 
 Dragonflow offers the following virtual network services:
 

doc/source/index.rst

@@ -29,7 +29,7 @@ Contents:
    releasenotes
 
 Dragonflow Specs
-=================
+================
 
 .. toctree::
    :maxdepth: 1

doc/source/installation.rst

@@ -17,9 +17,9 @@ Copy one of the following as your local.conf to your devstack folder
   ready to move packets.  You can see `Testing and Debugging
   <testing_and_debugging.rst>`_ to test and troubleshoot the deployment.
 
-============================================
- Automated setup using Vagrant + Virtualbox
-============================================
+==========================================
+Automated setup using Vagrant + Virtualbox
+==========================================
 
 This will create a 3 node devstack (controller + two computes), where Dragonflow is used as
 the Open vSwitch backend.

doc/source/releasenotes.rst

@@ -1,5 +1,5 @@
-===============
- Release Notes
-===============
+=============
+Release Notes
+=============
 
 .. release-notes::

doc/source/specs/allowed_address_pairs.rst

@@ -91,6 +91,5 @@ VMs mentioned above was detected.
 
 References
 ==========
-[1] http://specs.openstack.org/openstack/neutron-specs/specs/api/allowed_addr
-ess_pairs.html
+[1] http://specs.openstack.org/openstack/neutron-specs/specs/api/allowed_address_pairs.html
 [2] http://www.ietf.org/rfc/rfc3768.txt

doc/source/specs/igmp_application_and_multicast_support.rst

@@ -249,7 +249,7 @@ The IGMP-A may send periodic *Group-Specific Query* message to all local ports
 and synchronize its records.
 
 Synchronization across compute nodes
--------------------------------------
+------------------------------------
 
 The IGMP-A shares aggregated information with its peers (i.e. all multicast
 groups the compute node is registered to) by writing to the *Multicast* table

doc/source/specs/ipv6.rst

@@ -86,7 +86,7 @@ a dedicated spec will be written as it was done in `IPv4 Metadata Service <metad
 
 
 Neighbor Discovery
--------------------
+------------------
 
 Neighbor Discovery [#]_ relates to different protocols and processes known
 from IPv4 that have been modified and expanded. It combines Address

doc/source/specs/port_status_update.rst

@@ -4,9 +4,9 @@
 
 http://creativecommons.org/licenses/by/3.0/legalcode
 
-===================
+==================
 Port status update
-===================
+==================
 
 https://blueprints.launchpad.net/dragonflow/+spec/port-status-update
 
@@ -14,7 +14,7 @@ This blueprint describes how to support port status update for
 Dragonflow.
 
 Problem Description
-=====================
+===================
 Port status update feature will enable synchronization of port status
 between DF DB and neutron DB.
 

doc/source/specs/selective_topo_dist.rst

@@ -113,7 +113,7 @@ Subscriber may receive redundant event and store additional topology it will nev
 use.
 
 One topic per vpc or router
-"""""""""""""""""""""""""""""""
+"""""""""""""""""""""""""""
 Every vpc or router has its own topic. For isolated networks which don't connect
 to any routers, they also have their own topics. Changes in topology are published
 to the corresponding topics.

doc/source/specs/skeleton.rst

@@ -4,9 +4,9 @@
 
  http://creativecommons.org/licenses/by/3.0/legalcode
 
-==========================================
+=================
 Title of your RFE
-==========================================
+=================
 
 
 Problem Description

doc/source/usage.rst

@@ -1,6 +1,6 @@
-========
+=====
 Usage
-========
+=====
 
 To use dragonflow in a project::