summaryrefslogtreecommitdiffhomepage
path: root/content/docs/architecture_guide/security.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/docs/architecture_guide/security.md')
-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 2dec0765c..9cc146521 100644
--- a/content/docs/architecture_guide/security.md
+++ b/content/docs/architecture_guide/security.md
@@ -99,7 +99,7 @@ interactions with a guest operating system and a set of virtualized hardware
devices. These hardware devices are then implemented via the host System API by
a Virtual Machine Monitor (VMM). For both the Sentry and a VMM, it’s worth
noting that while direct interactions are minimized, indirect interactions are
-still possible. For example, a read on a host-backed file in the Sentry with
+still possible. For example, a read on a host-backed file in the Sentry will
ultimately result in a host read system call (made by the Sentry, not by passing
through arguments from the application), similarly to how a read on a block
device in a VMM will often result in a host read system call from the backing