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>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: [PATCH 05/11] doc: correct grammar in Intel platform guide
Date: Fri, 16 Jan 2026 13:06:21 -0800	[thread overview]
Message-ID: <20260116211649.104776-6-stephen@networkplumber.org> (raw)
In-Reply-To: <20260116211649.104776-1-stephen@networkplumber.org>

Change "take" to "taken" in passive construction.
Change "you wants" to "you want".
Rephrase awkward "If it wants" construction.
Change "drivers needs" to "drivers need" for subject-verb agreement.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 doc/guides/linux_gsg/nic_perf_intel_platform.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/guides/linux_gsg/nic_perf_intel_platform.rst b/doc/guides/linux_gsg/nic_perf_intel_platform.rst
index 4a5815dfb9..601d7bdc7a 100644
--- a/doc/guides/linux_gsg/nic_perf_intel_platform.rst
+++ b/doc/guides/linux_gsg/nic_perf_intel_platform.rst
@@ -82,7 +82,7 @@ You can use ``lspci`` to check the speed of a PCI slot using something like the
 
 When inserting NICs into PCI slots always check the caption, such as CPU0 or CPU1 to indicate which socket it is connected to.
 
-Care should be take with NUMA.
+Care should be taken with NUMA.
 If you are using 2 or more ports from different NICs, it is best to ensure that these NICs are on the same CPU socket.
 An example of how to determine this is shown further below.
 
@@ -101,7 +101,7 @@ so the following is mainly for reference:
 
 #. Consider using Turbo Boost to increase the frequency on cores.
 
-#. Disable all virtualization options when you test the physical function of the NIC, and turn on VT-d if you wants to use VFIO.
+#. Disable all virtualization options when you test the physical function of the NIC, and turn on VT-d if you want to use VFIO.
 
 
 Linux boot command line
@@ -119,7 +119,7 @@ The following are some recommendations on GRUB boot settings:
 
       isolcpus=2,3,4,5,6,7,8
 
-#. If it wants to use VFIO, use the following additional grub parameters::
+#. To use VFIO, use the following additional grub parameters::
 
       iommu=pt intel_iommu=on
 
@@ -181,5 +181,5 @@ Configurations before running DPDK
    **Note**: To get the best performance, ensure that the core and NICs are in the same socket.
    In the example above ``85:00.0`` is on socket 1 and should be used by cores on socket 1 for the best performance.
 
-#. Check which kernel drivers needs to be loaded and whether there is a need to unbind the network ports from their kernel drivers.
+#. Check which kernel drivers need to be loaded and whether there is a need to unbind the network ports from their kernel drivers.
    More details about DPDK setup and Linux kernel requirements see :ref:`linux_gsg_compiling_dpdk` and :ref:`linux_gsg_linux_drivers`.
-- 
2.51.0


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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 21:06 [PATCH 00/11] doc: Linux Getting Started Guide grammar and clarity improvements Stephen Hemminger
2026-01-16 21:06 ` [PATCH 01/11] doc: correct errors in Linux system requirements guide Stephen Hemminger
2026-01-16 21:06 ` [PATCH 02/11] doc: correct grammar in AMD platform guide Stephen Hemminger
2026-01-20  9:33   ` Varghese, Vipin
2026-01-16 21:06 ` [PATCH 03/11] doc: correct typos in DPDK build guide Stephen Hemminger
2026-01-16 21:06 ` [PATCH 04/11] doc: correct grammar in sample applications guide Stephen Hemminger
2026-01-16 21:06 ` Stephen Hemminger [this message]
2026-01-16 21:06 ` [PATCH 06/11] doc: correct word choice and redundant text in intro Stephen Hemminger
2026-01-16 21:06 ` [PATCH 07/11] doc: correct grammar in ARM64 cross-compile guide Stephen Hemminger
2026-01-16 21:06 ` [PATCH 08/11] doc: remove redundant text in documentation roadmap Stephen Hemminger
2026-01-16 21:06 ` [PATCH 09/11] doc: correct grammar and formatting in EAL arguments Stephen Hemminger
2026-01-16 21:06 ` [PATCH 10/11] doc: correct typos in enabling functionality guide Stephen Hemminger
2026-01-16 21:06 ` [PATCH 11/11] doc: correct grammar in Linux drivers guide Stephen Hemminger
2026-03-31 17:31 ` [PATCH 00/11] doc: Linux Getting Started Guide grammar and clarity improvements Thomas Monjalon

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=20260116211649.104776-6-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@huawei.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