Revise release notes generation steps in RELEASE.md

Updated instructions for generating release notes on GitHub.

Author: ktoso

Sources/Prometheus/RELEASE.md

@@ -31,10 +31,13 @@ git push origin "${tag}"
 
 Step 2) Make the GitHub Release and Release Notes.
 
-Release notes generation is automated and based on the enforced labelling of pull requests.
-As pull requests are merged, they are required to be tagged with `semver/*` tags (`semver/patch`, `semver/minor`, ...).
-When you navigate to the [New release](https://github.com/swift-server/swift-prometheus/releases/new) page on github and 
-select your release tag, and click **Generate release notes** release notes will automatically be generated.
+> Release notes generation is automated and based on the enforced labelling of pull requests.
+> As pull requests are merged, they are required to be tagged with `semver/*` tags (`semver/patch`, `semver/minor`, ...).
+
+Navigate to the [New release](https://github.com/swift-server/swift-prometheus/releases/new) page on github and 
+select your release tag.
+
+Click **Generate release notes** release notes will automatically be generated.
 
 Take a moment to read over the changes and make sure their assigned patch/minor/major categories are correct and match the release's assigned version.
 
@@ -47,4 +50,4 @@ Step 3) "There is no Step 3!"
 Generally this project supports three most recent minor versions of Swift.
 
 For example, at time of writing this document Swift 6.2 is the current release, so this project also supports 6.1 and 6.0.
-And this list of versions changes whenever a new minor Swift version is released.
+And this list of versions changes whenever a new minor Swift version is released.