Update docs for publishing from a support branch

docs/releasing/publishing-from-a-support-branch.md

@@ -112,11 +112,11 @@ Note: Before you go on annual leave, tell the delivery manager who will be looki
 3. Run `npm run publish-release`, which will prompt you to check whether the NPM tag looks as expected.
 
   If you're following these instructions, it's likely that you're publishing an out-of-order release which should
-  *not* be tagged as the 'latest' release on NPM. In this scenario,
+  *not* be tagged as the 'latest' release on NPM. In this scenario, the tag should take the format `latest-[major-version-number`, for example: `latest-4`.
 
   Enter 'y' to continue. If you think the tag should be different, enter `N` to have the option to set your own NPM tag.
 
-Run `npm run publish-release`, which will prompt you to either continue or cancel. Enter `y` to continue.
+4. You will now be prompted to continue or cancel the release. Check the details and enter `y` to continue.
 
 4. View the created tag in the [GitHub interface](https://github.com/alphagov/govuk-frontend/releases) as follows:
 
@@ -138,7 +138,7 @@ Run `npm run publish-release`, which will prompt you to either continue or cance
     - move any relevant issues from the 'Ready to Release' column to 'Done'
     - close any associated milestones
 
-## Update the `main` branch
+## Update the `main` branch (optional)
 
 1. Check out the `main` branch and pull the latest changes.