Correct various issues in the packet distributor documentation:

- remove extra space after "each"
- fix typo "work" to "worker" in queue description
- fix "of less use that" to "of less use than"
- fix inconsistent capitalization "APIS" to "APIs"

Signed-off-by: Stephen Hemminger <[email protected]>
---
 doc/guides/prog_guide/packet_distrib_lib.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/guides/prog_guide/packet_distrib_lib.rst 
b/doc/guides/prog_guide/packet_distrib_lib.rst
index 3c3b746aca..10e187be04 100644
--- a/doc/guides/prog_guide/packet_distrib_lib.rst
+++ b/doc/guides/prog_guide/packet_distrib_lib.rst
@@ -33,11 +33,11 @@ The operation of the distributor is as follows:
 
 #.  As workers request packets, the distributor takes packets from the set of 
packets passed in and distributes them to the workers.
     As it does so, it examines the "tag" -- stored in the RSS hash field in 
the mbuf -- for each packet
-    and records what tags are being processed by each  worker.
+    and records what tags are being processed by each worker.
 
 #.  If the next packet in the input set has a tag which is already being 
processed by a worker,
     then that packet will be queued up for processing by that worker
-    and given to it in preference to other packets when that work next makes a 
request for work.
+    and given to it in preference to other packets when that worker next makes 
a request for work.
     This ensures that no two packets with the same tag are processed in 
parallel,
     and that all packets with the same tag are processed in input order.
 
@@ -78,7 +78,7 @@ while allowing packet order within a packet flow -- 
identified by a tag -- to be
 
 
 The flush and clear_returns API calls, mentioned previously,
-are likely of less use that the process and returned_pkts APIS, and are 
principally provided to aid in unit testing of the library.
+are likely of less use than the process and returned_pkts APIs, and are 
principally provided to aid in unit testing of the library.
 Descriptions of these functions and their use can be found in the DPDK API 
Reference document.
 
 Worker Operation
-- 
2.51.0

Reply via email to