Fix typos

Author: eddumelendez

RELEASING.md

@@ -15,8 +15,8 @@ Testcontainers' release process is semi-automated through GitHub Actions. This d
     * For TinSalver to correctly work with keybase on WSL on Windows, you might need to disable pinentry: `keybase config set -b pinentry.disabled true`.
 7. Close the release in Sonatype. This will evaluate the release based on given Sonatype rules.
 8. After successful closing, the release button needs to be clicked and afterwards it is automatically synced to Maven Central.
-9. Handcraft and polish some of the release notes (e.g. substitute combinded dependency PRs and highlight certain features).
-10. Rename existing milestone corresponding to new release and close it. Then create a new `next` milstestone.
+9. Handcraft and polish some of the release notes (e.g. substitute combined dependency PRs and highlight certain features).
+10. Rename existing milestone corresponding to new release and close it. Then create a new `next` milestone.
 11. When available through Maven Central, poke [Richard North](https://github.com/rnorth) to announce the release on Twitter!
 12. Merge automated version update PRs in order to update the reference version in `mkdocs.yml` and `gradle.properties`.
 
@@ -25,4 +25,4 @@ Testcontainers' release process is semi-automated through GitHub Actions. This d
 * The process is done with GitHub Actions, TinSalver and Sonatype.
 * Sonatype will automatically promote the staging release to Maven Central.
 * Keybase needs to be installed on the developer machine.
-* GPG key of signing developer needs to be uplodaed to the [Ubuntu keyserver](https://keyserver.ubuntu.com/) (or other server supported by Sonatype).
+* GPG key of signing developer needs to be uploaded to the [Ubuntu keyserver](https://keyserver.ubuntu.com/) (or other server supported by Sonatype).