- Fix copy/paste error in description of how to capture both rx
& tx traffic in a single pcap file
- Replace duplicate word with what original author presumably
intended, such that description now makes sense
Signed-off-by: Mark Kavanagh <mark.b.kavanagh at intel.com>
---
doc/guides/sample_app_ug/pdump.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/sample_app_ug/pdump.rst
b/doc/guides/sample_app_ug/pdump.rst
index ac0e7c9..320c914 100644
--- a/doc/guides/sample_app_ug/pdump.rst
+++ b/doc/guides/sample_app_ug/pdump.rst
@@ -119,8 +119,8 @@ Can be either a pcap file name or any Linux iface.
* To receive ingress and egress packets separately ``rx-dev`` and
``tx-dev``
should both be passed with the different file names or the Linux iface
names.
- * To receive ingress and egress packets separately ``rx-dev`` and
``tx-dev``
- should both be passed with the same file names or the the Linux iface
names.
+ * To receive ingress and egress packets together, ``rx-dev`` and
``tx-dev``
+ should both be passed with the same file name or the same Linux iface
name.
``ring-size``:
Size of the ring. This value is used internally for ring creation. The ring
will be used to enqueue the packets from
--
1.9.3
