Apply review comments

Author: asodja

RELEASING.md

@@ -15,11 +15,11 @@ These are the steps to release Gradle profiler.
 * The [Publish to SDKman](https://builds.gradle.org/buildConfiguration/GradleProfiler_GradleProfilerPublishToSdkMan?branch=%3Cdefault%3E) should trigger automatically after the publishing job finishes. Though it may fail, since the artifacts are not yet on Maven Central. The build will retry the SDKMan publishing after half an hour. If it still doesn't work, you can trigger the build manually. 
 * All done!
 
-### Releasing Snapshot Versions
+### Releasing Pre-release Versions
 
-Releasing master snapshot versions is also supported.
+Releasing pre-release versions from the master branch is also supported.
 These versions are normally used for dogfooding in the [gradle/gradle](https://github.com/gradle/gradle) build.
-We use `-alpha` suffix for these versions, e.g. `0.20.0-alpha01`.
+We use `-alpha-<number>` suffix for these versions, e.g. `0.21.0-alpha-1`.
 
 Process is the same as releasing the final versions, except that you should not publish the [release draft](https://github.com/gradle/gradle-profiler/releases).
 Also, the build will automatically detect a snapshot version if it contains `snapshot` or `alpha` and will skip publishing to SDKMan.