(no commit message)

diff --git a/openpower/sv/rfc/ls001.mdwn b/openpower/sv/rfc/ls001.mdwn
index 25d4433a4b83667d215b0cff52360c152f1d7199..f1a06c5cb304d76a4da6ded73e1028a3b4b24841 100644 (file)
--- a/openpower/sv/rfc/ls001.mdwn
+++ b/openpower/sv/rfc/ls001.mdwn
@@ -329,7 +329,7 @@ the above scheme originated. Section 1.6.3 uses the term "defined word"
 to refer to pre-existing EXT000-EXT063 32-bit instructions so prefixed
 to create the new numbering EXT100-EXT163, respectively*)
 
-For Libre-SOC's needs, one of the `RESERVED` spaces *needs* to be allocated to new POs, the other does not:
+For the needs identified by Libre-SOC's team, one of the `RESERVED` spaces *needs* allocation to new POs, the other does not:
 
 |          | Scalar (bit7=0,8-31=0000) | Scalar (bit7=0,8-31=!zero)| Vector (bit7=1)  |
 |----------|---------------------------|---------------------------|------------------|
@@ -344,7 +344,7 @@ For Libre-SOC's needs, one of the `RESERVED` spaces *needs* to be allocated to n
   These opcodes do not *need* to be Simple-V-Augmented
   *but the option to do so exists* should an Implementor choose to do so.
   This is unlike `EXT300-363` which may **never** be Simple-V-Augmented
-  under any cirmstances.
+  under any circumstances.
 * **`SVP64-Single:{EXT200-263}`** - Major opcodes 200-263 with
   Single-Augmentation, providing a one-bit predicate mask, element-width
   overrides on source and destination, and the option to extend the Scalar