3 files changed, 13 insertions, 13 deletions
diff --git a/docs/ref/contrib/postgres/fields.txt b/docs/ref/contrib/postgres/fields.txt
index 983b4234c9..8200cee3f1 100644
--- a/docs/ref/contrib/postgres/fields.txt
+++ b/docs/ref/contrib/postgres/fields.txt
@@ -11,8 +11,8 @@ Indexing these fields
 =====================
 
 :class:`~django.db.models.Index` and :attr:`.Field.db_index` both create a
-B-tree index, which isn't particularly helpful when querying complex data types.
-Indexes such as :class:`~django.contrib.postgres.indexes.GinIndex` and
+B-tree index, which isn't particularly helpful when querying complex data
+types. Indexes such as :class:`~django.contrib.postgres.indexes.GinIndex` and
 :class:`~django.contrib.postgres.indexes.GistIndex` are better suited, though
 the index choice is dependent on the queries that you're using. Generally, GiST
 may be a good choice for the :ref:`range fields <range-fields>` and
@@ -450,8 +450,8 @@ operator ``?|``. For example:
 ``has_keys``
 ~~~~~~~~~~~~
 
-Returns objects where all of the given keys are in the data. Uses the SQL operator
-``?&``. For example:
+Returns objects where all of the given keys are in the data. Uses the SQL
+operator ``?&``. For example:
 
 .. code-block:: pycon
 
@@ -741,8 +741,8 @@ passed range.
 ``not_gt``
 ^^^^^^^^^^
 
-The returned ranges do not contain any points greater than the passed range, that
-is the upper bound of the returned range is at most the upper bound of the
+The returned ranges do not contain any points greater than the passed range,
+that is the upper bound of the returned range is at most the upper bound of the
 passed range.
 
     >>> Event.objects.filter(ages__not_gt=NumericRange(3, 10))
diff --git a/docs/ref/contrib/postgres/lookups.txt b/docs/ref/contrib/postgres/lookups.txt
index e7ccf1c21b..6dc6618f9a 100644
--- a/docs/ref/contrib/postgres/lookups.txt
+++ b/docs/ref/contrib/postgres/lookups.txt
@@ -88,7 +88,8 @@ can be chained with other lookup functions. To use it, you need to add
 ``'django.contrib.postgres'`` in your :setting:`INSTALLED_APPS` and activate
 the `unaccent extension on PostgreSQL`_. The
 :class:`~django.contrib.postgres.operations.UnaccentExtension` migration
-operation is available if you want to perform this activation using migrations).
+operation is available if you want to perform this activation using
+migrations).
 
 .. _unaccent extension on PostgreSQL: https://www.postgresql.org/docs/current/unaccent.html
 
@@ -105,7 +106,7 @@ The ``unaccent`` lookup can be used on
 
 .. warning::
 
-    ``unaccent`` lookups should perform fine in most use cases. However, queries
-    using this filter will generally perform full table scans, which can be slow
-    on large tables. In those cases, using dedicated full text indexing tools
-    might be appropriate.
+    ``unaccent`` lookups should perform fine in most use cases. However,
+    queries using this filter will generally perform full table scans, which
+    can be slow on large tables. In those cases, using dedicated full text
+    indexing tools might be appropriate.
diff --git a/docs/ref/contrib/postgres/search.txt b/docs/ref/contrib/postgres/search.txt
index 220ab4c591..4647fcbfa2 100644
--- a/docs/ref/contrib/postgres/search.txt
+++ b/docs/ref/contrib/postgres/search.txt
@@ -295,8 +295,7 @@ the search vector you wish to use. For example::
         name="search_vector_idx",
     )
 
-The PostgreSQL documentation has details on
-`creating indexes for full text search
+The PostgreSQL docs has details on `creating indexes for full text search
 <https://www.postgresql.org/docs/current/textsearch-tables.html#TEXTSEARCH-TABLES-INDEX>`_.
 
 ``SearchVectorField``