Layout fixes to test case descriptions

Change-Id: I9658b023e4f3db7e22d67c71dfbba61511d981c6
Signed-off-by: Mika Rautakumpu <mika.rautakumpu@nokia.com>

3 files changed, 16 insertions, 11 deletions

diff --git a/docs/testing/user/userguide/opnfv_yardstick_tc056.rst b/docs/testing/user/userguide/opnfv_yardstick_tc056.rst
index e6e06df57..09b866c34 100644
--- a/docs/testing/user/userguide/opnfv_yardstick_tc056.rst
+++ b/docs/testing/user/userguide/opnfv_yardstick_tc056.rst
@@ -10,7 +10,7 @@ Yardstick Test Case Description TC056
 
 +-----------------------------------------------------------------------------+
 |OpenStack Controller Messaging Queue Service High Availability               |
-+==============+==============================================================+
++--------------+--------------------------------------------------------------+
 |test case id  | OPNFV_YARDSTICK_TC056:OpenStack Controller Messaging Queue   |
 |              | Service High Availability                                    |
 +--------------+--------------------------------------------------------------+
diff --git a/docs/testing/user/userguide/opnfv_yardstick_tc057.rst b/docs/testing/user/userguide/opnfv_yardstick_tc057.rst
index 2a4ce40c0..bb42b2aae 100644
--- a/docs/testing/user/userguide/opnfv_yardstick_tc057.rst
+++ b/docs/testing/user/userguide/opnfv_yardstick_tc057.rst
@@ -10,8 +10,11 @@ Yardstick Test Case Description TC057
 
 +-----------------------------------------------------------------------------+
 |OpenStack Controller Cluster Management Service High Availability            |
-+==============+==============================================================+
-|test case id  |                                                              |
+|                                                                             |
++--------------+--------------------------------------------------------------+
+|test case id  | OPNFV_YARDSTICK_TC057_HA: OpenStack Controller Cluster       |
+|              | Management Service High Availability                         |
+|              |                                                              |
 +--------------+--------------------------------------------------------------+
 |test purpose  | This test case will verify the quorum configuration of the   |
 |              | cluster manager(pacemaker) on controller nodes. When a       |
@@ -53,10 +56,11 @@ Yardstick Test Case Description TC057
 |              | "openstack-cmd" for this monitor.                            |
 |              | 2) command_name: which is the command name used for request  |
 |              |                                                              |
-|              | In this case, the command_name of monitor1 should be services|
-|              | that are managed by the cluster manager. (Since rabbitmq and |
-|              | haproxy are managed by pacemaker, most Openstack Services    |
-|              | can be used to check high availability in this case)         |
+|              | In this case, the command_name of monitor1 should be         |
+|              | services that are managed by the cluster manager.            |
+|              | (Since rabbitmq and haproxy are managed by pacemaker,        |
+|              | most Openstack Services can be used to check high            |
+|              | availability in this case)                                   |
 |              |                                                              |
 |              | (e.g.)                                                       |
 |              | monitor1:                                                    |
@@ -155,8 +159,8 @@ Yardstick Test Case Description TC057
 |              | Result: The test case is passed or not.                      |
 |              |                                                              |
 +--------------+------+----------------------------------+--------------------+
-|post-action   | It is the action when the test cases exist. It will check the|
-|              | status of the cluster messaging process(corosync) on the     |
+|post-action   | It is the action when the test cases exist. It will check    |
+|              | the status of the cluster messaging process(corosync) on the |
 |              | host, and restart the process if it is not running for next  |
 |              | test cases                                                   |
 +--------------+------+----------------------------------+--------------------+
diff --git a/docs/testing/user/userguide/opnfv_yardstick_tc058.rst b/docs/testing/user/userguide/opnfv_yardstick_tc058.rst
index fb9a4c2d1..7c323e913 100644
--- a/docs/testing/user/userguide/opnfv_yardstick_tc058.rst
+++ b/docs/testing/user/userguide/opnfv_yardstick_tc058.rst
@@ -10,8 +10,9 @@ Yardstick Test Case Description TC058
 
 +-----------------------------------------------------------------------------+
 |OpenStack Controller Virtual Router Service High Availability                |
-+==============+==============================================================+
-|test case id  | OPNFV_YARDSTICK_TC058:OpenStack Controller Virtual Router    |
+|                                                                             |
++--------------+--------------------------------------------------------------+
+|test case id  | OPNFV_YARDSTICK_TC058: OpenStack Controller Virtual Router   |
 |              | Service High Availability                                    |
 +--------------+--------------------------------------------------------------+
 |test purpose  | This test case will verify the high availability of virtual  |