diff options
| author | Didier Durand <durand.didier@gmail.com> | 2020-09-20 10:41:08 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-09-20 10:41:08 +0200 |
| commit | b8793582d61dc4096f452ab7d3f70dc2963b3c3d (patch) | |
| tree | 9d842a77b5841873e461599a53e52d29cfc12e30 | |
| parent | 916751039cca927a0e64b4e6f776d2d4732cf8d8 (diff) | |
Fix 2 typos in resources.md
2 typos spotted and fixed
Best
Didier
| -rw-r--r-- | g3doc/architecture_guide/resources.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/g3doc/architecture_guide/resources.md b/g3doc/architecture_guide/resources.md index 1dec37bd1..fc997d40c 100644 --- a/g3doc/architecture_guide/resources.md +++ b/g3doc/architecture_guide/resources.md @@ -19,12 +19,12 @@ sandboxed process: Much like a Virtual Machine (VM), a gVisor sandbox appears as an opaque process on the system. Processes within the sandbox do not manifest as processes on the -host system, and process-level interactions within the sandbox requires entering +host system, and process-level interactions within the sandbox require entering the sandbox (e.g. via a [Docker exec][exec]). ## Networking -The sandbox attaches a network endpoint to the system, but runs it's own network +The sandbox attaches a network endpoint to the system, but runs its own network stack. All network resources, other than packets in flight on the host, exist only inside the sandbox, bound by relevant resource limits. |