summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorRadovan Bast <bast@users.noreply.github.com>2017-01-29 20:50:35 +0100
committerAdrian <adrian@planetcoding.net>2017-01-29 20:50:35 +0100
commitb5239afafe6e36f53defabb392ac5264e0f5eb6b (patch)
tree50e35be67fde58639e9c9b79d4384753592a41d3 /docs
parenta50befdc3ac475826af75e48fd48b21530851176 (diff)
downloadclick-b5239afafe6e36f53defabb392ac5264e0f5eb6b.tar.gz
Fix typos in docs (#623)
Diffstat (limited to 'docs')
-rw-r--r--docs/advanced.rst2
-rw-r--r--docs/bashcomplete.rst2
-rw-r--r--docs/commands.rst2
-rw-r--r--docs/upgrading.rst2
-rw-r--r--docs/utils.rst2
5 files changed, 5 insertions, 5 deletions
diff --git a/docs/advanced.rst b/docs/advanced.rst
index a0165f0..17f86da 100644
--- a/docs/advanced.rst
+++ b/docs/advanced.rst
@@ -277,7 +277,7 @@ options:
If you go with this solution, the extra arguments will be collected in
:attr:`Context.args`.
2. You can attach a :func:`argument` with ``nargs`` set to `-1` which
- will eat up all leftover arguments. In this case it's recommeded to
+ will eat up all leftover arguments. In this case it's recommended to
set the `type` to :data:`UNPROCESSED` to avoid any string processing
on those arguments as otherwise they are forced into unicode strings
automatically which is often not what you want.
diff --git a/docs/bashcomplete.rst b/docs/bashcomplete.rst
index 9154dfb..257bcff 100644
--- a/docs/bashcomplete.rst
+++ b/docs/bashcomplete.rst
@@ -42,7 +42,7 @@ with dashes replaced by underscores.
If your tool is called ``foo-bar``, then the magic variable is called
``_FOO_BAR_COMPLETE``. By exporting it with the ``source`` value it will
-spit out the activation script which can be trivally activated.
+spit out the activation script which can be trivially activated.
For instance, to enable Bash completion for your ``foo-bar`` script, this
is what you would need to put into your ``.bashrc``::
diff --git a/docs/commands.rst b/docs/commands.rst
index 29c71e4..5a7ef79 100644
--- a/docs/commands.rst
+++ b/docs/commands.rst
@@ -437,7 +437,7 @@ you're not satisfied with the defaults.
The default map can be nested arbitrarily for each subcommand and
provided when the script is invoked. Alternatively, it can also be
-overriden at any point by commands. For instance, a top-level command could
+overridden at any point by commands. For instance, a top-level command could
load the defaults from a configuration file.
Example usage:
diff --git a/docs/upgrading.rst b/docs/upgrading.rst
index b682d21..7c4cccd 100644
--- a/docs/upgrading.rst
+++ b/docs/upgrading.rst
@@ -44,7 +44,7 @@ properly by this function.
Multicommand Chaining API
`````````````````````````
-Click 3 introduced multicommand chaning. This required a change in how
+Click 3 introduced multicommand chaining. This required a change in how
Click internally dispatches. Unfortunately this change was not correctly
implemented and it appeared that it was possible to provide an API that
can inform the super command about all the subcommands that will be
diff --git a/docs/utils.rst b/docs/utils.rst
index 2ecbe88..9bd98b0 100644
--- a/docs/utils.rst
+++ b/docs/utils.rst
@@ -226,7 +226,7 @@ Launching Applications
.. versionadded:: 2.0
Click supports launching applications through :func:`launch`. This can be
-used to open the default application assocated with a URL or filetype.
+used to open the default application associated with a URL or filetype.
This can be used to launch web browsers or picture viewers, for instance.
In addition to this, it can also launch the file manager and automatically
select the provided file.