From ab28cd9a2c8c7c3b46a2499c67be5157c9483e40 Mon Sep 17 00:00:00 2001 From: Dan Gohman Date: Thu, 28 Mar 2019 10:51:07 -0700 Subject: [PATCH] Tidy up wording in the explanation of capabilities, and link to the tutorial. --- docs/WASI-capabilities.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/WASI-capabilities.md b/docs/WASI-capabilities.md index ea8aded425..a44a7a6580 100644 --- a/docs/WASI-capabilities.md +++ b/docs/WASI-capabilities.md @@ -47,9 +47,12 @@ advantage of the hierarchical nature of the filesystem and require untrusted code to have a capability for a directory in order to access things inside that directory. -So you can launch untrusted code, and at runtime give it access to specific -directories, without having to set permissions in the filesystem or in -per-application or per-user configuration settings. +This way, you can launch untrusted code, and at runtime give it access to +specific directories, without having to set permissions in the filesystem or +in per-application or per-user configuration settings. + +See [this tutorial](WASI-tutorial.md) for an example of how this can look +in practice. ## Berkeley socket rules