Update README.md (RasaHQ#10387)

* clarify micro releases don't need to update sdk
* clarify which PR number to add to changelog when issue does not exist

README.md

@@ -351,7 +351,7 @@ Releasing a new version is quite simple, as the packages are build and distribut
 
 *Release steps*:
 1. Make sure all dependencies are up to date (**especially Rasa SDK**)
-    - For Rasa SDK that means first creating a [new Rasa SDK release](https://github.com/RasaHQ/rasa-sdk#steps-to-release-a-new-version) (make sure the version numbers between the new Rasa and Rasa SDK releases match)
+    - For Rasa SDK, except in the case of a micro release, that means first creating a [new Rasa SDK release](https://github.com/RasaHQ/rasa-sdk#steps-to-release-a-new-version) (make sure the version numbers between the new Rasa and Rasa SDK releases match)
     - Once the tag with the new Rasa SDK release is pushed and the package appears on [pypi](https://pypi.org/project/rasa-sdk/), the dependency in the rasa repository can be resolved (see below).
 2. In case of a minor release, create a new branch that corresponds to the new release, e.g. 
    ```bash

changelog/README.md

@@ -23,9 +23,9 @@ Each file should be named like `<ISSUE>.<TYPE>.md`, where
 
 So for example: `123.feature.md`, `456.bugfix.md`.
 
-If your PR fixes an issue, use that number here. If there is no issue,
-then after you submit the PR and get the PR number you can add a
-changelog using that instead.
+If your change fixes an issue, use the issue number here. If there is no issue,
+then after you submit the PR with your changes and get the PR number, you can add a
+changelog using that PR number instead.
 
 If you are not sure what issue type to use, don't hesitate to ask in your PR.