Fix instructions for updating contrib repo in release docs (#6939)

Signed-off-by: Anthony J Mirabella <a9@aneurysm9.com>
open-telemetry · Jan 12, 2023 · f2a0133 · f2a0133
1 parent 7e8b1c4
commit f2a0133
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/docs/release.md b/docs/release.md
@@ -64,16 +64,17 @@ It is possible that a core approver isn't a contrib approver. In that case, the
 
 1. Prepare Contrib for release.
 
-  * Update CHANGELOG.md file, this is done via `chloggen`. Run the following command from the root of the opentelemetry-collector-contrib repo:
+   * Update CHANGELOG.md file, this is done via `chloggen`. Run the following command from the root of the opentelemetry-collector-contrib repo:
       * `make chlog-update VERSION=v0.55.0`
 
-  * Use multimod to update the version of the collector package:
+   * Use multimod to update the version of the collector package:
 
       * Update [versions.yaml](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/versions.yaml) and commit it
 
       * Run `make multimod-prerelease`
 
-1. Update the Core dependency to the Core version we just released with `make update-otel OTEL_VERSION=v0.55.0` command. Create a PR with both the changes, get it approved and merged.
+1. Update the Core dependency to the Core version we just released with
+`make multimod-sync` command. Create a PR with both the changes, get it approved and merged.
 
 1. Create a branch named `release/<release-series>` (e.g. `release/v0.45.x`) in Contrib from the changelog update commit and push it to `open-telemetry/opentelemetry-collector-contrib`.