diff options
| author | Carlton Gibson <carlton.gibson@noumenal.es> | 2024-07-03 18:54:21 +0200 |
|---|---|---|
| committer | Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> | 2024-07-04 08:32:34 +0200 |
| commit | 3b5d04f879f6d3d8ff7f5d82b4a7c801b71b2fd0 (patch) | |
| tree | 25157010f540a6a61b89b35e89d05ef89ad03497 /docs | |
| parent | 9f4725fa8f8fbf6d94f5c93022fc36d4246fbd11 (diff) | |
[5.1.x] Removed unneeded hyphens in "counterintuitive".
Follow-up to 65ad4ade74dc9208b9d686a451cd6045df0c9c3a which added
counterintuitive to the wordlist. Removes unneeded (antiquated)
hyphenated usages.
See e.g. https://www.merriam-webster.com/dictionary/counterintuitive
Backport of 704192e478885762411252979021771ba23b8adb from main.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/intro/tutorial05.txt | 2 | ||||
| -rw-r--r-- | docs/ref/databases.txt | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/intro/tutorial05.txt b/docs/intro/tutorial05.txt index 2e218bd331..5f501ce92f 100644 --- a/docs/intro/tutorial05.txt +++ b/docs/intro/tutorial05.txt @@ -111,7 +111,7 @@ There are many ways to approach writing tests. Some programmers follow a discipline called "`test-driven development`_"; they actually write their tests before they write their code. This might seem -counter-intuitive, but in fact it's similar to what most people will often do +counterintuitive, but in fact it's similar to what most people will often do anyway: they describe a problem, then create some code to solve it. Test-driven development formalizes the problem in a Python test case. diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index c8e9f2ebff..437feeaccb 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -826,7 +826,7 @@ specific to SQLite that you should be aware of. Substring matching and case sensitivity --------------------------------------- -For all SQLite versions, there is some slightly counter-intuitive behavior when +For all SQLite versions, there is some slightly counterintuitive behavior when attempting to match some types of strings. These are triggered when using the :lookup:`iexact` or :lookup:`contains` filters in Querysets. The behavior splits into two cases: |