FIX: Small inconsistencies in report sections

[csit.git] / docs / report / vpp_functional_tests / overview.rst

diff --git a/docs/report/vpp_functional_tests/overview.rst b/docs/report/vpp_functional_tests/overview.rst
index e8f8460..1cd5def 100644 (file)
--- a/docs/report/vpp_functional_tests/overview.rst
+++ b/docs/report/vpp_functional_tests/overview.rst
@@ -5,14 +5,12 @@ Tested Virtual Topologies
 -------------------------\r
 \r
 CSIT VPP functional tests are executed on virtualized topologies created using\r
 -------------------------\r
 \r
 CSIT VPP functional tests are executed on virtualized topologies created using\r

-Virtual Internet Routing Lab (VIRL) simulation platform contributed by Cisco.\r
-VIRL runs on physical baremetal servers hosted by LF FD.io project.  Majority\r
-of the tests are executed in the three node logical test topology - Traffic\r
-Generator (TG) node and two Systems Under Test (SUT) nodes connected in a\r
-loop. Some tests use two node logical test topology - TG node and SUT1 node.\r
-Both logical test topologies are shown in the figures below.\r
-\r
-::\r
+:abbr:`VIRL (Virtual Internet Routing Lab)` simulation platform contributed by\r
+Cisco. VIRL runs on physical baremetal servers hosted by LF FD.io project.\r
+Majority of the tests are executed in the three node logical test topology -\r
+Traffic Generator (TG) node and two Systems Under Test (SUT) nodes connected in\r
+a loop. Some tests use two node logical test topology - TG node and SUT1 node.\r
+Both logical test topologies are shown in the figures below.::\r

 \r
     +------------------------+           +------------------------+\r
     |                        |           |                        |\r
 \r
     +------------------------+           +------------------------+\r
     |                        |           |                        |\r


@@ -68,9 +66,7 @@ For the test cases that require DUT (VPP) to communicate with VM over the
 vhost-user interfaces, a nested VM is created on SUT1 and/or SUT2 for the\r
 duration of these particular test cases only. DUT (VPP) test topology with VM\r
 is shown in the figure below including the applicable packet flow thru the VM\r
 vhost-user interfaces, a nested VM is created on SUT1 and/or SUT2 for the\r
 duration of these particular test cases only. DUT (VPP) test topology with VM\r
 is shown in the figure below including the applicable packet flow thru the VM\r

-(marked in the figure with ``***``).\r
-\r
-::\r
+(marked in the figure with ``***``).::\r

 \r
     +------------------------+           +------------------------+\r
     |      +----------+      |           |      +----------+      |\r
 \r
     +------------------------+           +------------------------+\r
     |      +----------+      |           |      +----------+      |\r


@@ -131,12 +127,11 @@ results listed in this report:
 Functional Tests Naming\r
 -----------------------\r
 \r
 Functional Tests Naming\r
 -----------------------\r
 \r

-CSIT |release| follows a common structured naming convention for all\r
-performance and system functional tests, introduced in CSIT |release-1|.\r
+CSIT |release| follows a common structured naming convention for all performance\r
+and system functional tests, introduced in CSIT rls1701.\r

 \r
 \r

-The naming should be intuitive for majority of the tests. Complete\r
-description of CSIT test naming convention is provided on \r
-`CSIT test naming wiki page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.\r
+The naming should be intuitive for majority of the tests. Complete description\r
+of CSIT test naming convention is provided on :ref:`csit_test_naming`..\r

 \r
 Here few illustrative examples of the new naming usage for functional test\r
 suites:\r
 \r
 Here few illustrative examples of the new naming usage for functional test\r
 suites:\r