JM tech review 4

Author: rustagir

docs/eloquent-models/model-class.txt

@@ -363,10 +363,10 @@ model. In this method, you can specify the changes to make to an older
 model to update it to match the current schema version.
 
 When you save a model that does not have a schema version
-specified, Laravel assumes that it follows the latest schema version.
-When you retrieve a model that does not contain the ``schema_version``
-field, Laravel assumes that its schema version is ``0`` and performs the
-migration.
+specified, the ``HasSchemaVersion`` trait assumes that it follows the
+latest schema version. When you retrieve a model that does not contain
+the ``schema_version`` field, the trait assumes that its schema version
+is ``0`` and performs the migration.
 
 Schema Versioning Example
 ~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -395,11 +395,11 @@ You can define the new model class with the following behavior:
 
 In the ``"WASP-39 b"`` document in the following code, the
 ``schema_version`` field value is less than ``2``. When you retrieve the
-document, Laravel adds the ``galaxy`` field and updates the schema
+document, {+odm-short+} adds the ``galaxy`` field and updates the schema
 version to the current version, ``2``.
 
 The ``"Saturn"`` document does not contain the ``schema_version`` field,
-so Laravel assigns it the current schema version upon saving.
+so {+odm-short+} assigns it the current schema version upon saving.
 
 Finally, the code retrieves the models from the collection to
 demonstrate the changes: