diff --git a/docs/pro.md b/docs/pro.md
index 762fbaa..e335389 100644
--- a/docs/pro.md
+++ b/docs/pro.md
@@ -26,7 +26,7 @@ incoming messages, you might want to fallback to the _actor-per-connection_ mode
 
 ## More features
 
-- [Adaptive RPC concurrency](anycable-go/configuration.md#adaptive-concurrency)
+- [Adaptive RPC concurrency](anycable-go/rpc.md#adaptive-concurrency)
 - [Multi-node streams history](anycable-go/reliable_streams.md#redis)
 - [Slow drain mode for disconnecting clients on shutdown](anycable-go/configuration.md#slow-drain-mode)
 - [Binary messaging formats](anycable-go/binary_formats.md)
diff --git a/docs/release_notes.md b/docs/release_notes.md
index 197fe07..7c1af65 100644
--- a/docs/release_notes.md
+++ b/docs/release_notes.md
@@ -151,7 +151,7 @@ This page contains combined release notes for major and minor releases of all An
 
   Users of AnyCable had to scale and balance resources on two sides: RPC and AnyCable-Go. Now AnyCable-Go can adjust its concurrency limit automatically to minimize errors (`ResourcesExhausted`) and maximize throughput (thus, reduce the backlog size) if possible. This means, you only have to scale the Rails application, and AnyCable-Go will balance itself alongside automatically.
 
-  See [documentation](./anycable-go/configuration.md#adaptive-concurrency).
+  See [documentation](./anycable-go/rpc.md#adaptive-concurrency).
 
 #### AnyCable-Go