docs: auth0 migration guid formatting improvements

Author: wassimoo

docs/migrate-to-ory/auth0.mdx

@@ -19,8 +19,8 @@ Before you begin, ensure you have:
 
 - **Auth0 account** with admin access to export user data
 - **Ory account** and CLI installed
-{/* TODO: change this to refer to new migration guide (docs/migrate-to-ory/migrate/create-project.mdx) */}
-- **Ory project** created - See [creating a project](index.mdx) for instructions 
+  {/* TODO: change this to refer to new migration guide (docs/migrate-to-ory/migrate/create-project.mdx) */}
+- **Ory project** created - See [creating a project](index.mdx) for instructions
 - **Required tools**:
   - [jq](https://jqlang.org/) - Command-line JSON processor
   - [Gzip](https://www.gnu.org/software/gzip/) - Compression utility
@@ -54,7 +54,9 @@ Follow these steps to get the Management API Access Token and connection ID:
 2. Select **Auth0 Management API** and go to the **API Explorer** tab. Copy the displayed token.
 
    :::warning Token expiration
+
    The token is valid for 24 hours by default and is configurable.
+
    :::
 
 3. Go to **Authentication** and navigate to **Database**.
@@ -86,15 +88,18 @@ Follow these steps to export the user data:
 
 ### 2. Export password hashes
 
-Exporting password hashes is optional but recommended. Because password hashes are considered sensitive information, Auth0 doesn't export them as part of the general export process. To get the password hashes and other password-related information, you must [create an Auth0 support ticket](#create-auth0-support-ticket).
+Exporting password hashes is optional but recommended. Because password hashes are considered sensitive information, Auth0 doesn't
+export them as part of the general export process. To get the password hashes and other password-related information, you must
+[create an Auth0 support ticket](#create-auth0-support-ticket).
 
 If you get your users' password hashes and import them to Ory, users can log in to their accounts using the same credentials they
 used before the migration. If you can't get users' password hashes, you can still import Auth0 user accounts to Ory and migrate
 them using a [Password migration hook](../kratos/manage-identities/25_import-user-accounts-identities.mdx).
 
-:::note 
-Password hash exports are not available for Auth0's Free subscription tier. You'll need a paid Auth0 plan to request this
-data. 
+:::note
+
+Password hash exports are not available for Auth0's Free subscription tier. You'll need a paid Auth0 plan to request this data.
+
 :::
 
 #### Create Auth0 support ticket
@@ -138,15 +143,15 @@ export ORY_WORKSPACE_ID='{your-workspace-id}'
 If you don't have these values, you can retrieve them:
 
 - **Using the CLI**: Run `ory list projects` to see all your projects and their IDs
-- **Using the Console**: Go to [Ory Console](https://console.ory.sh/), select your project, and find the IDs in the project settings
+- **Using the Console**: Go to [Ory Console](https://console.ory.sh/), select your project, and find the IDs in the project
+  settings
 
 :::
 
-
-
 ### 2. Configure identity schema
 
-Before importing users, you need to configure your Ory project's identity schema to match your Auth0 setup. Since Auth0 users authenticate with email and password, configure the identity schema to use the email preset.
+Before importing users, you need to configure your Ory project's identity schema to match your Auth0 setup. Since Auth0 users
+authenticate with email and password, configure the identity schema to use the email preset.
 
 Update your project's identity schema:
 
@@ -173,7 +178,8 @@ export AUTH0_PWEXPORT="{path-to-the-json-file-with-password-hashes}"
 :::info Migration Mode
 
 - Set `RESERVE_ONLY="false"` if you have password hashes
-- Set `RESERVE_ONLY="true"` if you don't have password hashes 
+- Set `RESERVE_ONLY="true"` if you don't have password hashes
+
 :::
 
 ### 2. Run import script