Update BREAKING_CHANGES.md

Co-authored-by: Asbjørn Ulsberg <[email protected]>

Author: HHobeck

BREAKING_CHANGES.md

@@ -5,7 +5,7 @@
 *   The current branch (child) inherits its configuration from the source (parent) branch if the `increment` strategy is set to `Inherit`. This makes branch configuration recursive, simpler, more intuitive, more flexible, and more robust.
 *   Instead of having a single effective configuration, we now have one effective configuration per branch where the increment strategy is not set to `inherit`.
 *   The new implementation of the branch configuration inheritance affects per default only the pull-requests, hotfix and feature branches. In this case the next version will be generated like the child branch is not existing and the commits have been made on the source branch.
-    *   The following example illustrates this behavior. On the feature branch the semantic version 1.1.0-just-a-test.1+2 will be generated instead of version 1.0.0-just-a-test.1+3:
+    *   The following example illustrates this behavior. On the feature branch the semantic version `1.1.0-just-a-test.1+2` will now be generated instead of version `1.0.0-just-a-test.1+3` previously:
 	```
     * 1f1cfb4 52 minutes ago  (HEAD -> feature/just-a-test)
 	* 1f9654d 54 minutes ago  (release/1.1.0)