RM feedback

Author: norareidy

source/model-data/models.txt

@@ -104,7 +104,7 @@ that {+django-odm+} supports:
      - | Stores an IPv4 or IPv6 address in string format.
 
    * - ``IntegerField``
-     - | Stores integer values.
+     - | Stores integer values up to 32 bits in size.
 
    * - ``JSONField``
      - | Stores JSON data. To learn more about this field, see the
@@ -297,7 +297,7 @@ class that includes the following information:
 Use Advanced Fields
 -------------------
 
-This section how to use the following field types
+This section shows how to use the following field types
 in your Django models:
 
 - :ref:`JSONField <django-models-json>`
@@ -321,19 +321,6 @@ stores this data in BSON, or Binary JSON, format.
     MongoDB ``Object``. To learn more about this field, see the 
     :ref:`django-models-embedded` section of this guide.
 
-{+django-odm+}'s support for ``JSONField`` has the following limitations:
-
-- If you set the field's value to ``None``, {+django-odm+} stores its value as 
-  a SQL ``NULL`` value. Alternatively, you can set the ``JSONField`` value
-  to ``Value(None, JSONField())``, which represents the JSON scalar ``null``.
-  However, there is no way to distinguish between the SQL ``NULL`` and the JSON
-  ``null`` when querying.
-
-- Some queries that use ``Q`` objects might not return the expected results.
-
-- When querying for fields that have a ``None`` value, {+django-odm+} incorrectly
-  returns documents in which the field doesn't exist.
-
 Example
 ```````
 
@@ -354,6 +341,23 @@ user ratings for each ``Movie`` object:
    To learn how to query data stored in a ``JSONField``, see
    :ref:`django-query-jsonfield` in the Specify a Query guide.
 
+Limitations
+```````````
+
+{+django-odm+}'s support for ``JSONField`` has the following limitations:
+
+- If you set the field's value to ``None``, {+django-odm+} stores its value as 
+  a SQL ``NULL`` value. Alternatively, you can set the ``JSONField`` value
+  to ``Value(None, JSONField())``, which represents the JSON scalar ``null``.
+  However, there is no way to distinguish between the SQL ``NULL`` and the JSON
+  ``null`` when querying.
+
+- Some queries that use ``Q`` objects might not return the expected results,
+  particularly when using the ``QuerySet.exclude()`` method.
+
+- When querying for fields that have a ``None`` value, {+django-odm+} incorrectly
+  returns documents in which the field doesn't exist.
+
 .. _django-models-array:
 
 Use an ArrayField