Docs: minor textual changes

Author: marnovandermaas

doc/auditing-firmware.md

@@ -101,7 +101,7 @@ In this fashion, you can define readable and maintainable policies, and easily a
 
 Rego is a policy language designed similarly to Datalog, which is a declarative logic inference programming language.
 As such, much of Rego's semantics will be familiar if you already know a logic programming language like Prolog, ASP or Datalog.
-Otherwise, it may be unfamiliar and unintuitive otherwise.
+Otherwise, it may be unfamiliar and unintuitive.
 If you have no such prior experience, it is highly recommended to read over the [Rego documentation][].
 
 [Rego documentation]: https://www.openpolicyagent.org/docs/latest/policy-language/

exercises/hardware_access_control/README.md

@@ -49,7 +49,7 @@ This compartment will arbitrate access to the LED outputs by making use of CHERI
 When a compartment seals a capability, it can no longer be dereferenced or modified until it is unsealed by a compartment with the capability to do so.
 The `gpio_access` compartment creates these sealing capabilities as LED *handles* that it can give to other compartments.
 These other compartments can't use the handles directly, but can only pass them to `gpio_access` which can unseal them and use them.
-In this case, they only point to a `LedHandle` structure that only holds the index of a LED.
+In this case, they only point to an `LedHandle` structure that holds the index of an LED.
 They are purely used as a proof of LED ownership.
 *For more information on sealing, see the [`cheriot-rtos/examples/05.sealing/`][].*