From d946abd8d749a56f1eb12130b729ae9a30a79ff7 Mon Sep 17 00:00:00 2001 From: Oliver Wickham Date: Tue, 18 Feb 2020 14:13:06 +0000 Subject: [PATCH] Fix incorrect link in 2.6 migration guide (#28622) --- .../src/main/paradox/project/migration-guide-2.5.x-2.6.x.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/akka-docs/src/main/paradox/project/migration-guide-2.5.x-2.6.x.md b/akka-docs/src/main/paradox/project/migration-guide-2.5.x-2.6.x.md index 941d1fa2b4..ed07987267 100644 --- a/akka-docs/src/main/paradox/project/migration-guide-2.5.x-2.6.x.md +++ b/akka-docs/src/main/paradox/project/migration-guide-2.5.x-2.6.x.md @@ -7,7 +7,7 @@ An overview of the changes in Akka 2.6 is presented in the [What's new in Akka 2 and the [release announcement](https://akka.io/blog/news/2019/11/06/akka-2.6.0-released). Akka 2.6.x is binary backwards compatible with 2.5.x with the ordinary exceptions listed in the -@ref:[Binary Compatibility Rules](../common/circuitbreaker.md). +@ref:[Binary Compatibility Rules](../common/binary-compatibility-rules.md). This means that updating an application from Akka 2.5.x to 2.6.x should be a smooth process, and that libraries built for Akka 2.5.x can also be used with Akka 2.6.x. For example Akka HTTP 10.1.10