Improving structure.

Author: Oxyjun

src/content/docs/durable-objects/reference/durable-objects-migrations.mdx

@@ -139,19 +139,16 @@ To apply a Rename migration:
 	renamed_classes = [{from = "<OldDurableObject>", to = "<UpdatedDurableObject>" }] # Array of rename directives
 	```
 	</WranglerConfig>
+
 	The Rename migration contains:
 	- A `tag` to identify the migration.
 	- The `renamed_classes` array, which contains objects with `from` and `to` properties.
-		- `from` property is the name of the old Durable Object class.
-		- `to` property is the name of the renamed Durable Object class.
+		- `from` property is the old Durable Object class name.
+		- `to` property is the renamed Durable Object class name.
 2. Reference the new Durable Object class name in your Worker code.
 3. Deploy the Worker.
 </Steps>
 
-:::note
-To apply both migrations in the same deploy, add the migrations configuration and deploy the Worker.
-:::
-
 <Details header = "Rename migration example">
 
 To rename a Durable Object class, from `OldName` to `UpdatedName`, your `wrangler.toml / wrangler.json` file should look like the following:
@@ -209,16 +206,6 @@ To apply a Transfer migration:
 3. Deploy the Worker.
 </Steps>
 
-:::caution[Important]
-- The destination class (the class that stored Durable Objects are being transferred to) for a Rename or Transfer migration must be exported by the deployed Worker.
-
-- You should not create the destination Durable Object class before running a Rename or Transfer migration. The migration will create the destination class for you.
-
-- After a Rename or Transfer migration, requests to the destination Durable Object class will have access to the source Durable Object's stored data.
-
-- After a migration, any existing bindings to the original Durable Object class (for example, from other Workers) will automatically forward to the updated destination class. However, any Workers bound to the updated Durable Object class must update their Durable Object binding configuration in the `wrangler` configuration file for their next deployment.
-:::
-
 <Details header = "Transfer migration example">
 
 You can transfer stored Durable Objects from `DurableObjectExample` to `TransferredClass` from a Worker script named `OldWorkerScript`. The configuration of the `wrangler.toml / wrangler.json` file for your new Worker code (destination Worker code) would look like this:
@@ -238,7 +225,7 @@ transferred_classes = [{from = "DurableObjectExample", from_script = "OldWorkerS
 </WranglerConfig>
 
 </Details>
-## Durable Object migrations configuration in the Wrangler configuration file
+## Migration Wrangler configuration
 
 - Migrations are performed through the `[[migrations]]` configurations key in your `wrangler.toml` file or `migration` key in your `wrangler.json` file.
 
@@ -252,6 +239,16 @@ transferred_classes = [{from = "DurableObjectExample", from_script = "OldWorkerS
 
 - Each migration in the list can have multiple directives, and multiple migrations can be specified as your project grows in complexity.
 
+:::caution[Important]
+- The destination class (the class that stored Durable Objects are being transferred to) for a Rename or Transfer migration must be exported by the deployed Worker.
+
+- You should not create the destination Durable Object class before running a Rename or Transfer migration. The migration will create the destination class for you.
+
+- After a Rename or Transfer migration, requests to the destination Durable Object class will have access to the source Durable Object's stored data.
+
+- After a migration, any existing bindings to the original Durable Object class (for example, from other Workers) will automatically forward to the updated destination class. However, any Workers bound to the updated Durable Object class must update their Durable Object binding configuration in the `wrangler` configuration file for their next deployment.
+:::
+
 :::note
 Note that `.toml` files do not allow line breaks in inline tables (the `{key = "value"}` syntax), but line breaks in the surrounding inline array are acceptable.
 :::