Fixed docs spelling errors accumulated over time.

The `docs` GitHub action does not install `aspell` so the seplling
checks are always passing in CI. After installing it, the following
errors are reported:

WARNING: internals/security.txt:50: : Spell check: runnable: Include a runnable proof of concept.
WARNING: ref/contrib/postgres/search.txt:292: : Spell check: lexeme: an untrusted source. The content of each lexeme is escaped so that any.
WARNING: ref/contrib/postgres/search.txt:295: : Spell check: lexemes: You can combine lexemes with other lexemes using the .
WARNING: ref/contrib/postgres/search.txt:295: : Spell check: lexemes: You can combine lexemes with other lexemes using the .
WARNING: ref/contrib/postgres/search.txt:314: : Spell check: Lexeme: Lexeme objects also support term weighting and prefixes:.
WARNING: ref/models/database-functions.txt:1897: : Spell check: ai: 23ai/26ai (23.9) or later..
WARNING: ref/models/database-functions.txt:1897: : Spell check: ai: 23ai/26ai (23.9) or later..
WARNING: ref/models/expressions.txt:439: : Spell check: positionally:  can be supplied positionally or only by keyword. For.
WARNING: ref/models/fields.txt:1339: : Spell check: ai: PostgreSQL < 18 only supports persisted columns. Oracle < 23ai/26ai (23.7).
WARNING: ref/models/fields.txt:1339: : Spell check: ai: PostgreSQL < 18 only supports persisted columns. Oracle < 23ai/26ai (23.7).
WARNING: ref/models/fields.txt:1344: : Spell check: ai: s was added on Oracle 23ai/26ai.
WARNING: ref/models/fields.txt:1344: : Spell check: ai: s was added on Oracle 23ai/26ai.
WARNING: releases/4.2.21.txt:24: : Spell check: unclosed: exception if it encounters an unusually large number of unclosed opening tags..
WARNING: releases/5.1.9.txt:24: : Spell check: unclosed: exception if it encounters an unusually large number of unclosed opening tags..
WARNING: releases/5.2.1.txt:24: : Spell check: unclosed: exception if it encounters an unusually large number of unclosed opening tags..
WARNING: releases/6.1.txt:244: : Spell check: mistyped: suggestions for mistyped subcommand names and argument choices..
WARNING: releases/6.1.txt:281: : Spell check: ai: Oracle 23ai/26ai (23.7+)..
WARNING: releases/6.1.txt:281: : Spell check: ai: Oracle 23ai/26ai (23.7+)..
WARNING: releases/6.1.txt:343: : Spell check: durations: durations expressed in weeks (.
WARNING: Found 19 misspelled words
build finished with problems, 20 warnings (with warnings treated as errors).

This branch adds some of the words to the allowlist, but for others I
chose to rephrase the text in a more approachable manner.

docs/internals/security.txt

@@ -46,8 +46,8 @@ the industry-standard 90 days. Confirmed vulnerabilities with a
 Reporting guidelines
 --------------------
 
-Include a runnable proof of concept
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Include a working proof of concept
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Please privately share a minimal Django project or code snippet that
 demonstrates the potential vulnerability. Include clear instructions on how to

docs/ref/models/expressions.txt

@@ -438,11 +438,11 @@ return type.
 
     Built-in database functions (such as
     :class:`~django.db.models.functions.Cast`) vary in whether arguments such
-    as ``output_field`` can be supplied positionally or only by keyword. For
-    ``output_field`` and several other cases, the input ultimately reaches
-    ``Func()`` as a keyword argument, so the advice to avoid constructing
-    keyword arguments from untrusted user input applies as equally to these
-    arguments as it does to ``**extra``.
+    as ``output_field`` can be supplied as positional arguments or only by
+    keyword. For ``output_field`` and several other cases, the input ultimately
+    reaches ``Func()`` as a keyword argument, so the advice to avoid
+    constructing keyword arguments from untrusted user input applies as equally
+    to these arguments as it does to ``**extra``.
 
 ``Aggregate()`` expressions
 ---------------------------

docs/releases/6.1.txt

@@ -242,7 +242,7 @@ Management Commands
 
 * Management commands now set :class:`~argparse.ArgumentParser`\'s
   ``suggest_on_error`` argument to ``True`` by default on Python 3.14, enabling
-  suggestions for mistyped subcommand names and argument choices.
+  suggestions for incorrectly typed subcommand names and argument choices.
 
 * The :djadmin:`loaddata` command now calls
   :data:`~django.db.models.signals.m2m_changed` signals with ``raw=True`` when
@@ -340,7 +340,7 @@ Utilities
 ~~~~~~~~~
 
 * :func:`~django.utils.dateparse.parse_duration` now supports ISO 8601
-  durations expressed in weeks (``PnW``).
+  time periods expressed in weeks (``PnW``).
 
 Validators
 ~~~~~~~~~~

docs/spelling_wordlist

@@ -4,6 +4,7 @@ accessors
 Aceh
 admindocs
 affordances
+ai
 Ai
 Alchin
 allowlist
@@ -245,6 +246,8 @@ kwargs
 Kyrgyz
 latin
 lawrence
+lexeme
+lexemes
 Libera
 lifecycle
 lifecycles
@@ -531,6 +534,7 @@ unapplied
 unapplying
 uncategorized
 unclaim
+unclosed
 uncopyable
 unencoded
 unencrypted