Update RELEASE.adoc (#6395)

Co-authored-by: Nikolaos Bezirgiannis <bezirg@users.noreply.github.com>

RELEASE.adoc

@@ -79,7 +79,7 @@ This updates versions and version bounds, and assembles the changelogs.open a PR
 - Click `Publish release`.
 7. Open a PR in the https://github.com/IntersectMBO/cardano-haskell-packages[CHaP repository] for publishing the new version. +
 If you are making PR from your own fork then don't forget to sync your fork with the upstream first. +
-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/764. 
+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/764.
 - 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?
 It is desirable to minimize the amount of change between `rc1` and `rc2`, because it may reduce the tests and checks that need to be performed against `rc2`.
@@ -103,7 +103,12 @@ Another example is if a security audit is done on `rc1`, and the changes in `rc2
 - Click the `Run workflow` button on the right, enter the new release version and confirm
 - Ensure that the action completes successfully
 
-11. Delete unused brances and tags 
+11. Publish the updated Haddock site
+- Navigate to the https://github.com/IntersectMBO/plutus/actions/workflows/haddock-site.yml[Haddock Site Action] on GitHub
+- Click the `Run workflow` button on the right, enter the new release version 2 times, leave the checkbox Enabled, and confirm
+- Ensure that the action completes successfully
+
+12. Delete unused branches and tags
 - If it was created, delete the `release/*` branch locally and on GitHub
 - If they were created, delete any release candidate `-rc*` tags locally and on GitHub