Report: Improve docs related to TRex

Change-Id: I0ed346ff30c61d28b5a2232ef2f9d32d26c1ae2c
Signed-off-by: Vratko Polak <vrpolak@cisco.com>

2 files changed, 5 insertions, 2 deletions

diff --git a/docs/report/introduction/test_environment_changes_tg.rst b/docs/report/introduction/test_environment_changes_tg.rst
index 21175f2ba5..d21e43e04a 100644
--- a/docs/report/introduction/test_environment_changes_tg.rst
+++ b/docs/report/introduction/test_environment_changes_tg.rst
@@ -1,5 +1,5 @@
 To identify performance changes due to TRex code development between previous
-and current TRex  version, both have been tested in CSIT environment of latest
+and current TRex version, both have been tested in CSIT environment of latest
 version and compared against each other. All substantial progressions and
 regressions have been marked up with RCA analysis. See :ref:`trex_known_issues`.
 
diff --git a/docs/report/introduction/test_environment_intro.rst b/docs/report/introduction/test_environment_intro.rst
index 1999906669..c2feb1b4c4 100644
--- a/docs/report/introduction/test_environment_intro.rst
+++ b/docs/report/introduction/test_environment_intro.rst
@@ -10,9 +10,12 @@ CSIT test environment versioning has been introduced to track
 modifications of the test environment.
 
 Any benchmark anomalies (progressions, regressions) between releases of
-a DUT application (e.g. VPP, DPDK, TRex), are determined by testing it in the
+a DUT application (e.g. VPP, DPDK), are determined by testing it in the
 same test environment, to avoid test environment changes clouding the
 picture.
+To beter distinguish impact of test environment changes,
+we also execute tests without any SUT (just with TRex TG sending packets
+over a link looping back to TG).
 
 A mirror approach is introduced to determine benchmarking anomalies due
 to the test environment change. This is achieved by testing the same DUT