d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc: remove repeated repeated words

Browse Source 
Some duplicate words were detected with a script.

Fixes: fdec9301f5 ("doc: add flow classify guides")
Fixes: 4dc6d8e63c ("doc: add graph library guide")
Fixes: 30d3aa861d ("doc: rework VM power manager user guide")
Fixes: 0d547ed037 ("examples/ipsec-secgw: support configuration file")
Fixes: e64833f227 ("examples/l2fwd-keepalive: add sample application")
Cc: stable@dpdk.org

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: David Marchand <david.marchand@redhat.com>
This commit is contained in:
Thomas Monjalon 2021-11-05 22:10:30 +01:00 committed by David Marchand
parent 25d45b391a
commit 4f823975f4
5 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/guides/prog_guide/flow_classify_lib.rst
View File

@ -366,7 +366,7 @@ Packet Matching
~~~~~~~~~~~~~~~
The ``rte_flow_classifier_query`` API is used to find packets which match a
given flow Flow rule in the table.
given flow rule in the table.
This API calls the flow_classify_run internal function which calls the
``table.ops.f_lookup`` API to see if any packets in a burst match any
of the Flow rules in the table.

2
doc/guides/prog_guide/graph_lib.rst
View File

@ -220,7 +220,7 @@ the user needs to update the context of the node hence access to
``struct rte_node *`` memory.
``rte_graph_foreach_node()``, ``rte_graph_node_get()``,
``rte_graph_node_get_by_name()`` APIs can be used to to get the
``rte_graph_node_get_by_name()`` APIs can be used to get the
``struct rte_node*``. ``rte_graph_foreach_node()`` iterator function works on
``struct rte_graph *`` fast-path graph object while others works on graph ID or name.

2
doc/guides/sample_app_ug/ipsec_secgw.rst
View File

@ -443,7 +443,7 @@ where each options means:
* *protect <SA_idx>*: the specified traffic is protected by SA rule
with id SA_idx
* *bypass*: the specified traffic traffic is bypassed
* *bypass*: the specified traffic is bypassed
* *discard*: the specified traffic is discarded
``<priority>``

2
doc/guides/sample_app_ug/keep_alive.rst
View File

@ -78,7 +78,7 @@ options.
Explanation
-----------
The following sections provide some explanation of the The
The following sections provide some explanation of the
Keep-Alive/'Liveliness' conceptual scheme. As mentioned in the
overview section, the initialization and run-time paths are very
similar to those of the :doc:`l2_forward_real_virtual`.

2
doc/guides/sample_app_ug/vm_power_management.rst
View File

@ -236,7 +236,7 @@ Compiling and Running the Host Application
Compiling the Host Application
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For information on compiling the DPDK and sample applications, see
For information on compiling the DPDK and sample applications,
see :doc:`compiling`.
The application is located in the ``vm_power_manager`` subdirectory.