Removed hyphen from pre-/re- prefixes.

"prepopulate", "preload", and "preprocessing" are already in the
spelling_wordlist.

This also removes hyphen from double "e" combinations with "pre" and
"re", e.g. preexisting, preempt, reestablish, or reenter.

See also:
- https://ahdictionary.com/word/search.html?q=rerun
- https://ahdictionary.com/word/search.html?q=recreate
- https://ahdictionary.com/word/search.html?q=predetermined
- https://ahdictionary.com/word/search.html?q=reuse
- https://ahdictionary.com/word/search.html?q=reopening

5 files changed, 6 insertions, 6 deletions

diff --git a/docs/releases/1.0.txt b/docs/releases/1.0.txt
index 84e4837692..1fc48330f6 100644
--- a/docs/releases/1.0.txt
+++ b/docs/releases/1.0.txt
@@ -73,8 +73,8 @@ You'll know that you're looking at something new or changed.
 
 The other major highlights of Django 1.0 are:
 
-Re-factored admin application
------------------------------
+Refactored admin application
+----------------------------
 
 The Django administrative interface (``django.contrib.admin``) has been
 completely refactored; admin definitions are now completely decoupled from model
diff --git a/docs/releases/1.1.3.txt b/docs/releases/1.1.3.txt
index c88d676f7e..7be4061957 100644
--- a/docs/releases/1.1.3.txt
+++ b/docs/releases/1.1.3.txt
@@ -45,6 +45,6 @@ password hashes.
 To remedy this, ``django.contrib.admin`` will now validate that
 querystring lookup arguments either specify only fields on the model
 being viewed, or cross relations which have been explicitly
-allowed by the application developer using the pre-existing
+allowed by the application developer using the preexisting
 mechanism mentioned above. This is backwards-incompatible for any
 users relying on the prior ability to insert arbitrary lookups.
diff --git a/docs/releases/1.2.4.txt b/docs/releases/1.2.4.txt
index 26a67d9d1e..587bffebde 100644
--- a/docs/releases/1.2.4.txt
+++ b/docs/releases/1.2.4.txt
@@ -45,7 +45,7 @@ password hashes.
 To remedy this, ``django.contrib.admin`` will now validate that
 querystring lookup arguments either specify only fields on the model
 being viewed, or cross relations which have been explicitly
-allowed by the application developer using the pre-existing
+allowed by the application developer using the preexisting
 mechanism mentioned above. This is backwards-incompatible for any
 users relying on the prior ability to insert arbitrary lookups.
 
diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt
index aac7c80c59..4109565448 100644
--- a/docs/releases/1.6.txt
+++ b/docs/releases/1.6.txt
@@ -74,7 +74,7 @@ Persistent database connections
 -------------------------------
 
 Django now supports reusing the same database connection for several requests.
-This avoids the overhead of re-establishing a connection at the beginning of
+This avoids the overhead of reestablishing a connection at the beginning of
 each request. For backwards compatibility, this feature is disabled by
 default. See :ref:`persistent-database-connections` for details.
 
diff --git a/docs/releases/3.1.1.txt b/docs/releases/3.1.1.txt
index 906e52924a..c833807338 100644
--- a/docs/releases/3.1.1.txt
+++ b/docs/releases/3.1.1.txt
@@ -74,7 +74,7 @@ Bugfixes
   grouping by :class:`~django.db.models.JSONField` with a custom
   :attr:`~django.db.models.JSONField.decoder` (:ticket:`31956`). As a
   consequence, fetching a ``JSONField`` with raw SQL now returns a string
-  instead of pre-loaded data. You will need to explicitly call ``json.loads()``
+  instead of preloaded data. You will need to explicitly call ``json.loads()``
   in such cases.
 
 * Fixed a ``QuerySet.delete()`` crash on MySQL, following a performance