docker-compose formating edits

sourcegraph · Feb 3, 2025 · 2952920 · 2952920
1 parent 4440ca6
commit 2952920
Showing 1 changed file with 5 additions and 4 deletions.
diff --git a/docs/admin/deploy/docker-compose/upgrade.mdx b/docs/admin/deploy/docker-compose/upgrade.mdx
@@ -78,14 +78,15 @@ To perform a multi-version upgrade via migrators [upgrade](/admin/updates/migrat
 
 4. **Run Migrator with the `upgrade` command**:
    - *For more detailed instructions and available command flags see our [migrator docs](/admin/updates/migrator/migrator-operations#docker-compose).*
-    1. If the migrator `image:` in your `docker-compose.yaml` wasn't updated to in the **latest** release of `migrator` in step 2 set migrator's image to the latest release. **Example:**
+    1. If the migrator `image:` in your `docker-compose.yaml` wasn't updated to in the **latest** release of `migrator` in step 2 set migrator's image to the latest release.
+    **Example:**
     ```yaml
     migrator:
       container_name: migrator
       image: 'index.docker.io/sourcegraph/migrator:6.0.0'
     ```
-    > *Note: Always use the latest image version of migrator for migrator commands, except the startup command `up`*
-    2. Set the migrator `command:` to `upgrade` you'll need to supply a `--to=` argument. **Example:**
+    2. Set the migrator `command:` to `upgrade` you'll need to supply a `--to=` argument to the version you're upgrading to. 
+    **Example:**
     ```yaml
     command: ['upgrade', '--from=v5.9.0', '--to=v6.0.0']
     ```
@@ -122,7 +123,7 @@ To perform a multi-version upgrade via migrators [upgrade](/admin/updates/migrat
     migrator | ✅ Schema migrations complete
     migrator exited with code 0
     ```
-5. **Set Migrator to `up`**
+5. **Run Migrator with the `up` command**
    - Set your migrator `command:` to `up`
    > *Note: If you aren't upgrading to the latest release remember to set the migrator image back to the version you are upgrading to.*
    **Example:**