On 15/01/2025 1:44 pm, Bernhard Kaindl wrote: > diff --git a/docs/designs/argo.pandoc b/docs/designs/argo.pandoc > index e18aacea7c..cd854d2a7a 100644 > --- a/docs/designs/argo.pandoc > +++ b/docs/designs/argo.pandoc > @@ -127,7 +127,7 @@ by the domain. > > ## Hierarchical Locking Model and Protocol > > -The locking discipline within the Argo code is heirarchical and utilizes > +The locking discipline within the Argo code is hierarchical and utilizes > reader/writer locks to enable increased concurrency when operations do not > conflict. None of the Argo locks are reentrant. >
In addition, focusses -> focuses needed in another hunk here. > diff --git a/docs/designs/nested-svm-cpu-features.md > b/docs/designs/nested-svm-cpu-features.md > index 837a96df05..c855748141 100644 > --- a/docs/designs/nested-svm-cpu-features.md > +++ b/docs/designs/nested-svm-cpu-features.md > @@ -89,7 +89,7 @@ leaf 8000000A:edx > - 5 `VmcbClean`: VMCB Clean Bits: Not required by L0, provide to L1 > > This is a pure optimization, both on the side of the L0 and L1. The > - implementaiton for L1 is entirely Xen-side, so can be provided even > + implementation for L1 is entirely Xen-side, so can be provided even > on hardware that doesn't provide it. And it's purely an > optimization, so could be "implemented" by ignoring the bits > entirely. Also reson -> reason in another hunk here. > diff --git a/docs/designs/qemu-deprivilege.md > b/docs/designs/qemu-deprivilege.md > index f12b1a3ae3..603491f24d 100644 > --- a/docs/designs/qemu-deprivilege.md > +++ b/docs/designs/qemu-deprivilege.md > @@ -251,7 +251,7 @@ executing QEMU. (But this would then require other > changes to create > the QMP socket, VNC socket, and so on). > > It should be noted that `-sandbox` is implemented as a blacklist, not > -a whitelist; that is, it disables known-unsed functionality which may > +a whitelist; that is, it disables known-unused functionality which may > be harmful, rather than disabling all functionality except that known > to be safe and needed. This is unfortunately necessary since qemu > doesn't know what system calls libraries might end up making. (See Also assymetry -> asymmetry and constrants -> constraints. I've folded these in. Acked-by: Andrew Cooper <andrew.coop...@citrix.com>
