diff options
| author | Ian Gudger <igudger@google.com> | 2019-04-02 10:25:41 -0700 |
|---|---|---|
| committer | Adin Scannell <adin@scannell.ca> | 2019-04-02 11:36:47 -0700 |
| commit | 6929bdac333a64d342b352bf2fdba1435624a4a2 (patch) | |
| tree | 4bd4c79b76a4520e8a53ceecdc29c7f01eb94219 /content/docs/architecture_guide | |
| parent | 882a3a914ea8fb48f15e29f24fc0ed6a56fa84f6 (diff) | |
Fix typo in security doc
with -> will
Diffstat (limited to 'content/docs/architecture_guide')
| -rw-r--r-- | content/docs/architecture_guide/security.md | 2 |
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 |