diff --git a/docusaurus/docs/dev-docs/database-migrations.md b/docusaurus/docs/dev-docs/database-migrations.md
index 2f22312e60..ef4f1b1c8c 100644
--- a/docusaurus/docs/dev-docs/database-migrations.md
+++ b/docusaurus/docs/dev-docs/database-migrations.md
@@ -7,7 +7,7 @@ description: Strapi database migrations are ways to modify the database
 
 Database migrations exist to run one-time queries against the database, typically to modify the tables structure or the data when upgrading the Strapi application. These migrations are run automatically when the application starts and are executed before the automated schema migrations that Strapi also performs on boot.
 
-:::callout 🚧  Experimental feature
+:::callout 🚧 Experimental feature
 Database migrations are experimental. This feature is still a work in progress and will continue to be updated and improved. In the meantime, feel free to ask for help on the [forum](https://forum.strapi.io/) or on the community [Discord](https://discord.strapi.io).
 :::
 
@@ -18,10 +18,11 @@ Migrations are run using JavaScript migration files stored in `./database/migrat
 Strapi automatically detects migration files and run them once at the next startup in alphabetical order. Every new file is executed once. Migrations are run before the database tables are synced with the content-types schemas.
 
 :::warning
-* Currently Strapi does not support down migrations. This means that if you need to revert a migration, you will have to do it manually. It is planned to implement down migrations in the future but no timeline is currently available.
 
-* Strapi will delete any unknown tables without warning. This means that database migrations can only be used to keep data when changing the Strapi schema. The `forceMigration` and `runMigrations` [database configuration parameters](/dev-docs/configurations/database#settings-configuration-object) can be used to fine-tune the database migrations behavior.
-:::
+- Currently Strapi does not support down migrations. This means that if you need to revert a migration, you will have to do it manually. It is planned to implement down migrations in the future but no timeline is currently available.
+
+- Strapi will delete any unknown tables without warning. This means that database migrations can only be used to keep data when changing the Strapi schema. The `forceMigration` and `runMigrations` [database configuration parameters](/dev-docs/configurations/database#settings-configuration-object) can be used to fine-tune the database migrations behavior.
+  :::
 
 Migration files should export the function `up()`, which is used when upgrading (e.g. adding a new table `my_new_table`).
 
@@ -40,7 +41,7 @@ To create a migration file:
 2. Copy and paste the following template in the previously created file:
 
 ```jsx
-'use strict'
+"use strict";
 
 async function up(knex) {}
 
@@ -48,27 +49,60 @@ module.exports = { up };
 ```
 
 3. Fill in the template by adding actual migration code inside the `up()` function.
-`up()` receives a [Knex instance](https://knexjs.org/), already in a transaction state, that can be used to run the database queries.
+   `up()` receives a [Knex instance](https://knexjs.org/), already in a transaction state, that can be used to run the database queries.
 
 <details>
 <summary>Example of migration file</summary>
 
 ```jsx title="./database/migrations/2022.05.10T00.00.00.name-of-my-migration.js"
-
 module.exports = {
   async up(knex) {
     // You have full access to the Knex.js API with an already initialized connection to the database
 
     // Example: renaming a table
-    await knex.schema.renameTable('oldName', 'newName');
+    await knex.schema.renameTable("oldName", "newName");
 
     // Example: renaming a column
-    await knex.schema.table('someTable', table => {
-      table.renameColumn('oldName', 'newName');
+    await knex.schema.table("someTable", (table) => {
+      table.renameColumn("oldName", "newName");
     });
 
     // Example: updating data
-    await knex.from('someTable').update({ columnName: 'newValue' }).where({ columnName: 'oldValue' });
+    await knex
+      .from("someTable")
+      .update({ columnName: "newValue" })
+      .where({ columnName: "oldValue" });
+  },
+};
+```
+
+</details>
+
+## Additional considerations
+
+### Using Strapi Instance for migrations
+
+If a user opts not to use Knex directly for migrations and instead utilizes the Strapi instance, it is important to wrap the migration code with `strapi.db.transaction()`. Failure to do so may result in migrations not rolling back if an error occurs.
+
+<details>
+<summary>Example of migration file with Strapi instance</summary>
+
+```jsx title="./database/migrations/2022.05.10T00.00.00.name-of-my-migration.js"
+module.exports = {
+  async up() {
+    await strapi.db.transaction(async () => {
+      // Your migration code here
+
+      // Example: creating new entries
+      await strapi.entityService.create("api::article.article", {
+        data: {
+          title: "My Article",
+        },
+      });
+
+      // Example: custom service method
+      await strapi.service("api::article.article").updateRelatedArticles();
+    });
   },
 };
 ```