Add titles

Issue-Id: DCAEGEN2-128
Change-Id: I0e4956e80b251a9dfaf0e08b789dd90104946a4c
Signed-off-by: Lusheng Ji <lji@research.att.com>

diff --git a/docs/sections/blueprints/PGaaS.rst b/docs/sections/blueprints/PGaaS.rst
index 5599c63..1b32d42 100644 (file)
--- a/docs/sections/blueprints/PGaaS.rst
+++ b/docs/sections/blueprints/PGaaS.rst
@@ -1,10 +1,12 @@
-= PostgreSQL as a Service
+PostgreSQL as a Service
+============
 
 PostgreSQL as a Service 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 Two Flavors?
+Why Two Flavors?
+------------
 
 The reason there are two flavors of blueprints lays in the difference in
 lifetime management of the constituent parts.

diff --git a/docs/sections/blueprints/example.rst b/docs/sections/blueprints/example.rst
index 47e52fd..642dfd3 100644 (file)
--- a/docs/sections/blueprints/example.rst
+++ b/docs/sections/blueprints/example.rst
@@ -1,19 +1,23 @@
-= My BluePrint Name
+My BluePrint Name
+======================
 
 Overview of my blueprint and the part it plays in DCAE.
 
-== Blue print files
+Blueprint files
+----------------------
 
 List where we can find the blueprints
 
-== Parameters 
+Parameters
+---------------------
 
 The input parameters needed for running the blueprint
 
-== How to run
+How To Run
+---------------------
 
 Cfy command for running the blueprint
 
-== Addiional information
-
+Additional Information
+---------------------
 Any additional information that help other people understanding and using yor blueprint