Static report content - Honeycomb

[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 13eab06..c88ec49 100644 (file)
--- a/docs/report/introduction/csit_test_naming.rst
+++ b/docs/report/introduction/csit_test_naming.rst
@@ -11,7 +11,7 @@ The naming should be intuitive for majority of the tests. Complete
 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
 Below few illustrative examples of the naming usage for test suites across CSIT\r
-performance, functional and HoneyComb management test areas.\r
+performance, functional and Honeycomb management test areas.\r
 \r
 Naming Convention\r
 -----------------\r
@@ -106,13 +106,13 @@ topologies:
    * *mgmt-cfg-lisp-apivat-func* => configuration of LISP with VAT API calls,\r
      functional tests.\r
    * *mgmt-cfg-l2bd-apihc-apivat-func* => configuration of L2 Bridge-Domain with\r
-     HoneyComb API and VAT API calls, functional tests.\r
+     Honeycomb API and VAT API calls, functional tests.\r
    * *mgmt-oper-int-apihcnc-func* => reading status and operational data of\r
-     interface with HoneyComb NetConf API calls, functional tests.\r
+     interface with Honeycomb NetConf API calls, functional tests.\r
    * *mgmt-cfg-int-tap-apihcnc-func* => configuration of tap interfaces with\r
-     HoneyComb NetConf API calls, functional tests.\r
+     Honeycomb NetConf API calls, functional tests.\r
    * *mgmt-notif-int-subint-apihcnc-func* => notifications of interface and\r
-     sub-interface events with HoneyComb NetConf Notifications, functional tests.\r
+     sub-interface events with Honeycomb NetConf Notifications, functional tests.\r
 \r
 For complete description of CSIT test naming convention please refer to `CSIT\r
 test naming wiki page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.\r