From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A2C14A04F5 for ; Wed, 11 Dec 2019 22:28:30 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 986E11D9E; Wed, 11 Dec 2019 22:28:30 +0100 (CET) Received: from us-smtp-delivery-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.61]) by dpdk.org (Postfix) with ESMTP id 928551BE9D for ; Wed, 11 Dec 2019 22:28:29 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576099709; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DyI75U2pA++JJZGOlMImXZ7UdWPF0mWvPtNkvO2gaFg=; b=hzhELFmFkkqq7c8rIw8QUa2rEjCvIU/QGZTe7hyVPOC+A+8WpMOT3n93UhadEzYWoNl+Uk TfZmN2DFrWhE0x04wkP2AgNwQICC9/0LCuaPBaryOEUyVu4jXr6ZbP9MKt4ZBg/uK3s0f8 sRpShuYlee+UTSL0uNl4ase/t8SzuUQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-308-TjHOzOSsNvynZcYKgmc3dw-1; Wed, 11 Dec 2019 16:28:25 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BE9E818543A1 for ; Wed, 11 Dec 2019 21:28:24 +0000 (UTC) Received: from rh.redhat.com (ovpn-116-64.ams2.redhat.com [10.36.116.64]) by smtp.corp.redhat.com (Postfix) with ESMTP id 90A2E10013A1; Wed, 11 Dec 2019 21:28:23 +0000 (UTC) From: Kevin Traynor To: David Marchand Cc: Kevin Traynor , dpdk stable Date: Wed, 11 Dec 2019 21:26:20 +0000 Message-Id: <20191211212702.27851-28-ktraynor@redhat.com> In-Reply-To: <20191211212702.27851-1-ktraynor@redhat.com> References: <20191211212702.27851-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-MC-Unique: TjHOzOSsNvynZcYKgmc3dw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Subject: [dpdk-stable] patch 'doc/guides: clean repeated words' has been queued to LTS release 18.11.6 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to LTS release 18.11.6 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 12/17/19. 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 rebasi= ng (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/kevintraynor/dpdk-stable-queue This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable-queue/commit/98e4dae7d0a00b2ccb= c809983b3f0866f748044a Thanks. Kevin. --- >From 98e4dae7d0a00b2ccbc809983b3f0866f748044a Mon Sep 17 00:00:00 2001 From: David Marchand Date: Tue, 12 Nov 2019 20:33:41 +0100 Subject: [PATCH] doc/guides: clean repeated words [ upstream commit f43d3dbbd90c9e195d26d18ac7da9ca2854c3f1e ] Shoot repeated words in all our guides. Signed-off-by: David Marchand Acked-by: Kevin Traynor --- doc/guides/contributing/coding_style.rst | 8 ++++---- doc/guides/cryptodevs/zuc.rst | 2 +- doc/guides/linux_gsg/nic_perf_intel_platform.rst | 2 +- doc/guides/nics/fm10k.rst | 2 +- doc/guides/prog_guide/env_abstraction_layer.rst | 2 +- .../prog_guide/generic_segmentation_offload_lib.rst | 2 +- doc/guides/prog_guide/kernel_nic_interface.rst | 2 +- doc/guides/prog_guide/packet_classif_access_ctrl.rst | 4 ++-- doc/guides/prog_guide/rte_flow.rst | 2 +- doc/guides/prog_guide/rte_security.rst | 4 ++-- doc/guides/rel_notes/release_17_11.rst | 2 +- doc/guides/rel_notes/release_18_02.rst | 2 +- doc/guides/sample_app_ug/ethtool.rst | 2 +- doc/guides/sample_app_ug/performance_thread.rst | 2 +- doc/guides/testpmd_app_ug/testpmd_funcs.rst | 4 ++-- 15 files changed, 21 insertions(+), 21 deletions(-) diff --git a/doc/guides/contributing/coding_style.rst b/doc/guides/contribu= ting/coding_style.rst index 656563dde..b848be5fb 100644 --- a/doc/guides/contributing/coding_style.rst +++ b/doc/guides/contributing/coding_style.rst @@ -632,8 +632,8 @@ In the DPDK environment, use the logging interface prov= ided: /* log in debug level */ rte_log_set_global_level(RTE_LOG_DEBUG); - RTE_LOG(DEBUG, my_logtype1, "this is is a debug level message\n"); - RTE_LOG(INFO, my_logtype1, "this is is a info level message\n"); - RTE_LOG(WARNING, my_logtype1, "this is is a warning level message\n"); - RTE_LOG(WARNING, my_logtype2, "this is is a debug level message (not disp= layed)\n"); + RTE_LOG(DEBUG, my_logtype1, "this is a debug level message\n"); + RTE_LOG(INFO, my_logtype1, "this is a info level message\n"); + RTE_LOG(WARNING, my_logtype1, "this is a warning level message\n"); + RTE_LOG(WARNING, my_logtype2, "this is a debug level message (not display= ed)\n"); =20 /* log in info level */ diff --git a/doc/guides/cryptodevs/zuc.rst b/doc/guides/cryptodevs/zuc.rst index e38989968..dcd3ab0a5 100644 --- a/doc/guides/cryptodevs/zuc.rst +++ b/doc/guides/cryptodevs/zuc.rst @@ -29,5 +29,5 @@ Limitations * ZUC (EEA3) supported only if cipher length, cipher offset fields are byt= e-aligned. * ZUC PMD cannot be built as a shared library, due to limitations in - in the underlying library. + the underlying library. =20 =20 diff --git a/doc/guides/linux_gsg/nic_perf_intel_platform.rst b/doc/guides/= linux_gsg/nic_perf_intel_platform.rst index cf5c9e0db..4e9afbdbc 100644 --- a/doc/guides/linux_gsg/nic_perf_intel_platform.rst +++ b/doc/guides/linux_gsg/nic_perf_intel_platform.rst @@ -153,5 +153,5 @@ Configurations before running DPDK mount -t hugetlbfs nodev /mnt/huge =20 -2. Check the CPU layout using using the DPDK ``cpu_layout`` utility: +2. Check the CPU layout using the DPDK ``cpu_layout`` utility: =20 .. code-block:: console diff --git a/doc/guides/nics/fm10k.rst b/doc/guides/nics/fm10k.rst index 20a1cde53..4e178c2cc 100644 --- a/doc/guides/nics/fm10k.rst +++ b/doc/guides/nics/fm10k.rst @@ -120,5 +120,5 @@ Switch manager The Intel FM10000 family of NICs integrate a hardware switch and multiple = host interfaces. The FM10000 PMD driver only manages host interfaces. For the -switch component another switch driver has to be loaded prior to to the +switch component another switch driver has to be loaded prior to the FM10000 PMD driver. The switch driver can be acquired from Intel support. Only Testpoint is validated with DPDK, the latest version that has been diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/p= rog_guide/env_abstraction_layer.rst index 2bb77b019..a7536a80e 100644 --- a/doc/guides/prog_guide/env_abstraction_layer.rst +++ b/doc/guides/prog_guide/env_abstraction_layer.rst @@ -221,5 +221,5 @@ matter of supplying the correct socket ID to DPDK alloc= ator, either directly structure-specific allocation API's such as ``rte_ring_create``). =20 -Since there is no way DPDK can verify whether memory are is available or v= alid, +Since there is no way DPDK can verify whether memory is available or valid= , this responsibility falls on the shoulders of the user. All multiprocess synchronization is also user's responsibility, as well as ensuring that a= ll diff --git a/doc/guides/prog_guide/generic_segmentation_offload_lib.rst b/d= oc/guides/prog_guide/generic_segmentation_offload_lib.rst index 0cfc1198c..73e768740 100644 --- a/doc/guides/prog_guide/generic_segmentation_offload_lib.rst +++ b/doc/guides/prog_guide/generic_segmentation_offload_lib.rst @@ -207,5 +207,5 @@ To segment an outgoing packet, an application must: =20 - The GSO library use the value of an mbuf's ``ol_flags`` attribute to - to determine how a packet should be segmented. It is the application'= s + determine how a packet should be segmented. It is the application's responsibility to ensure that these flags are set. =20 diff --git a/doc/guides/prog_guide/kernel_nic_interface.rst b/doc/guides/pr= og_guide/kernel_nic_interface.rst index 9c1483adc..ccf03a41d 100644 --- a/doc/guides/prog_guide/kernel_nic_interface.rst +++ b/doc/guides/prog_guide/kernel_nic_interface.rst @@ -244,5 +244,5 @@ to create a separate thread or secondary process to per= iodically call The KNI interfaces can be deleted by a DPDK application with ``rte_kni_release()``. All KNI interfaces not explicitly deleted will be -deleted when the the ``/dev/kni`` device is closed, either explicitly with +deleted when the ``/dev/kni`` device is closed, either explicitly with ``rte_kni_close()`` or when the DPDK application is closed. =20 diff --git a/doc/guides/prog_guide/packet_classif_access_ctrl.rst b/doc/gui= des/prog_guide/packet_classif_access_ctrl.rst index 395b3ec47..9e08a8e3f 100644 --- a/doc/guides/prog_guide/packet_classif_access_ctrl.rst +++ b/doc/guides/prog_guide/packet_classif_access_ctrl.rst @@ -155,5 +155,5 @@ To define classification for the IPv6 2-tuple: o .. code-block:: c =20 - struct struct ipv6_hdr { + struct ipv6_hdr { uint32_t vtc_flow; /* IP version, traffic class & flow label. = */ uint16_t payload_len; /* IP packet length - includes sizeof(ip_he= ader). */ @@ -168,5 +168,5 @@ The following array of field definitions can be used: .. code-block:: c =20 - struct struct rte_acl_field_def ipv6_2tuple_defs[5] =3D { + struct rte_acl_field_def ipv6_2tuple_defs[5] =3D { { .type =3D RTE_ACL_FIELD_TYPE_BITMASK, diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte= _flow.rst index 9c6fc5e82..cbfeee870 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -1525,5 +1525,5 @@ The shared flag indicates whether the counter is uniq= ue to the flow rule the action is specified with, or whether it is a shared counter. =20 -For a count action with the shared flag set, then then a global device +For a count action with the shared flag set, then a global device namespace is assumed for the counter id, so that any matched flow rules us= ing a count action with the same counter id on the same port will contribute t= o diff --git a/doc/guides/prog_guide/rte_security.rst b/doc/guides/prog_guide= /rte_security.rst index 7d0734a37..f77fb89dc 100644 --- a/doc/guides/prog_guide/rte_security.rst +++ b/doc/guides/prog_guide/rte_security.rst @@ -52,5 +52,5 @@ packet. e.g. In case of IPsec, the IPsec tunnel headers (= if any), ESP/AH headers will remain in the packet but the received packet contains the decrypted data where the encrypted data was when the packet -arrived. The driver Rx path check the descriptors and and based on the +arrived. The driver Rx path check the descriptors and based on the crypto status sets additional flags in the rte_mbuf.ol_flags field. =20 @@ -66,5 +66,5 @@ relevant security protocol headers. Only the data will no= t be encrypted by the software. The driver will accordingly configure the tx descriptors. The hardware device will encrypt the data before sending t= he -the packet out. +packet out. =20 .. note:: diff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/= release_17_11.rst index 6448b6cb1..1f3b45ef6 100644 --- a/doc/guides/rel_notes/release_17_11.rst +++ b/doc/guides/rel_notes/release_17_11.rst @@ -476,5 +476,5 @@ API Changes =20 Two ``mbuf`` flags have been added to indicate that the VLAN - identifier has been saved in in the ``mbuf`` structure. For instance: + identifier has been saved in the ``mbuf`` structure. For instance: =20 - If VLAN is not stripped and TCI is saved: ``PKT_RX_VLAN`` diff --git a/doc/guides/rel_notes/release_18_02.rst b/doc/guides/rel_notes/= release_18_02.rst index 8e403118a..3523ea7fd 100644 --- a/doc/guides/rel_notes/release_18_02.rst +++ b/doc/guides/rel_notes/release_18_02.rst @@ -211,5 +211,5 @@ New Features operations by allowing applications to interact with device using opaque structures/buffers. Also, southbound APIs provide a means of integrating= devices - either as as part of a physical bus (PCI, FSLMC etc) or through ``vdev``= . + either as part of a physical bus (PCI, FSLMC etc) or through ``vdev``. =20 See the :doc:`../prog_guide/rawdev` programmer's guide for more details. diff --git a/doc/guides/sample_app_ug/ethtool.rst b/doc/guides/sample_app_u= g/ethtool.rst index 47e09f6ed..8f7fc6ca6 100644 --- a/doc/guides/sample_app_ug/ethtool.rst +++ b/doc/guides/sample_app_ug/ethtool.rst @@ -41,5 +41,5 @@ The application is console-driven using the cmdline DPDK = interface: =20 From this interface the available commands and descriptions of what -they do as as follows: +they do as follows: =20 * ``drvinfo``: Print driver info diff --git a/doc/guides/sample_app_ug/performance_thread.rst b/doc/guides/s= ample_app_ug/performance_thread.rst index 96f0fc6fd..a0ff18ffd 100644 --- a/doc/guides/sample_app_ug/performance_thread.rst +++ b/doc/guides/sample_app_ug/performance_thread.rst @@ -281,5 +281,5 @@ interconnected via software rings. =20 On initialization an L-thread scheduler is started on every EAL thread. On= all -but the master EAL thread only a a dummy L-thread is initially started. +but the master EAL thread only a dummy L-thread is initially started. The L-thread started on the master EAL thread then spawns other L-threads = on different L-thread schedulers according the command line parameters. diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testp= md_app_ug/testpmd_funcs.rst index 37d5d876b..c327d1f4d 100644 --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst @@ -34,5 +34,5 @@ If you type a partial command and hit ```` you get a= list of the available .. note:: =20 - Some examples in this document are too long to fit on one line are are = shown wrapped at `"\\"` for display purposes:: + Some examples in this document are too long to fit on one line are show= n wrapped at `"\\"` for display purposes:: =20 testpmd> set flow_ctrl rx (on|off) tx (on|off) (high_water) (low_wat= er) \ @@ -2575,5 +2575,5 @@ Traffic Management =20 The following section shows functions for configuring traffic management o= n -on the ethernet device through the use of generic TM API. +the ethernet device through the use of generic TM API. =20 show port traffic management capability --=20 2.21.0 --- Diff of the applied patch vs upstream commit (please double-check if non-= empty: --- --- -=092019-12-11 21:24:14.940436094 +0000 +++ 0028-doc-guides-clean-repeated-words.patch=092019-12-11 21:24:12.654651= 486 +0000 @@ -1 +1 @@ -From f43d3dbbd90c9e195d26d18ac7da9ca2854c3f1e Mon Sep 17 00:00:00 2001 +From 98e4dae7d0a00b2ccbc809983b3f0866f748044a Mon Sep 17 00:00:00 2001 @@ -6 +6 @@ -Shoot repeated words in all our guides. +[ upstream commit f43d3dbbd90c9e195d26d18ac7da9ca2854c3f1e ] @@ -8 +8 @@ -Cc: stable@dpdk.org +Shoot repeated words in all our guides. @@ -17,2 +16,0 @@ - doc/guides/prog_guide/bbdev.rst | 2 +- - doc/guides/prog_guide/cryptodev_lib.rst | 4 ++-- @@ -27,2 +24,0 @@ - doc/guides/rel_notes/release_19_02.rst | 4 ++-- - doc/guides/rel_notes/release_19_11.rst | 2 +- @@ -30,2 +25,0 @@ - doc/guides/sample_app_ug/ipsec_secgw.rst | 2 +- - doc/guides/sample_app_ug/ntb.rst | 2 +- @@ -34,2 +28 @@ - doc/guides/tools/proc_info.rst | 2 +- - 22 files changed, 30 insertions(+), 30 deletions(-) + 15 files changed, 21 insertions(+), 21 deletions(-) @@ -38 +31 @@ -index e95a1a2be..a6843de5a 100644 +index 656563dde..b848be5fb 100644 @@ -55 +48 @@ -index 69a5218b1..002e986da 100644 +index e38989968..dcd3ab0a5 100644 @@ -66 +59 @@ -index 0c25ec03d..c554c2159 100644 +index cf5c9e0db..4e9afbdbc 100644 @@ -69 +62 @@ -@@ -151,5 +151,5 @@ Configurations before running DPDK +@@ -153,5 +153,5 @@ Configurations before running DPDK @@ -87,29 +79,0 @@ -diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev= .rst -index d49184967..d39167af1 100644 ---- a/doc/guides/prog_guide/bbdev.rst -+++ b/doc/guides/prog_guide/bbdev.rst -@@ -1070,5 +1070,5 @@ the code block size ``K``. -=20 - The first CB Virtual Circular Buffer (VCB) index is given by ``r`` but th= e --the number of the remaining CB VCBs is calculated automatically by BBDEV -+number of the remaining CB VCBs is calculated automatically by BBDEV - and passed down to the driver. -=20 -diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_gui= de/cryptodev_lib.rst -index bf0ee79f8..ac1643774 100644 ---- a/doc/guides/prog_guide/cryptodev_lib.rst -+++ b/doc/guides/prog_guide/cryptodev_lib.rst -@@ -499,5 +499,5 @@ operations such as cipher encrypt and authentication g= enerate, the next pointer - allows transform to be chained together. Crypto devices which support cha= ining - must publish the chaining of symmetric Crypto operations feature flag. Al= location of the --xform structure is in the the application domain. To allow future API ext= ensions in a -+xform structure is in the application domain. To allow future API extensi= ons in a - backwardly compatible manner, e.g. addition of a new parameter, the appli= cation should - zero the full xform struct before populating it. -@@ -894,5 +894,5 @@ to specify the details of the asymmetric Crypto operat= ion. Next pointer within - xform allows transform to be chained together. Also it is important to no= te that - the order in which the transforms are passed indicates the order of the c= haining. Allocation --of the xform structure is in the the application domain. To allow future = API extensions in a -+of the xform structure is in the application domain. To allow future API = extensions in a - backwardly compatible manner, e.g. addition of a new parameter, the appli= cation should - zero the full xform struct before populating it. @@ -117 +81 @@ -index 6e59faeea..cd8e3003e 100644 +index 2bb77b019..a7536a80e 100644 @@ -120,2 +84,2 @@ -@@ -250,5 +250,5 @@ manual memory management. - + Using heap API's for externally allocated memory +@@ -221,5 +221,5 @@ matter of supplying the correct socket ID to DPDK allo= cator, either directly + structure-specific allocation API's such as ``rte_ring_create``). @@ -123,4 +87,4 @@ --Using using a set of malloc heap API's is the recommended way to use exte= rnally -+Using a set of malloc heap API's is the recommended way to use externally - allocated memory in DPDK. In this way, support for externally allocated m= emory - is implemented through overloading the socket ID - externally allocated h= eaps +-Since there is no way DPDK can verify whether memory are is available or = valid, ++Since there is no way DPDK can verify whether memory is available or vali= d, + this responsibility falls on the shoulders of the user. All multiprocess + synchronization is also user's responsibility, as well as ensuring that = all @@ -139 +103 @@ -index 2fd58e117..e12634ddc 100644 +index 9c1483adc..ccf03a41d 100644 @@ -142 +106 @@ -@@ -255,5 +255,5 @@ to create a separate thread or secondary process to pe= riodically call +@@ -244,5 +244,5 @@ to create a separate thread or secondary process to pe= riodically call @@ -150 +114 @@ -index c16b11af4..2945eacf5 100644 +index 395b3ec47..9e08a8e3f 100644 @@ -156,2 +120,2 @@ -- struct struct rte_ipv6_hdr { -+ struct rte_ipv6_hdr { +- struct struct ipv6_hdr { ++ struct ipv6_hdr { @@ -168 +132 @@ -index ac0020e44..a254c81ef 100644 +index 9c6fc5e82..cbfeee870 100644 @@ -171 +135 @@ -@@ -1651,5 +1651,5 @@ The shared flag indicates whether the counter is uni= que to the flow rule the +@@ -1525,5 +1525,5 @@ The shared flag indicates whether the counter is uni= que to the flow rule the @@ -218,27 +181,0 @@ -diff --git a/doc/guides/rel_notes/release_19_02.rst b/doc/guides/rel_notes= /release_19_02.rst -index b353620b7..ace1534ef 100644 ---- a/doc/guides/rel_notes/release_19_02.rst -+++ b/doc/guides/rel_notes/release_19_02.rst -@@ -266,9 +266,9 @@ ABI Changes - to include the following fields: ``queue ID``, ``traffic class``, ``col= or``. -=20 --* cryptodev: as shown in the the 18.11 deprecation notice, the structure -+* cryptodev: as shown in the 18.11 deprecation notice, the structure - ``rte_cryptodev_qp_conf`` has added two parameters for symmetric sessio= n - mempool and symmetric session private data mempool. -=20 --* cryptodev: as shown in the the 18.11 deprecation notice, the structure -+* cryptodev: as shown in the 18.11 deprecation notice, the structure - ``rte_cryptodev_sym_session`` has been updated to contain more informat= ion - to ensure safely accessing the session and session private data. -diff --git a/doc/guides/rel_notes/release_19_11.rst b/doc/guides/rel_notes= /release_19_11.rst -index 682c1bdf3..c0045a91f 100644 ---- a/doc/guides/rel_notes/release_19_11.rst -+++ b/doc/guides/rel_notes/release_19_11.rst -@@ -98,5 +98,5 @@ New Features -=20 - * Added new API ``rte_eth_dev_set_ptypes`` that allows an application t= o -- inform PMD about about reduced range of packet types to handle. -+ inform PMD about reduced range of packet types to handle. - * This scheme will allow PMDs to avoid lookup to internal ptype table o= n Rx - and thereby improve Rx performance if application wishes do so. @@ -256,22 +192,0 @@ -diff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_= app_ug/ipsec_secgw.rst -index ae8cce235..d6d8d4468 100644 ---- a/doc/guides/sample_app_ug/ipsec_secgw.rst -+++ b/doc/guides/sample_app_ug/ipsec_secgw.rst -@@ -159,5 +159,5 @@ Where: - will be discarded. Fragment lifetime should be decreased when - there is a high fragmented traffic loss in high bandwidth networks. -- Should be lower for for low number of reassembly buckets. -+ Should be lower for low number of reassembly buckets. - Valid values: from 1 ns to 10 s. Default value: 10000000 (10 s). -=20 -diff --git a/doc/guides/sample_app_ug/ntb.rst b/doc/guides/sample_app_ug/n= tb.rst -index df16af86c..93fb752f2 100644 ---- a/doc/guides/sample_app_ug/ntb.rst -+++ b/doc/guides/sample_app_ug/ntb.rst -@@ -83,5 +83,5 @@ The application is console-driven using the cmdline DPDK= interface: -=20 - From this interface the available commands and descriptions of what --they do as as follows: -+they do as follows: -=20 - * ``send [filepath]``: Send file to the peer host. Need to be in @@ -279 +194 @@ -index ac6ee8ac2..5fed46465 100644 +index 96f0fc6fd..a0ff18ffd 100644 @@ -290 +205 @@ -index 48473d8e2..6779822e1 100644 +index 37d5d876b..c327d1f4d 100644 @@ -300 +215 @@ -@@ -2761,5 +2761,5 @@ Traffic Management +@@ -2575,5 +2575,5 @@ Traffic Management @@ -307,11 +221,0 @@ -diff --git a/doc/guides/tools/proc_info.rst b/doc/guides/tools/proc_info.r= st -index 2ea1b59c2..0390b9c58 100644 ---- a/doc/guides/tools/proc_info.rst -+++ b/doc/guides/tools/proc_info.rst -@@ -64,5 +64,5 @@ ring. For invalid or no ring name, whole list is dump. - The show-mempool parameter display current allocation of all mempool - debug information. Specifying the name allows to display details for spec= ific --specific mempool. For invalid or no mempool name, whole list is dump. -+mempool. For invalid or no mempool name, whole list is dump. -=20 - **--iter-mempool=3Dname**