X-Git-Url: https://gerrit.fd.io/r/gitweb?p=csit.git;a=blobdiff_plain;f=docs%2Freport%2Fintroduction%2Fmethodology_trex_traffic_generator.rst;h=0d19c2cf78b0cfec1d716f4742823ae78f1f0051;hp=918a34f73deab35c9a5628e38b8f46b0447657ab;hb=c5e84fbee876a45d3495cde6f4e2d8140cacbe5a;hpb=ce1c52b1fd27d3e2b6c4909219fa98418565ba61

diff --git a/docs/report/introduction/methodology_trex_traffic_generator.rst b/docs/report/introduction/methodology_trex_traffic_generator.rst
index 918a34f73d..0d19c2cf78 100644
--- a/docs/report/introduction/methodology_trex_traffic_generator.rst
+++ b/docs/report/introduction/methodology_trex_traffic_generator.rst
@@ -13,7 +13,7 @@ TRex is installed and run on the TG compute node. The typical procedure
 is:
 
 - If the TRex is not already installed on TG, it is installed in the
-  suite setup phase - see `TRex intallation`_.
+  suite setup phase - see `TRex installation`_.
 - TRex configuration is set in its configuration file
   ::
 
@@ -22,7 +22,7 @@ is:
 - TRex is started in the background mode
   ::
 
-  $ sh -c 'cd <t-rex-install-dir>/scripts/ && sudo nohup ./t-rex-64 -i -c 7  > /tmp/trex.log 2>&1 &' > /dev/null
+  $ sh -c 'cd <t-rex-install-dir>/scripts/ && sudo nohup ./t-rex-64 -i -c 7 --prefix $(hostname) --hdrh > /tmp/trex.log 2>&1 &' > /dev/null
 
 - There are traffic streams dynamically prepared for each test, based on traffic
   profiles. The traffic is sent and the statistics obtained using