[4/5] doc/guides: fix grammar
Checks
Commit Message
A copy'n'paste typo was present in three guides.
Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
---
doc/guides/prog_guide/bbdev.rst | 2 +-
doc/guides/prog_guide/compressdev.rst | 2 +-
doc/guides/prog_guide/cryptodev_lib.rst | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
Comments
Acked-by: Rami Rosen <ramirose@gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thierry Herbelot
> Sent: Wednesday, May 22, 2019 10:45 AM
> To: dev@dpdk.org
> Cc: Thomas Monjalon <thomas@monjalon.net>
> Subject: [dpdk-dev] [PATCH 4/5] doc/guides: fix grammar
>
> A copy'n'paste typo was present in three guides.
>
> Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
@@ -284,7 +284,7 @@ baseband operations is usually completed during the enqueue call to the bbdev
device. The dequeue burst API will retrieve any processed operations available
from the queue on the bbdev device, from physical devices this is usually
directly from the device's processed queue, and for virtual device's from a
-``rte_ring`` where processed operations are place after being processed on the
+``rte_ring`` where processed operations are placed after being processed on the
enqueue call.
@@ -568,7 +568,7 @@ operations is usually completed during the enqueue call to the compression
device. The dequeue burst API will retrieve any processed operations available
from the queue pair on the compression device, from physical devices this is usually
directly from the devices processed queue, and for virtual device's from a
-``rte_ring`` where processed operations are place after being processed on the
+``rte_ring`` where processed operations are placed after being processed on the
enqueue call.
A burst in DPDK compression can be a combination of stateless and stateful operations with a condition
@@ -304,7 +304,7 @@ Crypto operations is usually completed during the enqueue call to the Crypto
device. The dequeue burst API will retrieve any processed operations available
from the queue pair on the Crypto device, from physical devices this is usually
directly from the devices processed queue, and for virtual device's from a
-``rte_ring`` where processed operations are place after being processed on the
+``rte_ring`` where processed operations are placed after being processed on the
enqueue call.