JT feedback

Author: norareidy

docs/eloquent-models/model-class.txt

@@ -295,12 +295,8 @@ including this trait, you can make the third-party class compatible with
 MongoDB.
 
 When you apply the ``DocumentModel`` trait to a model class, you must
-declare the following properties in your class:
-
-- ``$primaryKey = '_id'``, because the ``_id`` field uniquely
-  identifies MongoDB documents
-- ``$keyType = 'string'``, because the {+odm-short+} casts MongoDB
-  ``ObjectId`` values to type ``string``
+set the  ``$keyType`` property to ``'string'`` as the {+odm-short+}
+casts MongoDB ``ObjectId`` values to type ``string``.
 
 Extended Class Example
 ~~~~~~~~~~~~~~~~~~~~~~

docs/query-builder.txt

@@ -188,8 +188,8 @@ the value of the ``title`` field is ``"Back to the Future"``:
 
 .. note::
 
-	Starting in v5.0, you can use the ``id`` alias in your queries to represent
-	the ``_id`` field in MongoDB documents, as shown in the preceding
+	You can use the ``id`` alias in your queries to represent the
+	``_id`` field in MongoDB documents, as shown in the preceding
    code. When you run a find operation using the query builder, {+odm-short+}
 	automatically converts between ``id`` and ``_id``. Because of this behavior,
 	you cannot have two separate ``id`` and ``_id`` fields in your documents.