Kwxm/release/update instructions (#5748)

* Update release instructions

* Update release instructions

* Update release instructions

* Update release instructions

* Update release instructions

RELEASE.adoc

@@ -71,10 +71,12 @@ This updates versions and version bounds, and assembles the changelogs.open a PR
 - `<packages>` should normally be empty, which will prepare the default packages, or can be an explicit list of packages to prepare.
 4. Review the changelogs and edit manually if needed.
 5. Open a PR for updating the cabal files and the changelog files. Example: https://github.com/IntersectMBO/plutus/pull/5452.
-6. Once the PR is merged, 'Draft a new Release' with name `x.y.z.0` using https://github.com/IntersectMBO/plutus/releases/new[Github's release interface]:
+6. Once the PR is merged, 'Draft a new Release' with name `x.y.z.0` using https://github.com/IntersectMBO/plutus/releases/new[Github's release interface] (this can also be found under `Tags`/`Releases` on the main `plutus` page):
 - Choose as git tag `x.y.z.0`
 - Choose as target the git commit hash which points to the release commit
+- Click `Generate release notes` to automatically fill in the details of what's changed
 - Create and attach pir&uplc executables to the release by running the following commands inside the repository where its HEAD is at the release commit:
+- 
 +
 [source,bash]
 -------------
@@ -84,6 +86,7 @@ cp ./result/bin/pir ./pir-x86_64-linux-ghc96
 nix build .#hydraJobs.x86_64-linux.musl64.ghc96.uplc
 cp ./result/bin/uplc ./uplc-x86_64-linux-ghc96
 -------------
+- Click `Publish release`.
 7. Open a PR in the https://github.com/IntersectMBO/cardano-haskell-packages[CHaP repository] for publishing the new version. Run `./scripts/add-from-github.sh "https://github.com/IntersectMBO/plutus" COMMIT-SHA LIST-OF-UPDATED-PACKAGES` (see https://github.com/IntersectMBO/cardano-haskell-packages#-from-github[the README on CHaP]). Example: https://github.com/IntersectMBO/cardano-haskell-packages/pull/394.
 - If issues are found, create a release branch `release/x.y.z`, fix the issues on master, backport the fixes to `release/x.y.z`, tag `x.y.z.0-rc2`, and go to step 4.
 - Why not just fix the issues on master and tag `x.y.z.0-rc2` from master?