From ed3f7dd2f60a959baefbabffb687a9b92af804c2 Mon Sep 17 00:00:00 2001 From: Ali Alnubani Date: Tue, 1 Mar 2022 14:17:09 +0200 Subject: [PATCH] doc: fix typos and punctuation in flow API guide [ upstream commit 00373909c8f0377f03969eabf530293a7af9e23f ] This fixes typos and punctuation in the rte flow API guide. Fixes: 2f82d143fb31 ("ethdev: add group jump action") Fixes: 4d73b6fb9907 ("doc: add generic flow API guide") Signed-off-by: Ali Alnubani Acked-by: Ferruh Yigit --- doc/guides/prog_guide/rte_flow.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst index b182d310f0..10e6d06853 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -65,12 +65,12 @@ Flow rules can also be grouped, the flow rule priority is specific to the group they belong to. All flow rules in a given group are thus processed within the context of that group. Groups are not linked by default, so the logical hierarchy of groups must be explicitly defined by flow rules themselves in each -group using the JUMP action to define the next group to redirect too. Only flow -rules defined in the default group 0 are guarantee to be matched against, this +group using the JUMP action to define the next group to redirect to. Only flow +rules defined in the default group 0 are guaranteed to be matched against. This makes group 0 the origin of any group hierarchy defined by an application. Support for multiple actions per rule may be implemented internally on top -of non-default hardware priorities, as a result both features may not be +of non-default hardware priorities. As a result, both features may not be simultaneously available to applications. Considering that allowed pattern/actions combinations cannot be known in