summaryrefslogtreecommitdiffhomepage
path: root/g3doc
diff options
context:
space:
mode:
authorgVisor bot <gvisor-bot@google.com>2021-10-12 18:30:16 -0700
committergVisor bot <gvisor-bot@google.com>2021-10-12 18:30:16 -0700
commit049fa8ea9999799cc304fe811ca8028a195be493 (patch)
tree6edd50a60a66ff6b3f6b7eaaf72ffa9633b4ba28 /g3doc
parente54ee7a990753ba0616b9dc6010323f5a411cb5f (diff)
parentb5ae22f201854698acfb64266bba662de5c5b12b (diff)
Merge pull request #6654 from nickkelley42:documentation-nits
PiperOrigin-RevId: 402705397
Diffstat (limited to 'g3doc')
-rw-r--r--g3doc/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/g3doc/README.md b/g3doc/README.md
index 22bfb15f7..dc4179037 100644
--- a/g3doc/README.md
+++ b/g3doc/README.md
@@ -139,8 +139,8 @@ pipes, etc) are sent to the Gofer, described below.
The Gofer is a standard host process which is started with each container and
communicates with the Sentry via the [9P protocol][9p] over a socket or shared
memory channel. The Sentry process is started in a restricted seccomp container
-without access to file system resources. The Gofer mediates all access to the
-these resources, providing an additional level of isolation.
+without access to file system resources. The Gofer mediates all access to these
+resources, providing an additional level of isolation.
### Application {#application}