diff options
| author | Ian Gudger <igudger@google.com> | 2019-04-02 10:53:24 -0700 |
|---|---|---|
| committer | Adin Scannell <adin@scannell.ca> | 2019-04-02 11:36:47 -0700 |
| commit | dacb87a938986fa937c682062fa035f36566dea8 (patch) | |
| tree | ac3a516a799fa287c93e3130fd13ee89a2886146 /content/docs/architecture_guide | |
| parent | f419ffb46d34654e69e8dba3174bba3bc192f5c4 (diff) | |
Replace distinct with independent.
I think this is clearer.
Diffstat (limited to 'content/docs/architecture_guide')
| -rw-r--r-- | content/docs/architecture_guide/security.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/content/docs/architecture_guide/security.md b/content/docs/architecture_guide/security.md index 849c15744..79da7c56e 100644 --- a/content/docs/architecture_guide/security.md +++ b/content/docs/architecture_guide/security.md @@ -146,8 +146,8 @@ For gVisor development, there are several engineering principles that are employed in order to ensure that the system meets its design goals. 1. No system call is passed through directly to the host. Every supported call - has a distinct implementation in the Sentry, that is unlikely to suffer from - identical vulnerabilities that may appear in the host. This has the + has an independent implementation in the Sentry, that is unlikely to suffer + from identical vulnerabilities that may appear in the host. This has the consequence that all kernel features used by applications require an implementation within the Sentry. 1. Only common, universal functionality is implemented. Some filesystems, |