summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKian-Meng, Ang <kianmeng@cpan.org>2021-12-30 20:31:41 +0800
committerKian-Meng, Ang <kianmeng@cpan.org>2021-12-30 20:31:41 +0800
commitb812f158cb2012cf1ea3bc2147c7bc82dabdada9 (patch)
treecaaacc1eeef33c21ee737754d3f12555c87b734b /docs
parent45c042ee849710fb45df6c3a9f980cdc0d7524f4 (diff)
downloadnatsort-b812f158cb2012cf1ea3bc2147c7bc82dabdada9.tar.gz
Fix typos
Diffstat (limited to 'docs')
-rw-r--r--docs/api.rst2
-rw-r--r--docs/examples.rst2
-rw-r--r--docs/locale_issues.rst2
3 files changed, 3 insertions, 3 deletions
diff --git a/docs/api.rst b/docs/api.rst
index 39d7cec..242b22d 100644
--- a/docs/api.rst
+++ b/docs/api.rst
@@ -121,7 +121,7 @@ the corresponding regular expression to locate numbers will be returned.
Help With Type Hinting
++++++++++++++++++++++
-If you need to explictly specify the types that natsort accepts or returns
+If you need to explicitly specify the types that natsort accepts or returns
in your code, the following types have been exposed for your convenience.
+--------------------------------+----------------------------------------------------------------------------------------+
diff --git a/docs/examples.rst b/docs/examples.rst
index a0e3a01..8bc05c0 100644
--- a/docs/examples.rst
+++ b/docs/examples.rst
@@ -158,7 +158,7 @@ you can easily do this with the ``ns.IGNORECASE`` option:
>>> natsorted(a, alg=ns.IGNORECASE)
['Apple', 'apple', 'Banana', 'banana', 'corn', 'Corn']
-Note thats since Python's sorting is stable, the order of equivalent
+Note that's since Python's sorting is stable, the order of equivalent
elements after lowering the case is the same order they appear in the
original list.
diff --git a/docs/locale_issues.rst b/docs/locale_issues.rst
index f51ab27..56cd5a9 100644
--- a/docs/locale_issues.rst
+++ b/docs/locale_issues.rst
@@ -23,7 +23,7 @@ Regenerate Key With :func:`~natsort.natsort_keygen` After Changing Locale
When :func:`~natsort.natsort_keygen` is called it returns a key function that
hard-codes the provided settings. This means that the key returned when
-``ns.LOCALE`` is used contains the settings specifed by the locale
+``ns.LOCALE`` is used contains the settings specified by the locale
*loaded at the time the key is generated*. If you change the locale,
you should regenerate the key to account for the new locale.