diff --git a/docs/guide/db-migrations.md b/docs/guide/db-migrations.md
index c2e0996..faefb81 100644
--- a/docs/guide/db-migrations.md
+++ b/docs/guide/db-migrations.md
@@ -38,6 +38,13 @@ command `yii help migrate`.
 > Tip: migrations could affect not only database schema but adjust existing data to fit new schema, create RBAC
   hierarchy or clean up cache.
 
+> Note: When manipulating data using a migration you may find that using your [Active Record](db-active-record.md) classes
+> for this might be useful because some of the logic is already implemented there. Keep in mind however, that in contrast
+> to code written in the migrations, who's nature is to stay constant forever, application logic is subject to change.
+> So when using Active Record in migration code, changes to the logic in the Active Record layer may accidentally break
+> existing migrations. For this reason migration code should be kept independent from other application logic such
+> as Active Record classes.
+
 
 ## Creating Migrations <span id="creating-migrations"></span>
 
@@ -716,14 +723,6 @@ Below is the list of all these database accessing methods:
 > ```
 
 
-> Note: When manipulating data using a migration you may find that using your [Active Record](db-active-record.md) classes
-> for this might be useful because some of the logic is already implemented there. Keep in mind however, that in contrast
-> to code written in the migrations, who's nature is to stay constant forever, application logic is subject to change.
-> So when using Active Record in migration code, changes to the logic in the Active Record layer may accidentally break
-> existing migrations. For this reason migration code should be kept independent from other application logic such
-> as Active Record classes.
-
-
 ## Applying Migrations <span id="applying-migrations"></span>
 
 To upgrade a database to its latest structure, you should apply all available new migrations using the following command: