Documentation: Fix a few typos in the ProcFS Indexing document

1 files changed, 4 insertions, 4 deletions

diff --git a/Documentation/Kernel/ProcFSIndexing.md b/Documentation/Kernel/ProcFSIndexing.md
index 0855731909..8a2cf73a09 100644
--- a/Documentation/Kernel/ProcFSIndexing.md
+++ b/Documentation/Kernel/ProcFSIndexing.md
@@ -19,7 +19,7 @@ The current ProcFS design doesn't follow that principle, but is easier to edit a
 A compromise is needed to ensure we get the advantages from both designs while minimizing the
 effects of the disadvantages of each design.
 
-## The segmeneted index
+## The segmented index
 
 ### The layout of the segmented index
 
@@ -31,10 +31,10 @@ to 3 Segments:
 All values from 1 to 0xFFFFFFF are valid PID indices, which represents all PIDs from 0 to 0xFFFFFFE
 
 - The Sub-directory segment: value 0 is reserved for parent PID directory. All other values are
-available for usage of subdirectories in the PID directory.
+available for usage of sub-directories in the PID directory.
 
 - The property segment: value 0 is reserved for parent PID directory. All other values are
-available for usage of components in the PID directory or in subdirectories of the PID directory.
+available for usage of components in the PID directory or in sub-directories of the PID directory.
 
 So, the final layout of the 64 bit index is:
 
@@ -62,7 +62,7 @@ Otherwise, for every primary segment value > 0, then the sub-directory and prope
 is applied. This means that there might be up to 65534 sub-directories in a PID directory, and
 up to 1048575 (1048574 for PID directory) properties (objects) in each sub-directory.
 
-2. If the primary segment value equals to 0, then value 0 in both aritificial sub-directory 
+2. If the primary segment value equals to 0, then value 0 in both artificial sub-directory 
 and property segments represents the root ProcFS folder.
 Otherwise, for every primary segment value > 0, value 0 in both sub-directory and
 property segments are reserved to represent the root PID directory.