CSIT-612 Report: Minimization of hand-crafted content.

[csit.git] / docs / report / introduction / csit_test_naming.rst

diff --git a/docs/report/introduction/csit_test_naming.rst b/docs/report/introduction/csit_test_naming.rst
index a4de765..682fcd9 100644 (file)
--- a/docs/report/introduction/csit_test_naming.rst
+++ b/docs/report/introduction/csit_test_naming.rst
@@ -5,12 +5,12 @@ Background
 ----------\r
 \r
 CSIT |release| follows a common structured naming convention for all\r
 ----------\r
 \r
 CSIT |release| follows a common structured naming convention for all\r

-performance and system functional tests, introduced in CSIT rls1701.\r
+performance and system functional tests, introduced in CSIT |release-1|.\r

 \r
 The naming should be intuitive for majority of the tests. Complete\r
 description of CSIT test naming convention is provided on\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>`_. Below\r
-few illustrative examples of the naming usage for test suites across CSIT\r
+`CSIT test naming wiki page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.\r
+Below few illustrative examples of the naming usage for test suites across CSIT\r

 performance, functional and HoneyComb management test areas.\r
 \r
 Naming Convention\r
 performance, functional and HoneyComb management test areas.\r
 \r
 Naming Convention\r