fix various typos found using Vale.spelling (and manual effort to rem…

…ove all the false positives) (#1561)

Signed-off-by: Kevin Broch <kbroch@rivosinc.com>

src/mm-formal.adoc

@@ -597,7 +597,7 @@ continue executing.
 Transitions specific to `sc` instructions:
 
 [disc]
-* <<early_sc_fail, Early sc fail>>: This causes the `sc` to fail, either a spontaneous fail or becauset is not paired with a program-order-previous `lr`.
+* <<early_sc_fail, Early sc fail>>: This causes the `sc` to fail, either a spontaneous fail or because it is not paired with a program-order-previous `lr`.
 
 * <<paired_sc, Paired sc>>: This transition indicates the `sc` is paired with an `lr` and might
 succeed.
@@ -1049,10 +1049,10 @@ load is acquire-RCsc.
 ===== Satisfy memory load operation from memory
 
 For an instruction instance latexmath:[$i$] of a non-AMO load
-instruction or an AMO instruction in the context of the <<do_amo, Saitsfy, commit and propagate operations of an AMO>> transition,
+instruction or an AMO instruction in the context of the <<do_amo, Satisfy, commit and propagate operations of an AMO>> transition,
 any memory load operation latexmath:[$mlo$] in
 latexmath:[$i.\textit{mem\_loads}$] that has unsatisfied slices, can be
-satisfied from memory if all the conditions of <sat_by_forwarding, Saitsfy memory load operation by forwarding from unpropagated stores>> are satisfied. Action:
+satisfied from memory if all the conditions of <sat_by_forwarding, Satisfy memory load operation by forwarding from unpropagated stores>> are satisfied. Action:
 let latexmath:[$msoss$] be the memory store operation slices from memory
 covering the unsatisfied slices of latexmath:[$mlo$], and apply the
 action of <<do_amo, Satisfy memory operation by forwarding from unpropagates stores>>.
@@ -1259,7 +1259,7 @@ Plain(_store_continuation(false)_).
 For efficiency, the `rmem` tool allows this transition only when it is
 not possible to take the <<commit_sc, Commit and propagate store operation of an sc>> transition. This does not affect the set of
 allowed final states, but when explored interactively, if the `sc`
-should fail one should use the <<early_sc_fail, Eaarly sc fail>> transition instead of waiting for this transition.
+should fail one should use the <<early_sc_fail, Early sc fail>> transition instead of waiting for this transition.
 ====
 [[complete_stores]]
 ===== Complete store operations

src/priv-preface.adoc

@@ -95,10 +95,10 @@ implemented.
 * Defined hardware error and software check exception codes.
 * Specified synchronization requirements when changing the PBMTE fields
 in `menvcfg` and `henvcfg`.
-* Exposed count-overflow interrups to VS-mode via the Shlcofideleg extension.
+* Exposed count-overflow interrupts to VS-mode via the Shlcofideleg extension.
 * Relaxed behavior of some HINTs when MXLEN > XLEN.
 
-Finally, the following clarifications and document improvments have been made
+Finally, the following clarifications and document improvements have been made
 since the last document release:
 
 * Transliterated the document from LaTeX into AsciiDoc.

src/scalar-crypto.adoc

@@ -4763,7 +4763,7 @@ information flow even if not explicitly forbidden in the specification.
 
 For security, virtualization requires both conditioning and DRBG processing
 of physical entropy output. It is recommended if a single physical entropy
-source is shared between multiple different virtual machnies or if the 
+source is shared between multiple different virtual machines or if the 
 guest OS is untrusted. A virtual entropy source is significantly more
 resistant to depletion attacks and also lessens the risk from covert channels.
 
@@ -4939,7 +4939,7 @@ operational at the same time.
 The noise source state shall be protected from adversarial
 knowledge or influence to the greatest extent possible. The methods
 used for this shall be documented, including a description of the
-(conceptual) security boundarys role in protecting the noise source
+(conceptual) security boundary's role in protecting the noise source
 from adversarial observation or influence.
 
 An entropy source is a singular resource, subject to depletion

src/smepmp.adoc

@@ -118,7 +118,7 @@ Also when ``mseccfg.MML`` is set, according to 4b it’s not possible to add a _
 +
 [NOTE]
 ====
-If ``mseccfg.RLB`` is not used and left unset, it wil be locked as soon as a PMP rule/entry with the ``pmpcfg.L`` bit set is configured.
+If ``mseccfg.RLB`` is not used and left unset, it will be locked as soon as a PMP rule/entry with the ``pmpcfg.L`` bit set is configured.
 ====
 +
 [IMPORTANT]
@@ -151,7 +151,7 @@ To make sure that shared data regions can’t be executed and shared code region
 +
 [NOTE]
 ====
-For adding _Shared-region_ rules with executable privileges to share code segments between M-mode and S/U-mode, ``mseccfg.RLB`` needs to be implemented, or else such rules can only be added together with ``mseccfg.MML`` being set on *PMP Reset*. That's because the reserved encoding ``pmpcfg.RW=01`` being used for _Shared-region_ rules is only defined when ``mseccfg.MML`` is set, and 4b prevents the adition of rules with executable privileges on M-mode after ``mseccfg.MML`` is set unless ``mseccfg.RLB`` is also set.
+For adding _Shared-region_ rules with executable privileges to share code segments between M-mode and S/U-mode, ``mseccfg.RLB`` needs to be implemented, or else such rules can only be added together with ``mseccfg.MML`` being set on *PMP Reset*. That's because the reserved encoding ``pmpcfg.RW=01`` being used for _Shared-region_ rules is only defined when ``mseccfg.MML`` is set, and 4b prevents the addition of rules with executable privileges on M-mode after ``mseccfg.MML`` is set unless ``mseccfg.RLB`` is also set.
 ====
 +
 [NOTE]

src/v-st-ext.adoc

@@ -5245,7 +5245,7 @@ this constraint is backwards-compatible.
 
 NOTE: This constraint prevents element groups being broken across
 stripmining iterations in vector-length-agnostic code when a
-VLMAX-size vector would otherwise be able to accomodate a whole number
+VLMAX-size vector would otherwise be able to accommodate a whole number
 of element groups.
 
 NOTE: If EEW is encoded statically in the instruction, or if an

src/vector-crypto.adoc

@@ -559,7 +559,7 @@ efficiently.
 [NOTE]
 ====
 This Zvkb extension is a proper subset of the Zvbb extension.
-Zvkb allows for vector crypto implementations without incuring
+Zvkb allows for vector crypto implementations without incurring
 the the cost of implementing the additional bitmanip instructions
 in the Zvbb extension: vbrev.v, vclz.v, vctz.v, vcpop.v, and vwsll.[vv,vx,vi].
 ====