Fix doc build warnings

[dcaegen2.git] / docs / sections / blueprints / PGaaS.rst

diff --git a/docs/sections/blueprints/PGaaS.rst b/docs/sections/blueprints/PGaaS.rst
index 080e575..eedcfe5 100644 (file)
--- a/docs/sections/blueprints/PGaaS.rst
+++ b/docs/sections/blueprints/PGaaS.rst
@@ -1,12 +1,12 @@
 PostgreSQL as a Service
-============
+=======================
 
 PostgreSQL as a Service (PGaaS) comes in two flavors: all-in-one blueprint, and
 separate disk/cluster/database blueprints to separate the management of
 the lifetime of those constituent parts. Both are provided for use.
 
 Why Three Flavors?
-------------
+------------------
 
 The reason there are three flavors of blueprints lays in the difference in
 lifetime management of the constituent parts and the number of VMs created.
@@ -24,10 +24,10 @@ be deployed too. OR, the database should have a lifetime beyond the scope
 of the applications that are writing to it or reading from it.
 
 Blueprint Files
-------------
+---------------
 
 The Blueprints for PG Services and Cinder
-^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 The all-in-one blueprint ``pgaas.yaml`` assumes that the PG servers and Cinder volumes can be allocated and
 deallocated together. The ``pgaas.yaml`` blueprint creates a cluster of two VMs named "``pstg``" by default. 
@@ -40,7 +40,7 @@ Cinder volume, and ``pgaas-cluster.yaml`` to allocate a PG cluster. Create the C
 redeployed without affecting the data on the Cinder volumes.
 
 The Blueprints for Databases
-^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 The ``pgaas-database.yaml`` blueprint shows how a database can be created separately from any application
 that uses it. That database will remain present until the pgaas-database.yaml blueprint is
@@ -56,7 +56,7 @@ adds the ``use_existing: true`` property.
 
 
 What is Created by the Blueprints
-^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Each PostgreSQL cluster has a name, represented below as ``${CLUSTER}`` or ``CLNAME``. Each cluster is created
 with two VMs, one VM used for the writable master and the other as a cascaded read-only secondary. 
@@ -84,7 +84,7 @@ How to Run
 
 
 To install the PostgreSQL as a Service
-^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Installing the all-in-one blueprint is straightforward: