[dpdk-stable] patch 'doc: fix spelling' has been queued to stable release 20.11.3

[luca.boccassi@gmail.com]

Hi,

FYI, your patch has been queued to stable release 20.11.3

Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 08/05/21. So please
shout if anyone has objections.

Also note that after the patch there's a diff of the upstream commit vs the
patch applied to the branch. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.

Queued patches are on a temporary branch at:
https://github.com/bluca/dpdk-stable

This queued commit can be viewed at:
https://github.com/bluca/dpdk-stable/commit/cf52376b2d082868aa1b3dd7dbb910b8be0324bb

Thanks.

Luca Boccassi

---
From cf52376b2d082868aa1b3dd7dbb910b8be0324bb Mon Sep 17 00:00:00 2001
From: Henry Nadeau <hnadeau@iol.unh.edu>
Date: Thu, 29 Jul 2021 12:48:05 -0400
Subject: [PATCH] doc: fix spelling

[ upstream commit 9c30a6f3c9a456e8111a2b1e5f6c2c02a62025b6 ]

Spell checked and corrected documentation.
If there are any errors, or I have changed something that wasn't an error
please reach out to me so I can update the dictionary.

Signed-off-by: Henry Nadeau <hnadeau@iol.unh.edu>
---
 doc/guides/contributing/coding_style.rst        | 2 +-
 doc/guides/cryptodevs/scheduler.rst             | 2 +-
 doc/guides/howto/pvp_reference_benchmark.rst    | 2 +-
 doc/guides/nics/bnx2x.rst                       | 2 +-
 doc/guides/nics/dpaa.rst                        | 6 +++---
 doc/guides/nics/mlx5.rst                        | 2 +-
 doc/guides/nics/octeontx2.rst                   | 4 ++--
 doc/guides/nics/virtio.rst                      | 2 +-
 doc/guides/platform/dpaa.rst                    | 2 +-
 doc/guides/prog_guide/bbdev.rst                 | 2 +-
 doc/guides/prog_guide/env_abstraction_layer.rst | 2 +-
 doc/guides/prog_guide/eventdev.rst              | 2 +-
 doc/guides/prog_guide/multi_proc_support.rst    | 2 +-
 doc/guides/prog_guide/qos_framework.rst         | 2 +-
 doc/guides/prog_guide/regexdev.rst              | 2 +-
 doc/guides/rawdevs/ioat.rst                     | 2 +-
 doc/guides/rawdevs/ntb.rst                      | 2 +-
 doc/guides/regexdevs/features_overview.rst      | 2 +-
 doc/guides/rel_notes/release_16_11.rst          | 2 +-
 doc/guides/rel_notes/release_19_08.rst          | 2 +-
 doc/guides/rel_notes/release_2_2.rst            | 2 +-
 doc/guides/sample_app_ug/fips_validation.rst    | 2 +-
 doc/guides/sample_app_ug/ipsec_secgw.rst        | 2 +-
 doc/guides/sample_app_ug/performance_thread.rst | 2 +-
 doc/guides/testpmd_app_ug/run_app.rst           | 2 +-
 doc/guides/testpmd_app_ug/testpmd_funcs.rst     | 4 ++--
 doc/guides/tools/hugepages.rst                  | 6 +++---
 27 files changed, 33 insertions(+), 33 deletions(-)

diff --git a/doc/guides/contributing/coding_style.rst b/doc/guides/contributing/coding_style.rst
index bb3f3efcbc..a2a8130c6b 100644
--- a/doc/guides/contributing/coding_style.rst
+++ b/doc/guides/contributing/coding_style.rst
@@ -55,7 +55,7 @@ License Header
 ~~~~~~~~~~~~~~
 
 Each file must begin with a special comment containing the
-`Software Package Data Exchange (SPDX) License Identfier <https://spdx.org/using-spdx-license-identifier>`_.
+`Software Package Data Exchange (SPDX) License Identifier <https://spdx.org/using-spdx-license-identifier>`_.
 
 Generally this is the BSD License, except for code granted special exceptions.
 The SPDX licences identifier is sufficient, a file should not contain
diff --git a/doc/guides/cryptodevs/scheduler.rst b/doc/guides/cryptodevs/scheduler.rst
index 835d999cfa..d08207f2e1 100644
--- a/doc/guides/cryptodevs/scheduler.rst
+++ b/doc/guides/cryptodevs/scheduler.rst
@@ -118,7 +118,7 @@ operation:
    than the designated threshold, otherwise it will be handled by the secondary
    worker.
 
-   A typical usecase in this mode is with the QAT cryptodev as the primary and
+   A typical use case in this mode is with the QAT cryptodev as the primary and
    a software cryptodev as the secondary worker. This may help applications to
    process additional crypto workload than what the QAT cryptodev can handle on
    its own, by making use of the available CPU cycles to deal with smaller
diff --git a/doc/guides/howto/pvp_reference_benchmark.rst b/doc/guides/howto/pvp_reference_benchmark.rst
index 553458ddce..484de3b7db 100644
--- a/doc/guides/howto/pvp_reference_benchmark.rst
+++ b/doc/guides/howto/pvp_reference_benchmark.rst
@@ -26,7 +26,7 @@ Setup overview
 
    PVP setup using 2 NICs
 
-In this diagram, each red arrow represents one logical core. This use-case
+In this diagram, each red arrow represents one logical core. This use case
 requires 6 dedicated logical cores. A forwarding configuration with a single
 NIC is also possible, requiring 3 logical cores.
 
diff --git a/doc/guides/nics/bnx2x.rst b/doc/guides/nics/bnx2x.rst
index 9ad4f9f410..788a6dac08 100644
--- a/doc/guides/nics/bnx2x.rst
+++ b/doc/guides/nics/bnx2x.rst
@@ -105,7 +105,7 @@ Jumbo: Limitation
 -----------------
 
 Rx descriptor limit for number of segments per MTU is set to 1.
-PMD doesn't support Jumbo Rx scatter gather. Some applciations can
+PMD doesn't support Jumbo Rx scatter gather. Some applications can
 adjust mbuf_size based on this param and max_pkt_len.
 
 For others, PMD detects the condition where Rx packet length cannot
diff --git a/doc/guides/nics/dpaa.rst b/doc/guides/nics/dpaa.rst
index 917482dbe2..7355ec3059 100644
--- a/doc/guides/nics/dpaa.rst
+++ b/doc/guides/nics/dpaa.rst
@@ -297,7 +297,7 @@ FMC - FMAN Configuration Tool
 
 
    The details can be found in FMC Doc at:
-   `Frame Mnager Configuration Tool <https://www.nxp.com/docs/en/application-note/AN4760.pdf>`_.
+   `Frame Manager Configuration Tool <https://www.nxp.com/docs/en/application-note/AN4760.pdf>`_.
 
 FMLIB
 ~~~~~
@@ -307,7 +307,7 @@ FMLIB
 
    This is an alternate to the FMC based configuration. This library provides
    direct ioctl based interfaces for FMAN configuration as used by the FMC tool
-   as well. This helps in overcoming the main limitaiton of FMC - i.e. lack
+   as well. This helps in overcoming the main limitation of FMC - i.e. lack
    of dynamic configuration.
 
    The location for the fmd driver as used by FMLIB and FMC is as follows:
@@ -319,7 +319,7 @@ VSP (Virtual Storage Profile)
    The storage profiled are means to provide virtualized interface. A ranges of
    storage profiles cab be associated to Ethernet ports.
    They are selected during classification. Specify how the frame should be
-   written to memory and which buffer pool to select for packet storange in
+   written to memory and which buffer pool to select for packet storage in
    queues. Start and End margin of buffer can also be configured.
 
 Limitations
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 78bf829fe5..84e58fc27b 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -1288,7 +1288,7 @@ the DPDK application.
 
         echo -n "<device pci address" > /sys/bus/pci/drivers/mlx5_core/unbind
 
-5. Enbale switchdev mode::
+5. Enable switchdev mode::
 
         echo switchdev > /sys/class/net/<net device>/compat/devlink/mode
 
diff --git a/doc/guides/nics/octeontx2.rst b/doc/guides/nics/octeontx2.rst
index a4f224424e..7b86cf5461 100644
--- a/doc/guides/nics/octeontx2.rst
+++ b/doc/guides/nics/octeontx2.rst
@@ -153,7 +153,7 @@ Runtime Config Options
 
       -a 0002:02:00.0,max_sqb_count=64
 
-   With the above configuration, each send queue's decscriptor buffer count is
+   With the above configuration, each send queue's descriptor buffer count is
    limited to a maximum of 64 buffers.
 
 - ``Switch header enable`` (default ``none``)
@@ -242,7 +242,7 @@ configure the following features:
 #. Hierarchical scheduling
 #. Single rate - Two color, Two rate - Three color shaping
 
-Both DWRR and Static Priority(SP) hierarchial scheduling is supported.
+Both DWRR and Static Priority(SP) hierarchical scheduling is supported.
 
 Every parent can have atmost 10 SP Children and unlimited DWRR children.
 
diff --git a/doc/guides/nics/virtio.rst b/doc/guides/nics/virtio.rst
index aabd0f1bce..1f0aba3207 100644
--- a/doc/guides/nics/virtio.rst
+++ b/doc/guides/nics/virtio.rst
@@ -509,7 +509,7 @@ are shown in below table:
    Split virtqueue in-order non-mergeable path  virtio_recv_pkts_inorder          virtio_xmit_pkts_inorder
    Split virtqueue vectorized Rx path           virtio_recv_pkts_vec              virtio_xmit_pkts
    Packed virtqueue mergeable path              virtio_recv_mergeable_pkts_packed virtio_xmit_pkts_packed
-   Packed virtqueue non-meregable path          virtio_recv_pkts_packed           virtio_xmit_pkts_packed
+   Packed virtqueue non-mergeable path          virtio_recv_pkts_packed           virtio_xmit_pkts_packed
    Packed virtqueue in-order mergeable path     virtio_recv_mergeable_pkts_packed virtio_xmit_pkts_packed
    Packed virtqueue in-order non-mergeable path virtio_recv_pkts_packed           virtio_xmit_pkts_packed
    Packed virtqueue vectorized Rx path          virtio_recv_pkts_packed_vec       virtio_xmit_pkts_packed
diff --git a/doc/guides/platform/dpaa.rst b/doc/guides/platform/dpaa.rst
index 20a0e39329..389692907d 100644
--- a/doc/guides/platform/dpaa.rst
+++ b/doc/guides/platform/dpaa.rst
@@ -78,7 +78,7 @@ compatible board:
    based config (if /tmp/fmc.bin is present). DPAA FMD will be used only if no
    previous fmc config is existing.
 
-   Note that fmlib based integratin rely on underlying fmd driver in kernel,
+   Note that fmlib based integration rely on underlying fmd driver in kernel,
    which is available as part of NXP kernel or NXP SDK.
 
 The following dependencies are not part of DPDK and must be installed
diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index 6b2bd54e1a..9619280ffc 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -639,7 +639,7 @@ optionally the ``soft_output`` mbuf data pointers.
    "soft output","soft LLR output buffer (optional)"
    "op_flags","bitmask of all active operation capabilities"
    "rv_index","redundancy version index [0..3]"
-   "iter_max","maximum number of iterations to perofrm in decode all CBs"
+   "iter_max","maximum number of iterations to perform in decode all CBs"
    "iter_min","minimum number of iterations to perform in decoding all CBs"
    "iter_count","number of iterations to performed in decoding all CBs"
    "ext_scale","scale factor on extrinsic info (5 bits)"
diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index 1f30e13b8b..d124eb0e9a 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -465,7 +465,7 @@ devices would fail anyway.
     - By default, the mempool, first asks for IOVA-contiguous memory using
       ``RTE_MEMZONE_IOVA_CONTIG``. This is slow in RTE_IOVA_PA mode and it may
       affect the application boot time.
-    - It is easy to enable large amount of IOVA-contiguous memory use-cases
+    - It is easy to enable large amount of IOVA-contiguous memory use cases
       with IOVA in VA mode.
 
     It is expected that all PCI drivers work in both RTE_IOVA_PA and
diff --git a/doc/guides/prog_guide/eventdev.rst b/doc/guides/prog_guide/eventdev.rst
index ccde086f63..347203f404 100644
--- a/doc/guides/prog_guide/eventdev.rst
+++ b/doc/guides/prog_guide/eventdev.rst
@@ -120,7 +120,7 @@ Ports
 ~~~~~
 
 Ports are the points of contact between worker cores and the eventdev. The
-general use-case will see one CPU core using one port to enqueue and dequeue
+general use case will see one CPU core using one port to enqueue and dequeue
 events from an eventdev. Ports are linked to queues in order to retrieve events
 from those queues (more details in `Linking Queues and Ports`_ below).
 
diff --git a/doc/guides/prog_guide/multi_proc_support.rst b/doc/guides/prog_guide/multi_proc_support.rst
index 6b0ac30c5b..815e8bdc43 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -325,7 +325,7 @@ supported. However, since sending messages (not requests) does not involve an
 IPC thread, sending messages while processing another message or request is
 supported.
 
-Since the memory sybsystem uses IPC internally, memory allocations and IPC must
+Since the memory subsystem uses IPC internally, memory allocations and IPC must
 not be mixed: it is not safe to use IPC inside a memory-related callback, nor is
 it safe to allocate/free memory inside IPC callbacks. Attempting to do so may
 lead to a deadlock.
diff --git a/doc/guides/prog_guide/qos_framework.rst b/doc/guides/prog_guide/qos_framework.rst
index 4e4ea33ccb..e403b90d74 100644
--- a/doc/guides/prog_guide/qos_framework.rst
+++ b/doc/guides/prog_guide/qos_framework.rst
@@ -737,7 +737,7 @@ Strict priority scheduling of traffic classes within the same pipe is implemente
 which selects the queues in ascending order.
 Therefore, queue 0 (associated with TC 0, highest priority TC) is handled before
 queue 1 (TC 1, lower priority than TC 0),
-which is handled before queue 2 (TC 2, lower priority than TC 1) and it conitnues until queues of all TCs except the
+which is handled before queue 2 (TC 2, lower priority than TC 1) and it continues until queues of all TCs except the
 lowest priority TC are handled. At last, queues 12..15 (best effort TC, lowest priority TC) are handled.
 
 Upper Limit Enforcement
diff --git a/doc/guides/prog_guide/regexdev.rst b/doc/guides/prog_guide/regexdev.rst
index 3d8b591b56..5ca7e0c769 100644
--- a/doc/guides/prog_guide/regexdev.rst
+++ b/doc/guides/prog_guide/regexdev.rst
@@ -124,7 +124,7 @@ The configuration mode is depended on the PMD capabilities.
 
 Online rule configuration is done using the following API functions:
 ``rte_regexdev_rule_db_update`` which add / remove rules from the rules
-precomplied list, and ``rte_regexdev_rule_db_compile_activate``
+precompiled list, and ``rte_regexdev_rule_db_compile_activate``
 which compile the rules and loads them to the RegEx HW.
 
 Offline rule configuration can be done by adding a pointer to the compiled
diff --git a/doc/guides/rawdevs/ioat.rst b/doc/guides/rawdevs/ioat.rst
index 250cfc48a6..59ba20740f 100644
--- a/doc/guides/rawdevs/ioat.rst
+++ b/doc/guides/rawdevs/ioat.rst
@@ -65,7 +65,7 @@ To assign an engine to a group::
         $ accel-config config-engine dsa0/engine0.1 --group-id=1
 
 To assign work queues to groups for passing descriptors to the engines a similar accel-config command can be used.
-However, the work queues also need to be configured depending on the use-case.
+However, the work queues also need to be configured depending on the use case.
 Some configuration options include:
 
 * mode (Dedicated/Shared): Indicates whether a WQ may accept jobs from multiple queues simultaneously.
diff --git a/doc/guides/rawdevs/ntb.rst b/doc/guides/rawdevs/ntb.rst
index 2c5fa7690c..2bb115d13f 100644
--- a/doc/guides/rawdevs/ntb.rst
+++ b/doc/guides/rawdevs/ntb.rst
@@ -17,7 +17,7 @@ some information by using scratchpad registers.
 BIOS setting on Intel Xeon
 --------------------------
 
-Intel Non-transparent Bridge needs special BIOS setting. The referencce for
+Intel Non-transparent Bridge needs special BIOS setting. The reference for
 Skylake is https://www.intel.com/content/dam/support/us/en/documents/server-products/Intel_Xeon_Processor_Scalable_Family_BIOS_User_Guide.pdf
 
 - Set the needed PCIe port as NTB to NTB mode on both hosts.
diff --git a/doc/guides/regexdevs/features_overview.rst b/doc/guides/regexdevs/features_overview.rst
index f90b394801..c512bde592 100644
--- a/doc/guides/regexdevs/features_overview.rst
+++ b/doc/guides/regexdevs/features_overview.rst
@@ -16,7 +16,7 @@ PCRE atomic grouping
   Support PCRE atomic grouping.
 
 PCRE back reference
-  Support PCRE back regerence.
+  Support PCRE back reference.
 
 PCRE back tracking ctrl
   Support PCRE back tracking ctrl.
diff --git a/doc/guides/rel_notes/release_16_11.rst b/doc/guides/rel_notes/release_16_11.rst
index 92e0ec694e..3cec9143cf 100644
--- a/doc/guides/rel_notes/release_16_11.rst
+++ b/doc/guides/rel_notes/release_16_11.rst
@@ -77,7 +77,7 @@ New Features
   the current version, even 64 bytes packets take two slots with Virtio PMD on guest
   side.
 
-  The main impact is better performance for 0% packet loss use-cases, as it
+  The main impact is better performance for 0% packet loss use cases, as it
   behaves as if the virtqueue size was enlarged, so more packets can be buffered
   in the case of system perturbations. On the downside, small performance degradations
   were measured when running micro-benchmarks.
diff --git a/doc/guides/rel_notes/release_19_08.rst b/doc/guides/rel_notes/release_19_08.rst
index cbb27e8dc3..d2baa828b1 100644
--- a/doc/guides/rel_notes/release_19_08.rst
+++ b/doc/guides/rel_notes/release_19_08.rst
@@ -151,7 +151,7 @@ New Features
   * Added multi-queue support to allow one af_xdp vdev with multiple netdev
     queues.
   * Enabled "need_wakeup" feature which can provide efficient support for the
-    usecase where the application and driver executing on the same core.
+    use case where the application and driver executing on the same core.
 
 * **Enabled infinite Rx in the PCAP PMD.**
 
diff --git a/doc/guides/rel_notes/release_2_2.rst b/doc/guides/rel_notes/release_2_2.rst
index cea5c8746d..8273473ff4 100644
--- a/doc/guides/rel_notes/release_2_2.rst
+++ b/doc/guides/rel_notes/release_2_2.rst
@@ -322,7 +322,7 @@ Drivers
 
   Several customers have reported a link flap issue on 82579. The symptoms
   are random and intermittent link losses when 82579 is connected to specific
-  switches. the Issue was root caused as an inter-operability problem between
+  switches. the Issue was root caused as an interoperability problem between
   the NIC and at least some Broadcom PHYs in the Energy Efficient Ethernet
   wake mechanism.
 
diff --git a/doc/guides/sample_app_ug/fips_validation.rst b/doc/guides/sample_app_ug/fips_validation.rst
index ca37fc0b38..56df434215 100644
--- a/doc/guides/sample_app_ug/fips_validation.rst
+++ b/doc/guides/sample_app_ug/fips_validation.rst
@@ -113,7 +113,7 @@ where,
   * mbuf-dataroom: By default the application creates mbuf pool with maximum
     possible data room (65535 bytes). If the user wants to test scatter-gather
     list feature of the PMD he or she may set this value to reduce the dataroom
-    size so that the input data may be dividied into multiple chained mbufs.
+    size so that the input data may be divided into multiple chained mbufs.
 
 
 To run the application in linux environment to test one AES FIPS test data
diff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_app_ug/ipsec_secgw.rst
index 176e292d3f..c07275e581 100644
--- a/doc/guides/sample_app_ug/ipsec_secgw.rst
+++ b/doc/guides/sample_app_ug/ipsec_secgw.rst
@@ -93,7 +93,7 @@ Additionally the event mode introduces two submodes of processing packets:
   protocol use case, the worker thread resembles l2fwd worker thread as the IPsec
   processing is done entirely in HW. This mode can be used to benchmark the raw
   performance of the HW. The driver submode is selected with --single-sa option
-  (used also by poll mode). When --single-sa option is used in conjution with event
+  (used also by poll mode). When --single-sa option is used in conjunction with event
   mode then index passed to --single-sa is ignored.
 
 * App submode: This submode has all the features currently implemented with the
diff --git a/doc/guides/sample_app_ug/performance_thread.rst b/doc/guides/sample_app_ug/performance_thread.rst
index 4c6a1dbe5c..9b09838f64 100644
--- a/doc/guides/sample_app_ug/performance_thread.rst
+++ b/doc/guides/sample_app_ug/performance_thread.rst
@@ -1176,7 +1176,7 @@ Tracing of events can be individually masked, and the mask may be programmed
 at run time. An unmasked event results in a callback that provides information
 about the event. The default callback simply prints trace information. The
 default mask is 0 (all events off) the mask can be modified by calling the
-function ``lthread_diagniostic_set_mask()``.
+function ``lthread_diagnostic_set_mask()``.
 
 It is possible register a user callback function to implement more
 sophisticated diagnostic functions.
diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
index 6f9ff1316b..d76eb1032e 100644
--- a/doc/guides/testpmd_app_ug/run_app.rst
+++ b/doc/guides/testpmd_app_ug/run_app.rst
@@ -112,7 +112,7 @@ The command line options are:
     Set the data size of the mbufs used to N bytes, where N < 65536.
     The default value is 2048. If multiple mbuf-size values are specified the
     extra memory pools will be created for allocating mbufs to receive packets
-    with buffer splittling features.
+    with buffer splitting features.
 
 *   ``--total-num-mbufs=N``
 
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index 3187756892..a004d897d5 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -1732,7 +1732,7 @@ List all items from the ptype mapping table::
 
 Where:
 
-* ``valid_only``: A flag indicates if only list valid items(=1) or all itemss(=0).
+* ``valid_only``: A flag indicates if only list valid items(=1) or all items(=0).
 
 Replace a specific or a group of software defined ptype with a new one::
 
@@ -4767,7 +4767,7 @@ Sample Raw encapsulation rule
 
 Raw encapsulation configuration can be set by the following commands
 
-Eecapsulating VxLAN::
+Encapsulating VxLAN::
 
  testpmd> set raw_encap 4 eth src is 10:11:22:33:44:55 / vlan tci is 1
         inner_type is 0x0800 / ipv4 / udp dst is 4789 / vxlan vni
diff --git a/doc/guides/tools/hugepages.rst b/doc/guides/tools/hugepages.rst
index 6d3f410b20..dd24c803de 100644
--- a/doc/guides/tools/hugepages.rst
+++ b/doc/guides/tools/hugepages.rst
@@ -62,7 +62,7 @@ Options
 
 .. warning::
 
-   While any user can run the ``dpdk-hugpages.py`` script to view the
+   While any user can run the ``dpdk-hugepages.py`` script to view the
    status of huge pages, modifying the setup requires root privileges.
 
 
@@ -71,8 +71,8 @@ Examples
 
 To display current huge page settings::
 
-   dpdk-hugpages.py -s
+   dpdk-hugepages.py -s
 
 To a complete setup of with 2 Gigabyte of 1G huge pages::
 
-   dpdk-hugpages.py -p 1G --setup 2G
+   dpdk-hugepages.py -p 1G --setup 2G
-- 
2.30.2

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2021-08-03 12:35:09.107329284 +0100
+++ 0023-doc-fix-spelling.patch	2021-08-03 12:35:08.262819688 +0100
@@ -1 +1 @@
-From 9c30a6f3c9a456e8111a2b1e5f6c2c02a62025b6 Mon Sep 17 00:00:00 2001
+From cf52376b2d082868aa1b3dd7dbb910b8be0324bb Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit 9c30a6f3c9a456e8111a2b1e5f6c2c02a62025b6 ]
+
@@ -10,2 +11,0 @@
-Cc: stable@dpdk.org
-
@@ -15 +14,0 @@
- doc/guides/cryptodevs/mlx5.rst                  | 4 ++--
@@ -22 +20,0 @@
- doc/guides/nics/txgbe.rst                       | 4 ++--
@@ -24 +21,0 @@
- doc/guides/platform/cnxk.rst                    | 2 +-
@@ -32 +28,0 @@
- doc/guides/prog_guide/toeplitz_hash_lib.rst     | 8 ++++----
@@ -38 +33,0 @@
- doc/guides/rel_notes/release_21_08.rst          | 2 +-
@@ -46 +41 @@
- 32 files changed, 43 insertions(+), 43 deletions(-)
+ 27 files changed, 33 insertions(+), 33 deletions(-)
@@ -49 +44 @@
-index 7601162c4f..d648689f10 100644
+index bb3f3efcbc..a2a8130c6b 100644
@@ -61,22 +55,0 @@
-diff --git a/doc/guides/cryptodevs/mlx5.rst b/doc/guides/cryptodevs/mlx5.rst
-index 908a25a98f..68bfdf3a83 100644
---- a/doc/guides/cryptodevs/mlx5.rst
-+++ b/doc/guides/cryptodevs/mlx5.rst
-@@ -99,7 +99,7 @@ The mlxreg dedicated tool should be used as follows:
-   The "wrapped_crypto_operational" value will be "0x00000001" if the mode was
-   successfully changed to operational mode.
- 
--  The mlx5 crypto PMD can be verfied by running the test application::
-+  The mlx5 crypto PMD can be verified by running the test application::
- 
-      dpdk-test -c 1 -n 1 -w <dev>,class=crypto,wcs_file=<file_path>
-      RTE>>cryptodev_mlx5_autotest
-@@ -130,7 +130,7 @@ Driver options
- 
- - ``keytag`` parameter [int]
- 
--  The plaintext of the keytag appanded to the AES-XTS keys, default value is 0.
-+  The plaintext of the keytag appended to the AES-XTS keys, default value is 0.
- 
- - ``max_segs_num`` parameter [int]
- 
@@ -154 +127 @@
-index a00793907f..3e9c736cae 100644
+index 78bf829fe5..84e58fc27b 100644
@@ -157 +130 @@
-@@ -1476,7 +1476,7 @@ the DPDK application.
+@@ -1288,7 +1288,7 @@ the DPDK application.
@@ -167 +140 @@
-index 258c1693fc..e35c8116f7 100644
+index a4f224424e..7b86cf5461 100644
@@ -188,22 +160,0 @@
-diff --git a/doc/guides/nics/txgbe.rst b/doc/guides/nics/txgbe.rst
-index 2c2b6549f1..47501796f2 100644
---- a/doc/guides/nics/txgbe.rst
-+++ b/doc/guides/nics/txgbe.rst
-@@ -86,7 +86,7 @@ TXGBE PMD provides the following log types available for control:
- 
- - ``pmd.net.txgbe.bp`` (default level is **notice**)
- 
--  Extra logging of auto-negtiation process for backplane NICs.
-+  Extra logging of auto-negotiation process for backplane NICs.
-   Supply ``--log-level=pmd.net.txgbe.bp:debug`` to view messages.
- 
- Runtime Options
-@@ -156,7 +156,7 @@ ingress or egress traffic, alter its fate and query related counters according
- to any number of user-defined rules.
- 
- A flow rule is the combination of attributes with a matching pattern and a list of
--actions. Theorically one rule can match more than one filters, which named for
-+actions. Theoretically one rule can match more than one filters, which named for
- different patterns and actions. Like ethertype filter defines a rule in pattern:
- the first not void item can be ETH, and the next not void item must be END.
- 
@@ -211 +162 @@
-index ac07d4d1e5..82ce7399ce 100644
+index aabd0f1bce..1f0aba3207 100644
@@ -223,13 +173,0 @@
-diff --git a/doc/guides/platform/cnxk.rst b/doc/guides/platform/cnxk.rst
-index 2325983604..d7adf43165 100644
---- a/doc/guides/platform/cnxk.rst
-+++ b/doc/guides/platform/cnxk.rst
-@@ -358,7 +358,7 @@ RPM example usage:
-         Packets received with FrameCheckSequenceErrors: 0
-         Packets received with VLAN header: 0
-         Error packets: 0
--        Packets recievd with unicast DMAC: 0
-+        Packets received with unicast DMAC: 0
-         Packets received with multicast DMAC: 0
-         Packets received with broadcast DMAC: 0
-         Dropped packets: 0
@@ -276 +214 @@
-index fda9c3743c..a49e486a30 100644
+index ccde086f63..347203f404 100644
@@ -279 +217 @@
-@@ -152,7 +152,7 @@ Ports
+@@ -120,7 +120,7 @@ Ports
@@ -302 +240 @@
-index 7d410d3cc6..3b8a1184b0 100644
+index 4e4ea33ccb..e403b90d74 100644
@@ -327,27 +264,0 @@
-diff --git a/doc/guides/prog_guide/toeplitz_hash_lib.rst b/doc/guides/prog_guide/toeplitz_hash_lib.rst
-index 83d5b0108f..f916857efc 100644
---- a/doc/guides/prog_guide/toeplitz_hash_lib.rst
-+++ b/doc/guides/prog_guide/toeplitz_hash_lib.rst
-@@ -41,7 +41,7 @@ but it expects ``rss_key`` to be converted to the host byte order.
- Predictable RSS
- ---------------
- 
--In some usecases it is useful to have a way to find partial collisions of the
-+In some use cases it is useful to have a way to find partial collisions of the
- Toeplitz hash function. In figure :numref:`figure_rss_queue_assign` only a few
- of the least significant bits (LSB) of the hash value are used to indicate an
- entry in the RSS Redirection Table (ReTa) and thus the index of the queue. So,
-@@ -178,10 +178,10 @@ It expects:
-   tuple, if the callback function returns an error.
- 
- 
--Usecase example
-----------------
-+Use case example
-+----------------
- 
--There could be a number of different usecases, such as NAT, TCP stack, MPLS
-+There could be a number of different use cases, such as NAT, TCP stack, MPLS
- tag allocation, etc. In the following we will consider a SNAT application.
- 
- Packets of a single bidirectional flow belonging to different directions can
@@ -355 +266 @@
-index 2ad13db294..a28e909935 100644
+index 250cfc48a6..59ba20740f 100644
@@ -419,13 +329,0 @@
-diff --git a/doc/guides/rel_notes/release_21_08.rst b/doc/guides/rel_notes/release_21_08.rst
-index 16bb9ce19e..c8b98ae878 100644
---- a/doc/guides/rel_notes/release_21_08.rst
-+++ b/doc/guides/rel_notes/release_21_08.rst
-@@ -152,7 +152,7 @@ New Features
- 
-   Added Baseband PHY PMD which allows to configure BPHY hardware block
-   comprising accelerators and DSPs specifically tailored for 5G/LTE inline
--  usecases. Configuration happens via standard rawdev enq/deq operations. See
-+  use cases. Configuration happens via standard rawdev enq/deq operations. See
-   the :doc:`../rawdevs/cnxk_bphy` rawdev guide for more details on this driver.
- 
- * **Added support for Marvell CN10K, CN9K, event Rx/Tx adapter.**
@@ -459 +357 @@
-index 2dc39aa50a..78171b25f9 100644
+index 176e292d3f..c07275e581 100644
@@ -485 +383 @@
-index eb48318353..6061674239 100644
+index 6f9ff1316b..d76eb1032e 100644
@@ -498 +396 @@
-index 2c43719ad3..4f8751be1c 100644
+index 3187756892..a004d897d5 100644
@@ -501 +399 @@
-@@ -1742,7 +1742,7 @@ List all items from the ptype mapping table::
+@@ -1732,7 +1732,7 @@ List all items from the ptype mapping table::
@@ -510 +408 @@
-@@ -4842,7 +4842,7 @@ Sample Raw encapsulation rule
+@@ -4767,7 +4767,7 @@ Sample Raw encapsulation rule