[release] 3.0.1-A1 (#732)

[release] 3.0.1-A1

docs/build-and-release.md

@@ -22,8 +22,6 @@ GitHub Actions CI builds differ by branch:
     > - alfresco/alfresco-transform-core-aio
   - if the commit message contains the `[release]` tag, the builds will also 
   include the _Release_ stage;
-  - PR builds where the latest commit contains the `[release]` tag will execute dry runs 
-  of the release jobs (no artifacts will be published until the PR is actually merged).
 * `ATS-*` / `ACS-*` branches:
   - regular builds which include only the _Build_ and _Tests_ stages;
 
@@ -53,11 +51,8 @@ been generated by steps (2) and (3), then an empty commit should be created - e.
  
      > The location of the `[release]` tag in the commit message is irrelevant.
 
-     > If for any reason your PR contains multiple commits, the commit with the `[release]`
-     tag should be the last (newest) one. This will trigger the Release dry runs.
 5. Open a new Pull Request from the `ATS-###_release_version` branch into the original
-`master` / `SP/*` / `HF/*` branch and wait for a green build; the **Release** stage on the PR build
- will only execute a _Dry_Run_ of the release.
+`master` / `SP/*` / `HF/*` branch and wait for a green build.
 6. Once it is approved, merge the PR, preferably through the **Rebase and merge** option. If the 
 **Create a merge commit** (_Merge pull request_) or **Squash and merge** options are used, you 
 need to ensure that the _commit message_ contains the `[release]` tag (sub-string).