diff options
| author | Armin Ronacher <armin.ronacher@active-4.com> | 2014-04-26 13:01:21 +0200 |
|---|---|---|
| committer | Armin Ronacher <armin.ronacher@active-4.com> | 2014-04-26 13:01:21 +0200 |
| commit | b2475cd28ec6d5849e663e913d08059dabb2cb0f (patch) | |
| tree | 6ac4e01bf05b70ac231878f96a3677540860b80f /docs/commands.rst | |
| parent | e2d388e05db0059b1ba209153e96ec7b70ff8560 (diff) | |
| parent | ba82cf39c901c1cac2339871d8c44f94bc449c7e (diff) | |
| download | click-b2475cd28ec6d5849e663e913d08059dabb2cb0f.tar.gz | |
Merge pull request #27 from epequeno/docs-edits
edits to arguments.rst and commands.rst
Diffstat (limited to 'docs/commands.rst')
| -rw-r--r-- | docs/commands.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/commands.rst b/docs/commands.rst index 7c8ba58..36aa5e9 100644 --- a/docs/commands.rst +++ b/docs/commands.rst @@ -58,10 +58,10 @@ debug argument which is passed to its callback, but not to the sync command itself. The sync command only accepts its own arguments. This allows tools to act completely independent of each other. But how -does on command talk to a nested on? The answer to this is the +does one command talk to a nested one? The answer to this is the :class:`Context`. -Each time a command invokes a new context is created and linked with the +Each time a command is invoked a new context is created and linked with the parent context. Normally you can't see these contexts, but they are there. Contexts are passed to parameter callbacks together with the value automatically. Commands can also ask for the context to be passed |