chore(docs): fix link in info box (#73)

api-guidelines/global/compatibility/compatible-changes/rules/must-not-break-backward-compatibility.md

@@ -17,6 +17,7 @@ We strongly encourage using compatible API extensions and discourage versioning.
 The guidelines for API providers ([SHOULD prefer compatible extensions](./should-prefer-compatible-extensions.md)) and consumers ([MUST prepare consumers to accept compatible API extensions](./must-prepare-consumers-to-accept-compatible-api-extensions.md)) enable us (having Postel’s Law in mind) to make compatible changes without versioning.
 
 ::: info Info
-There is a difference between incompatible and breaking changes. Breaking changes break existing clients, when deployed into operation.
-However, in specific controlled situations, it is possible to deploy incompatible changes in a non-breaking way if no consuming client is using or plans to use the affected API aspects (see also [Deprecation](../../README.md#deprecation-of-obsolete-api-versions-and-components)).
-:::
+There is a difference between incompatible and breaking changes.
+Breaking changes break existing clients, when deployed into operation.
+However, in specific controlled situations, it is possible to deploy incompatible changes in a non-breaking way if no consuming client is using or plans to use the affected API aspects (see also [Deprecation](/guidelines/rest-guidelines/compatibility#deprecation-of-obsolete-api-versions-and-components)).
+:::