X-Git-Url: https://gerrit.fd.io/r/gitweb?p=csit.git;a=blobdiff_plain;f=docs%2Freport%2Fintroduction%2Fgeneral_notes.rst;h=994a53e6d0837d947ee801ac6038f82a848d42ef;hp=461e186f6df8ee2972e307c443d8da6f112ff779;hb=f4cd1c230a2328fd647fd88da5d9149fbad556e3;hpb=1749fc8da247a5aacd772b7f7b7353b3ee0733db

diff --git a/docs/report/introduction/general_notes.rst b/docs/report/introduction/general_notes.rst
index 461e186f6d..994a53e6d0 100644
--- a/docs/report/introduction/general_notes.rst
+++ b/docs/report/introduction/general_notes.rst
@@ -31,19 +31,18 @@ is listed separately, as follows:
    side). Tested across a range of multi-thread and multi-core
    configurations. TRex is used as a traffic generator.
 
-#. **Container Topologies Orchestrated by K8s - Performance** - CSIT
-   |release| introduced new tests of Container topologies connected over
-   the memif virtual interface (shared memory interface). For these tests
-   VPP vswitch instance runs in a Docker Container handling Intel x520 NIC
-   10GbE interfaces and connecting over memif (Master side) virtual
-   interfaces to more instances of VPP running in Docker Containers with
-   memif virtual interfaces (Slave side). All containers are orchestrated
-   by Kubernetes, with Ligato for container networking. TRex is used as a
-   traffic generator.
+#. **Container Topologies Orchestrated by K8s - Performance** - CSIT Container
+   topologies connected over the memif virtual interface (shared memory
+   interface). For these tests VPP vswitch instance runs in a Docker Container
+   handling Intel x520 NIC 10GbE interfaces and connecting over memif (Master
+   side) virtual interfaces to more instances of VPP running in Docker
+   Containers with memif virtual interfaces (Slave side). All containers are
+   orchestrated by Kubernetes, with `Ligato <https://github.com/ligato>`_ for
+   container networking. TRex is used as a traffic generator.
 
 #. **DPDK Performance** - VPP is using DPDK code to control and drive
-   the NICs and physical interfaces. Testpmd tests are used as a baseline to
-   profile the DPDK sub-system of VPP. DPDK performance tests executed in
+   the NICs and physical interfaces. Tests are used as a baseline to
+   profile performance of the DPDK sub-system. DPDK tests are executed in
    physical FD.io testbeds, focusing on Testpmd/L3FWD data plane performance for
    Phy-to-Phy (NIC-to-NIC). Tests cover a range of NICs, 10GE and 40GE
    interfaces, range of multi-thread and multi-core configurations.