From 4f823975f45218c674b15ad1e9b84255eeabe08c Mon Sep 17 00:00:00 2001 From: Thomas Monjalon Date: Fri, 5 Nov 2021 22:10:30 +0100 Subject: [PATCH] doc: remove repeated repeated words Some duplicate words were detected with a script. Fixes: fdec9301f52d ("doc: add flow classify guides") Fixes: 4dc6d8e63c16 ("doc: add graph library guide") Fixes: 30d3aa861db5 ("doc: rework VM power manager user guide") Fixes: 0d547ed03717 ("examples/ipsec-secgw: support configuration file") Fixes: e64833f2273a ("examples/l2fwd-keepalive: add sample application") Cc: stable@dpdk.org Signed-off-by: Thomas Monjalon Acked-by: David Marchand --- doc/guides/prog_guide/flow_classify_lib.rst | 2 +- doc/guides/prog_guide/graph_lib.rst | 2 +- doc/guides/sample_app_ug/ipsec_secgw.rst | 2 +- doc/guides/sample_app_ug/keep_alive.rst | 2 +- doc/guides/sample_app_ug/vm_power_management.rst | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/guides/prog_guide/flow_classify_lib.rst b/doc/guides/prog_guide/flow_classify_lib.rst index f0ed5a1a04..7dae0bc8c6 100644 --- a/doc/guides/prog_guide/flow_classify_lib.rst +++ b/doc/guides/prog_guide/flow_classify_lib.rst @@ -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. diff --git a/doc/guides/prog_guide/graph_lib.rst b/doc/guides/prog_guide/graph_lib.rst index fcff9c4286..1cfdc86433 100644 --- a/doc/guides/prog_guide/graph_lib.rst +++ b/doc/guides/prog_guide/graph_lib.rst @@ -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. diff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_app_ug/ipsec_secgw.rst index 2304141ce8..c53ee7c386 100644 --- a/doc/guides/sample_app_ug/ipsec_secgw.rst +++ b/doc/guides/sample_app_ug/ipsec_secgw.rst @@ -443,7 +443,7 @@ where each options means: * *protect *: 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 ```` diff --git a/doc/guides/sample_app_ug/keep_alive.rst b/doc/guides/sample_app_ug/keep_alive.rst index b6d75c8a80..a907ff36a1 100644 --- a/doc/guides/sample_app_ug/keep_alive.rst +++ b/doc/guides/sample_app_ug/keep_alive.rst @@ -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`. diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst index 35afdac63f..7160b6a63a 100644 --- a/doc/guides/sample_app_ug/vm_power_management.rst +++ b/doc/guides/sample_app_ug/vm_power_management.rst @@ -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. -- 2.20.1