Type Rust and WebAssembly consistently.

Author: definitelynobody

docs/Installation/Wasm.md

@@ -2,19 +2,19 @@
 
 ## Build and run a WebAssembly module
 
-Install the Webassembly rust toolchain:
+Install the WebAssembly Rust toolchain:
 
     $ rustup target install wasm32-wasi
 
-Create a simple rust program:
+Create a simple Rust program:
 
     $ cargo init --bin hello-world
     $ cd hello-world
     $ echo 'fn main() { println!("Hello, Enarx!"); }' > src/main.rs
     $ cargo build --release --target=wasm32-wasi
 
 Assuming you did install the `enarx` binary and have it in your `$PATH`, you can
-now run the Webassembly program in an Enarx keep.
+now run the WebAssembly program in an Enarx keep.
 
     $ enarx run target/wasm32-wasi/release/hello-world.wasm
     […]

docs/Technical/Trust-Architecture.md

@@ -8,7 +8,7 @@ Enarx provides four layers in the run-time stack.  Working from the lowest up, t
 1. a VMM (Virtual Memory Manager)
 2. a microkernel (μkernel)
 3. a WASM runtime (WebAssembly)
-4. a WASI implementation (Web Assembly System Interface).
+4. a WASI implementation (WebAssembly System Interface).
 
 All of these are cryptographically measured and checked at runtime before each deployment.  They are not the only layers in the stack, however.  Others include the CPU (in which layer we also include CPU firmware), the host kernel and the application itself.  See below for a little more detail about the trust architecture.