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>,
	Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: [PATCH 07/11] doc: correct grammar in ARM64 cross-compile guide
Date: Fri, 16 Jan 2026 13:06:23 -0800	[thread overview]
Message-ID: <20260116211649.104776-8-stephen@networkplumber.org> (raw)
In-Reply-To: <20260116211649.104776-1-stephen@networkplumber.org>

Change "files... is" to "files... are" for subject-verb agreement.
Use consistent spelling "toolchain" instead of "tool chain".
Change "distribution" to "distributions" for plural form.
Rephrase "Substitute <target_soc> with" for clarity.

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

diff --git a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
index e4de5c8d18..82dde17c35 100644
--- a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
+++ b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
@@ -44,7 +44,7 @@ NUMA is required by most modern machines, not needed for non-NUMA architectures.
    using the below guide. If you're using a different compiler,
    make sure you're using the proper executable name.
 
-The numa header files and lib file is generated in the include and lib folder
+The numa header files and lib file are generated in the include and lib folders
 respectively under ``<numa install dir>``.
 
 Meson prerequisites
@@ -185,7 +185,7 @@ provided the cross file has been modified accordingly::
 LLVM/Clang toolchain
 --------------------
 
-Obtain the cross tool chain
+Obtain the cross toolchain
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The latest LLVM/Clang cross compiler toolchain can be downloaded from:
@@ -236,7 +236,7 @@ use the following command to cross-compile DPDK for the target machine::
 Cross Compiling DPDK with LLVM/Clang toolchain using Meson on Ubuntu 18.04
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-On most popular Linux distribution it is not necessary to download
+On most popular Linux distributions, it is not necessary to download
 the toolchains, but rather use the packages provided by said distributions.
 On Ubuntu 18.04, these packages are needed:
 
@@ -260,7 +260,7 @@ option::
 
    meson setup soc_build -Dplatform=<target_soc>
 
-Substitute <target_soc> with one of the supported SoCs
+Replace <target_soc> with one of the supported SoCs.
 
 .. literalinclude:: ../../../config/arm/meson.build
    :start-after: Start of SoCs list
-- 
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 ` [PATCH 05/11] doc: correct grammar in Intel platform guide Stephen Hemminger
2026-01-16 21:06 ` [PATCH 06/11] doc: correct word choice and redundant text in intro Stephen Hemminger
2026-01-16 21:06 ` Stephen Hemminger [this message]
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-8-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=wathsala.vithanage@arm.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