summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorIan Gudger <igudger@google.com>2019-04-02 10:58:44 -0700
committerAdin Scannell <adin@scannell.ca>2019-04-02 11:36:47 -0700
commit2fce66039ed85c4e90fecd9dbed356b81f1d7da0 (patch)
tree4724fcf066e1ce2ff3e58119920bf03583d06778
parentdacb87a938986fa937c682062fa035f36566dea8 (diff)
Tweaks to VM comparison section
* Added a comma to improve readability and flow. * Fixed a typo.
-rw-r--r--content/docs/architecture_guide/security.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/docs/architecture_guide/security.md b/content/docs/architecture_guide/security.md
index 79da7c56e..ecc853d2f 100644
--- a/content/docs/architecture_guide/security.md
+++ b/content/docs/architecture_guide/security.md
@@ -185,7 +185,7 @@ The security of a VM depends to a large extent on what is exposed from the host
kernel and user space support code. For example, device emulation code in the
host kernel (e.g. APIC) or optimizations (e.g. vhost) can be more complex than a
simple system call, and exploits carry the same risks. Similarly, the user space
-support code is frequently unsandboxed and exploits, while rare, may allowed
+support code is frequently unsandboxed, and exploits, while rare, may allow
unfettered access to the system.
Some platforms leverage the same virtualization hardware as VMs in order to