release docs: clarify role of releases.json

site/content/en/docs/contrib/releasing/binaries.md

@@ -76,11 +76,11 @@ After job completion, click "Console Output" to verify that the release complete
 
 **Note: If you are releasing a beta, you are done when you get here.**
 
-## Check releases.json
+## Merge the releases.json change
 
-This file is used for auto-update notifications, but is not active until releases.json is copied to GCS.
+The release script updates https://storage.googleapis.com/minikube/releases.json - which is used by the minikube binary to check for updates, and is live immediately.
 
-minikube-bot will send out a PR to update the release checksums at the top of `deploy/minikube/releases.json`. You should merge this PR.
+minikube-bot will also send out a PR to merge this into the tree. Please merge this PR to keep GCS and Github in sync.
 
 ## Package managers which include minikube