Clarify the tag should be created in the MAJOR.MINOR.x branch

Author: bluetech

RELEASING.rst

@@ -10,7 +10,7 @@ taking a lot of time to make a new one.
     pytest releases must be prepared on **Linux** because the docs and examples expect
     to be executed on that platform.
 
-The release a version ``MAJOR.MINOR.PATCH``, follow these steps:
+To release a version ``MAJOR.MINOR.PATCH``, follow these steps:
 
 #. For major and minor releases, create a new branch ``MAJOR.MINOR.x`` from the
    latest ``master`` and push it to the ``pytest-dev/pytest`` repo.
@@ -27,7 +27,8 @@ The release a version ``MAJOR.MINOR.PATCH``, follow these steps:
 
 #. Open a PR for the ``release-MAJOR.MINOR.PATCH`` branch targeting ``MAJOR.MINOR.x``.
 
-#. After all tests pass and the PR has been approved, publish to PyPI by pushing the tag::
+#. After all tests pass and the PR has been approved, tag the release commit
+   in the ``MAJOR.MINOR.x`` branch and push it. This will publish to PyPI::
 
      git tag MAJOR.MINOR.PATCH
      git push [email protected]:pytest-dev/pytest.git MAJOR.MINOR.PATCH