diff --git a/source/get-started.txt b/source/get-started.txt
index 5a41e39..3795196 100644
--- a/source/get-started.txt
+++ b/source/get-started.txt
@@ -1,8 +1,8 @@
 .. _django-get-started:
 
-===============================
+=======================================
 Get Started with {+django-odm+}
-===============================
+=======================================
 
 .. contents:: On this page
    :local:
diff --git a/source/limitations-upcoming.txt b/source/limitations-upcoming.txt
index c015ede..609580c 100644
--- a/source/limitations-upcoming.txt
+++ b/source/limitations-upcoming.txt
@@ -75,10 +75,6 @@ Indexes
 - Creating geospatial indexes through the Django Indexes API
 - Updating indexes in ``EmbeddedModelFields`` after model creation
 
-To learn how to run unsupported database operations by operating directly on
-your ``MongoClient`` instance, see :ref:`django-client-operations`  in the
-Perform Raw Database Queries guide.
-
 .. _django-limitations-models-fields:
 
 Fields
@@ -88,15 +84,15 @@ Fields
 
 - ``ArrayField``
 
-  - {+django-odm+} does not support ``ArrayField`` polymorphism.
-  - {+django-odm+} does not support nesting an ``EmbeddedModelField`` within an ``ArrayField``.
+  - ``ArrayField`` polymorphism is not supported.
+  - Nested ``EmbeddedModelField`` values within an ``ArrayField`` are not supported.
 
 - ``EmbeddedModelField``
 
   - ``EmbeddedModel`` schema changes do not register after creation.
   - Embedded documents cannot take Django foreign keys.
-  - {+django-odm+} does not support arbitrary or untyped embedded model
-    fields. You must derive all fields from a ``EmbeddedModel`` class.
+  - Arbitrary or untyped embedded model fields are not supported. You must
+    derive all fields from a ``EmbeddedModel`` class.
 
 - ``JSONField``
 
@@ -110,8 +106,7 @@ Fields
 
 - ``DateTimeField``
 
-  - {+django-odm+} does not support microsecond granularity for
-    ``DateTimeField``.
+  - Microsecond granularity for ``DateTimeField`` values is not supported.
 
 - ``DurationField``
 
@@ -156,9 +151,10 @@ that span multiple collections.
 Geospatial Queries
 ``````````````````
 
-- {+django-odm+} does not support ``GeoDjango``.
-- {+django-odm+} does not have any Django lookup operators for MongoDB-specific
-  geospatial queries.
+{+django-odm+} does not support the following geospatial query features:
+
+- ``GeoDjango``
+- Django lookup operators for MongoDB-specific geospatial queries
 
 Aggregation Operators
 `````````````````````
@@ -208,13 +204,14 @@ Django Management Command Limitations
 Migration Limitations
 ~~~~~~~~~~~~~~~~~~~~~
 
-- {+django-odm+} does not support enforced schema validation. To learn how to
-  enforce schema validation in your application, see the :manual:`Specify JSON
+{+django-odm+} does not support the following migration features:
+
+- Enforced schema validation. To learn how to enforce schema
+  validation in your application, see the :manual:`Specify JSON
   Schema Validation </core/schema-validation/specify-json-schema/>` guide in the
   {+mdb-server+} manual.
-- {+django-odm+} does not support `DDL Transactions
-  <{+django-docs+}/topics/migrations/#transactions>`__.
-- {+django-odm+} does not support the ``migrate --fake-initial`` command.
+- `DDL Transactions <{+django-docs+}/topics/migrations/#transactions>`__.
+- ``migrate --fake-initial`` command.
 
 .. _django-limitations-async: