diff --git a/docs/Activation-Status.md b/docs/Activation-Status.md
index f133a3ef..d4d03955 100644
--- a/docs/Activation-Status.md
+++ b/docs/Activation-Status.md
@@ -1,6 +1,6 @@
 # Activation Status
 
-PowerAuth Client may need to check for an activation status, so that it can determine if it should display UI for non-activated state (registration form), blocked state (how to unblock tutorial) or active state (login screen). To facilitate this use-case, PowerAuth Standard RESTful API publishes a [/pa/v3/activation/status](./Standard-RESTful-API#post-pav3activationstatus) endpoint.
+PowerAuth Client may need to check for an activation status, so that it can determine if it should display UI for non-activated state (registration form), blocked state (how to unblock tutorial) or active state (login screen). To facilitate this use-case, PowerAuth Standard RESTful API publishes a [/pa/v3/activation/status](./Standard-RESTful-API#activation-status) endpoint.
 
 Checking for an activation status is simple. Client needs to prepare a HTTP request with an activation ID and random `STATUS_CHALLENGE`. Server processes the request and sends back the response with activation status blob and random `STATUS_NONCE`. Activation status blob is an encrypted binary blob that encodes the activation status. Key `KEY_TRANSPORT` and `STATUS_IV` is used to encrypt the activation blob.
 
diff --git a/docs/Activation-via-Recovery-Code.md b/docs/Activation-via-Recovery-Code.md
index 030a3c3b..bb67a19c 100644
--- a/docs/Activation-via-Recovery-Code.md
+++ b/docs/Activation-via-Recovery-Code.md
@@ -111,7 +111,7 @@ After this step, PowerAuth Client performs Key Exchange with the PowerAuth Serve
 
 ### Key Exchange
 
-Following diagram shows how public keys are exchanged between PowerAuth Client and PowerAuth Server, and how master shared secret and PowerAuth Standard Keys are derived. The process is very similar to [Key Exchange](Activation.md#key-exchange) from a regular [Activation](Activation.md).
+Following diagram shows how public keys are exchanged between PowerAuth Client and PowerAuth Server, and how master shared secret and PowerAuth Standard Keys are derived. The process is very similar to [Key Derivation](Activation.md#key-derivation) from a regular [Activation](Activation.md).
 
 ![Activation via Recovery Code](resources/images/sequence_activation_recovery.png)
 
diff --git a/docs/Activation.md b/docs/Activation.md
index 33450de1..873ba594 100644
--- a/docs/Activation.md
+++ b/docs/Activation.md
@@ -45,7 +45,7 @@ The first layer of encryption protects the data transfer between the mobile app
 
 Detailed documentation of [End-to-End Encryption](./End-To-End-Encryption.md) is available in a dedicated chapter.
 
-A good place to review the exact request and response payload structure is in the [PowerAuth Standard RESTful API documentation](./Standard-RESTful-API.md#post-pav3activationcreate).
+A good place to review the exact request and response payload structure is in the [PowerAuth Standard RESTful API documentation](./Standard-RESTful-API.md#initiate-activation).
 
 ## Key Derivation