Add a couple of clarifications to the release process

README.md

@@ -92,8 +92,8 @@ To avoid having to unzip the extension in the corresponding directory every time
 
 - Make sure you are on the `master` branch and it is up to date (`git pull`)
 - Open `pom.xml` and set the version to the desired version number, such as `<version>0.1.0</version>`
-- Commit and push those changes
-- Add a corresponding git tag, with `git tag -a v0.1.0 -m "Version 0.1.0"` (when working from GitHub Desktop, you can follow [this process](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags) and manually add the `v0.1.0` and `Version 0.1.0` tags)
+- Commit and push those changes to master
+- Add a corresponding git tag, with `git tag -a v0.1.0 -m "Version 0.1.0"` (when working from GitHub Desktop, you can follow [this process](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags) and manually add the `v0.1.0` tag the description `Version 0.1.0`)
 - Push the tag to GitHub: `git push --tags` (in GitHub Desktop, just push again)
 - Create the zip file for the release: `mvn package`
 - Create a new release on GitHub at https://github.com/OpenRefine/CommonsExtension/releases/new, providing a release title (such as "Commons extension 0.1.0") and a description of the features in this release. Upload the zip file you generated at the previous step as an attachment (it can be found in the `target` subfolder of your local copy of the repository).