VSPERF docs: Patches for Design Document

Routing Table Figure has an odd description
for the table#1 description.
Connectivity to the DUT is assumed, could provide
example directions. Suggest a new section.

JIRA: VSPERF-178
JIRA: VSPERF-179

Change-Id: I38e48034a9029d4a8969affdddef5b281dc8eba3
Signed-off-by: Radek Zetik <radekx.zetik@intel.com>
Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>
Reviewed-by: Brian Castelli <brian.castelli@spirent.com>
Reviewed-by: Al Morton <acmorton@att.com>
Reviewed-by: Tv Rao <tv.rao@freescale.com>

diff --git a/docs/design/vswitchperf_design.rst b/docs/design/vswitchperf_design.rst
index e139a02..4086cde 100755 (executable)
--- a/docs/design/vswitchperf_design.rst
+++ b/docs/design/vswitchperf_design.rst
@@ -12,6 +12,15 @@ deployment scenarios and so on.
 Usage
 =====
 
+Example Connectivity to DUT
+---------------------------
+
+Establish connectivity to the VSPERF DUT Linux host, such as the DUT in Pod 3,
+by following the steps in `Testbed POD3
+<https://wiki.opnfv.org/get_started/pod_3_-_characterize_vswitch_performance>`__
+
+The steps cover booking the DUT and establishing the VSPERF environment.
+
 Example Command Lines
 ---------------------
 
@@ -239,8 +248,8 @@ Frame Modification requirements.
              |
              |
              v
-      +--------------+  table#1 - Routing table. Flows to route packets between
-      |              |  ports goes here.
+      +--------------+  table#1 - Routing table. Flow entries to forward
+      |              |  packets between ports goes here.
       | Table 1      |  The chosen port is communicated to subsequent tables by
       |              |  setting the metadata value to the egress port number.
       |              |  Generally this table is set-up by by the