public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Ori Kam <orika@nvidia.com>
Subject: [PATCH 2/5] doc: correct grammar in rte_flow guide
Date: Fri, 16 Jan 2026 13:29:33 -0800	[thread overview]
Message-ID: <20260116213100.110419-3-stephen@networkplumber.org> (raw)
In-Reply-To: <20260116213100.110419-1-stephen@networkplumber.org>

Remove duplicate article "an" in phrase "a single an item".

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 doc/guides/prog_guide/ethdev/flow_offload.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/prog_guide/ethdev/flow_offload.rst b/doc/guides/prog_guide/ethdev/flow_offload.rst
index 1cd904e1ee..d51926a47c 100644
--- a/doc/guides/prog_guide/ethdev/flow_offload.rst
+++ b/doc/guides/prog_guide/ethdev/flow_offload.rst
@@ -109,7 +109,7 @@ However, ``rte_eth_dev_configure()`` may fail if any rules remain,
 so the application must flush them before attempting a reconfiguration.
 Keeping may be unsupported for some types of rule items and actions,
 as well as depending on the value of flow attributes transfer bit.
-A combination of a single an item or action type
+A combination of a single item or action type
 and a value of the transfer bit is called a rule feature.
 For example: a COUNT action with the transfer bit set.
 To test if rules with a particular feature are kept, the application must try
-- 
2.51.0


  parent reply	other threads:[~2026-01-16 21:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 21:29 [PATCH 0/5] doc: ethdev documentation grammar and typo corrections Stephen Hemminger
2026-01-16 21:29 ` [PATCH 1/5] doc: correct grammar and punctuation errors in ethdev guide Stephen Hemminger
2026-01-16 21:29 ` Stephen Hemminger [this message]
2026-01-16 21:29 ` [PATCH 3/5] doc: correct grammar in QoS framework guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 4/5] doc: correct typos in switch representation guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 5/5] doc: correct typos in traffic management guide Stephen Hemminger
2026-01-28 19:45 ` [PATCH v2 0/8] doc: ethdev documentation grammar and typo corrections Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 1/8] doc: correct grammar and punctuation errors in ethdev guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 2/8] doc: correct grammar in flow guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 3/8] doc: correct grammar in QoS framework guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 4/8] doc: correct typos in switch representation guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 5/8] doc: correct typos in traffic management guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 6/8] doc: correct grammar and improve clarity in ethdev guide Stephen Hemminger
2026-03-25 11:41     ` Thomas Monjalon
2026-01-28 19:46   ` [PATCH v2 7/8] doc: correct alphabetical ordering in ethdev toctree Stephen Hemminger
2026-03-25 11:45     ` Thomas Monjalon
2026-01-28 19:46   ` [PATCH v2 8/8] doc: correct grammar and improve clarity in MTR guide Stephen Hemminger
2026-02-05 21:29   ` [PATCH v2 0/8] doc: ethdev documentation grammar and typo corrections Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260116213100.110419-3-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox