summaryrefslogtreecommitdiff
path: root/docs/why.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/why.rst')
-rw-r--r--docs/why.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/why.rst b/docs/why.rst
index dc06ca9..10aeff8 100644
--- a/docs/why.rst
+++ b/docs/why.rst
@@ -101,7 +101,7 @@ following:
- Click has a strong understanding of what types are and can give the user
consistent error messages if something goes wrong. A subcommand
written by a different developer will not suddenly die with a
- different error messsage because it's manually handled.
+ different error message because it's manually handled.
- Click has enough meta information available for its whole program
that it can evolve over time to improve the user experience without
forcing developers to adjust their programs. For instance, if Click
@@ -125,7 +125,7 @@ reasons for this. The biggest one is that too much configurability makes
it hard to achieve a consistent command line experience.
The best example for this is optparse's ``callback`` functionality for
-accepting arbitrary number of arguments. Due to syntactical ambiguities
+accepting an arbitrary number of arguments. Due to syntactical ambiguities
on the command line, there is no way to implement fully variadic arguments.
There are always tradeoffs that need to be made and in case of
``argparse`` these tradeoffs have been critical enough, that a system like