Make uses of 'pseudo' consistent (#1469)

1 files changed, 3 insertions, 3 deletions

diff --git a/src/vector-crypto.adoc b/src/vector-crypto.adoc
index a87a589..695a46a 100644
--- a/src/vector-crypto.adoc
+++ b/src/vector-crypto.adoc
@@ -83,7 +83,7 @@ However, the Vector Crypto Sail model needs the Vector Sail model as a
 basis on which to build. This Vector Cryptography extensions specification
 was completed before there was an approved RISC-V Vector Sail Model.
 Therefore, we don't have any Sail code to include in the instruction
-descriptions. Instead we have included Sail-like pseudo code. While we have
+descriptions. Instead we have included Sail-like pseudocode. While we have
 endeavored to adhere to Sail syntax, we have taken some liberties for the
 sake of simplicity where we believe that that our intent is clear to the
 reader.
@@ -97,13 +97,13 @@ register with `a` having the highest element index of the group and `f` having t
 lowest index of the group.
 ====
 
-For the sake of brevity, our pseudo code does not include the handling of
+For the sake of brevity, our pseudocode does not include the handling of
 masks or tail elements. We follow the _undisturbed_ and _agnostic_ policies
 for masks and tails  as described in the *RISC-V "V" Vector Extension*
 specification. Furthermore, the code does not explicitly handle overlap and SEW
 constraints; these are, however, explicitly stated in the text.
 
-In many cases the pseudo code includes
+In many cases the pseudocode includes
 calls to supporting functions which are too verbose to include directly
 in the specification.
 This supporting code is listed in