Current wording regarding actions and flow rules doesn't make sense. Signed-off-by: Roy Franz <roy.fr...@cavium.com> --- Maybe a better word than 'assigned' could be chosen? (attached, associated with, etc) I'm happy to spin this if needed.
doc/guides/prog_guide/rte_flow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst index d158be5e4..9de6d32d3 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -984,7 +984,7 @@ Actions ~~~~~~~ Each possible action is represented by a type. Some have associated -configuration structures. Several actions combined in a list can be affected +configuration structures. Several actions combined in a list can be assigned to a flow rule. That list is not ordered. They fall in three categories: -- 2.11.0
