Correct several documentation issues:
- Change "It consist of calls" to "It consists of calls"
- Add missing comma after "EAL" for proper sentence structure

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

diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst 
b/doc/guides/prog_guide/env_abstraction_layer.rst
index d716895c1d..170c34576d 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -50,7 +50,7 @@ Initialization and Core Launching
 Part of the initialization is done by the start function of glibc.
 A check is also performed at initialization time to ensure that the micro 
architecture type chosen in the config file is supported by the CPU.
 Then, the main() function is called. The core initialization and launch is 
done in rte_eal_init() (see the API documentation).
-It consist of calls to the pthread library (more specifically, pthread_self(), 
pthread_create(), and pthread_setaffinity_np()).
+It consists of calls to the pthread library (more specifically, 
pthread_self(), pthread_create(), and pthread_setaffinity_np()).
 
 .. _figure_linux_launch:
 
@@ -69,7 +69,7 @@ It consist of calls to the pthread library (more 
specifically, pthread_self(), p
 Shutdown and Cleanup
 ~~~~~~~~~~~~~~~~~~~~
 
-During the initialization of EAL resources such as hugepage backed memory can 
be
+During the initialization of EAL, resources such as hugepage backed memory can 
be
 allocated by core components.  The memory allocated during ``rte_eal_init()``
 can be released by calling the ``rte_eal_cleanup()`` function. Refer to the
 API documentation for details.
-- 
2.51.0

Reply via email to