feedback 2

Author: norareidy

source/interact-data/transactions.txt

@@ -44,7 +44,7 @@ manually start a session before running a transaction.
    {+django-odm+}'s support for the {+framework+} transaction API
    has several limitations. To view a list of limitations, see
    :ref:`Database and Collection Support <django-feature-compat-db-coll>`
-   in the Django and MongoDB Feature Compatibility guide.
+   in the {+framework+} and MongoDB Feature Compatibility guide.
 
 Sample Data
 ~~~~~~~~~~~
@@ -129,7 +129,7 @@ the atomic block, you might obscure these errors from {+framework+}. Since
 {+framework+} uses errors to determine whether to commit or roll
 back a transaction, this can cause unexpected behavior.
 
-If a transaction does not succeed, Django does not revert any changes made
+If a transaction does not succeed, {+framework+} does not revert any changes made
 to a model's fields. To avoid inconsistencies between your models and database documents,
 you might need to manually restore the original field values.
 

source/limitations-upcoming.txt

@@ -250,7 +250,7 @@ Database and Collection Support
      - ✓
 
    * - Transactions
-     - *Partially Supported*. You can use {+framework+}'s transactions API with the
+     - ✓ You can use {+framework+}'s transactions API with the
        following limitations:
 
        - ``QuerySet.union()`` is not supported within a transaction.
@@ -259,7 +259,7 @@ Database and Collection Support
          a transaction, and any subsequent atomic blocks have no effect.
        - Migration operations do not run inside a transaction.
        - Your MongoDB deployment must be a replica set or sharded cluster.
-     - *Partially Supported*.
+     - ✓
 
 Django Features
 ---------------