Update README.md
diff --git a/distro/README.md b/distro/README.md
index 77fffd6..d1f9e74 100644
--- a/distro/README.md
+++ b/distro/README.md
@@ -1,47 +1,16 @@
# Updating bazelbuild/platforms
-WARNING: These are what worked last time. Reality might be different.
-
## Step 1: Make the release
-- Pick a new version number
-- Update version.bzl
-- Run distro/makerel.sh
-- Go to the [Releases](https://github.com/bazelbuild/platforms/releases) page
-- Draft a new release
- - Name the release with a version number
- - Use the version number as the title
- - Copy the description that makerel.sh produced to the description field.
- - upload the generated tar file
+1. Pick a new version number.
+1. Prepare a release bug ([example](https://github.com/bazelbuild/platforms/issues/112)).
+1. Submit a PR that updates `MODULE.bazel` and `version.bzl` to the new version ([example](https://github.com/bazelbuild/platforms/pull/117)).
+1. [Start](https://github.com/bazelbuild/platforms/releases/new) a new release draft.
+1. Run `distro/makerel.sh` to locally create the release. This creates a release archive (`.tar.gz`) on the local machine, emits suggested release notes, and emits instructions for mirroring the archive to `htps://mirror.bazel.build`.
+1. Using the results of the last step, fill out the release draft consistent with [previous releases](https://github.com/bazelbuild/platforms/releases). Add the local `platforms-<version>.tar.gz` to the draft's `Attach binaries by dropping them here or selecting them` pane.
+1. Click `Publish release` to release.
-- use https://github.com/bazelbuild/continuous-integration/blob/HEAD/mirror/mirror.sh to mirror the file
-
-## Step 2: Update Bazel
-
-- Edit `distdir_deps.bzl`
-- Merge the PR
-
-Sample diff:
-
-```
-diff --git a/distdir_deps.bzl b/distdir_deps.bzl
-index ed49a563bc..1739a25c2a 100644
---- a/distdir_deps.bzl
-+++ b/distdir_deps.bzl
-@@ -20,11 +20,11 @@ DIST_DEPS = {
- #
- ########################################
- "platforms": {
-- "archive": "platforms-0.0.2.tar.gz",
-- "sha256": "48a2d8d343863989c232843e01afc8a986eb8738766bfd8611420a7db8f6f0c3",
-+ "archive": "platforms-0.0.3.tar.gz",
-+ "sha256": "460caee0fa583b908c622913334ec3c1b842572b9c23cf0d3da0c2543a1a157d",
- "urls": [
-- "https://mirror.bazel.build/github.com/bazelbuild/platforms/releases/download/0.0.2/platforms-0.0.2.tar.gz",
-- "https://github.com/bazelbuild/platforms/releases/download/0.0.2/platforms-0.0.2.tar.gz",
-+ "https://mirror.bazel.build/github.com/bazelbuild/platforms/releases/download/0.0.3/platforms-0.0.3.tar.gz",
-+ "https://github.com/bazelbuild/platforms/releases/download/0.0.3/platforms-0.0.3.tar.gz",
- ],
- "used_in": [
- "additional_distfiles",
-```
+## Step 2: Register with the Bazel Central Registry
+1. Create a PR on https://github.com/bazelbuild/bazel-central-registry with [this pattern](https://github.com/bazelbuild/bazel-central-registry/pull/4677).
+1. `source.json`'s `integrity` field is a base64 encoding of the archives `sha256` hash. If you don't know how to create this directly, the PR presubmit will fail and show the expected hash.
+1. When this PR is submitted, the release is done and available in https://bcr.bazel.build.
