Updating the formatting for APPC docs

Updated header formatting for docs

Issue-Id:  APPC-102
Change-Id: Id26a4c85c8d370088eb0d2aef5e9aaadc075f4ab
Signed-off-by: Scott Seabolt <js9808@att.com>
diff --git a/docs/APPC Client Library Guide/APPC Client Library Guide.rst b/docs/APPC Client Library Guide/APPC Client Library Guide.rst
index 7de54b3..37b8716 100644
--- a/docs/APPC Client Library Guide/APPC Client Library Guide.rst
+++ b/docs/APPC Client Library Guide/APPC Client Library Guide.rst
@@ -6,14 +6,13 @@
 
 
 Revision History
-----------------
+================
 
 +--------------+------------+---------------+--------------------------------------------------+
 | Date         | Revision   | Author        | Changes                                          |
 +--------------+------------+---------------+--------------------------------------------------+
 | 2017-08-22   | 1.0.0      | Paul Miller   | First draft                                      |
 +--------------+------------+---------------+--------------------------------------------------+
-+--------------+------------+---------------+--------------------------------------------------+
 
 Introduction
 ============
@@ -26,7 +25,9 @@
 Related Documentation
 ---------------------
 
-For additional information, see the ONAP Application Controller (APPC) API Guide.
+For additional information, see 
+
+	:ref:`appc_api_guide`
 
 
 Client Library Background
@@ -54,14 +55,16 @@
 
     |image0|
 
-**Asynchronous Flow**
+Asynchronous Flow
+^^^^^^^^^^^^^^^^^
 
 -  The APPC Client Library is called using an asynchronous API using a full command object, which is mapped to a JSON representation.
 -  The APPC client calls the UEB client and sends the JSON command to a configured topic.
 -  The APPC client pulls response messages from the configured topic.
 -  On receiving the response for the command, the APPC client runs the relevant callback method of the consumer ResponseHandler.
 
-**Synchronous Flow**
+Synchronous Flow
+^^^^^^^^^^^^^^^^
 
 -  The APPC Client Library is called using a synchronous API using a full command object, which is mapped to a JSON representation.
 -  The APPC client calls the UEB client and sends the JSON command to a configured topic.