diff options
| author | Kyle Fazzari <kyle@canonical.com> | 2016-09-15 07:03:32 -0700 |
|---|---|---|
| committer | Kyle Fazzari <kyle@canonical.com> | 2016-09-15 07:03:32 -0700 |
| commit | bb62bc6df92eb29a640e5a84b1d243389254e052 (patch) | |
| tree | a6e9e2e5653f6d2a9c6d68f2989602e67b17e561 /docs | |
| parent | 2f86a9a40f6659972d02c0ad8ff2ddc9ade12893 (diff) | |
don't use the word "capability."
Signed-off-by: Kyle Fazzari <kyle@canonical.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/hooks.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/hooks.md b/docs/hooks.md index 0dae15166e..b4e879f1ac 100644 --- a/docs/hooks.md +++ b/docs/hooks.md @@ -14,8 +14,8 @@ the upgrade hook executable would be `meta/hooks/upgrade`). As long as the file name of the executable corresponds to a supported hook name, that's all one needs to do in order to utilize a hook within their snap. Note that hooks, like apps, are executed within a confined environment. By default -hooks will run with no plugs; if a hook needs more capabilities one can use the -top-level attribute `hooks` in `snap.yaml`, like so: +hooks will run with no plugs; if a hook needs more privileges one can use the +top-level attribute `hooks` in `snap.yaml` to request plugs, like so: hooks: # Top-level YAML attribute, parallel to `apps` upgrade: # Hook name, corresponds to executable name |