Update README.md

Author: damianmalczewski

README.md

@@ -1,7 +1,7 @@
 # Problem4J Core
 
 [![Build Status](https://github.com/problem4j/problem4j-core/actions/workflows/gradle-build.yml/badge.svg)](https://github.com/problem4j/problem4j-core/actions/workflows/gradle-build.yml)
-[![Sonatype](https://img.shields.io/maven-central/v/io.github.problem4j/problem4j-core)](https://central.sonatype.com/artifact/io.github.problem4j/problem4j-core)
+[![Sonatype](https://img.shields.io/maven-central/v/io.github.problem4j/problem4j-core)][maven-central]
 [![License](https://img.shields.io/github/license/problem4j/problem4j-core)](https://github.com/problem4j/problem4j-core/blob/main/LICENSE)
 
 This library provides a minimal, framework-agnostic Java model of the [RFC 7807][rfc7807] "Problem Details" object, with
@@ -108,20 +108,22 @@ module org.example.project {
 Add library as dependency to Maven or Gradle. See the actual versions on [Maven Central][maven-central]. **Java 8** or
 higher is required to use this library.
 
+[![Sonatype](https://img.shields.io/maven-central/v/io.github.problem4j/problem4j-core)][maven-central]
+
 1. Maven:
    ```xml
    <dependencies>
        <dependency>
            <groupId>io.github.problem4j</groupId>
            <artifactId>problem4j-core</artifactId>
-           <version>1.4.2</version>
+           <version>{version}</version>
        </dependency>
    </dependencies>
    ```
 2. Gradle (Groovy or Kotlin DSL):
    ```groovy
    dependencies {
-       implementation("io.github.problem4j:problem4j-core:1.4.2")
+       implementation("io.github.problem4j:problem4j-core:{version}")
    }
     ```
 

RELEASING.md

@@ -2,14 +2,13 @@
 
 1. Update `CHANGELOG.md` - change `[Unreleased]` to `[X.Y.Z] - YYYY-MM-DD` and add a new `[Unreleased]` section on top.
 2. Update `version` property in `gradle.properties` to the new version.
-3. Update versions of dependency samples in `README.md`.
-4. Commit the changes from (1) and (2) with a message `"Release X.Y.Z"` and push to GitHub.
-5. Create an annotated git tag named `vX.Y.Z` with the message `"Release X.Y.Z"` and push it to GitHub. This will
+3. Commit the changes from (1) and (2) with a message `"Release X.Y.Z"` and push to GitHub.
+4. Create an annotated git tag named `vX.Y.Z` with the message `"Release X.Y.Z"` and push it to GitHub. This will
    trigger the release workflow, which will build and publish the artifacts to Sonatype repository. You can use the
    [`./tools/tagrelease`](./tools/tagrelease) script to ensure the tag is correctly formatted and prevent mistakes.
-6. Update `version` property in `gradle.properties` to the next snapshot version, for example `1.4.1-SNAPSHOT`.
-7. Commit the change from (5) with a message `"Update snapshot version"` and push to GitHub.
-8. If the release was made on a maintenance branch, make sure to `merge` or `cherry-pick` the `CHANGELOG.md` entry to 
+5. Update `version` property in `gradle.properties` to the next snapshot version, for example `1.4.1-SNAPSHOT`.
+6. Commit the change from (5) with a message `"Update snapshot version"` and push to GitHub.
+7. If the release was made on a maintenance branch, make sure to `merge` or `cherry-pick` the `CHANGELOG.md` entry to 
    the `main` branch as well.
 
 ## Maven Central