Merge pull request #659 from /issues/646-fix-doc-links

Fix invalid links in the documentation
wultra · Oct 7, 2024 · cbd42df · cbd42df
2 parents 83de379 + 6cdf6a9
commit cbd42df
Show file tree

Hide file tree

Showing 6 changed files with 7 additions and 7 deletions.
diff --git a/docs/Activation-Code.md b/docs/Activation-Code.md
@@ -7,7 +7,7 @@ The PowerAuth protocol 3, defines a new version of activation code, where OTP<su
 - 96 out of possible 100 bits are used (80 random bits + 16 bits for CRC).
 
 > Notes:
-> 1. PowerAuth protocol V2 defines OTP as a part of activation code. It's completely unrelated to an OTP described in chapter [Advanced Activation Flows](Advanced-Activation-Flows).
+> 1. PowerAuth protocol V2 defines OTP as a part of activation code. It's completely unrelated to an OTP described in chapter [Advanced Activation Flows](./Advanced-Activation-Flows.md).
 
 ## Code Construction
 

diff --git a/docs/Activation-via-Activation-Code.md b/docs/Activation-via-Activation-Code.md
@@ -143,5 +143,5 @@ Note that the activation commit step can be skipped in case activation is commit
 - [Activation via Custom Credentials](./Activation-via-Custom-Credentials.md)
 - [Checking Activation Status](./Activation-Status.md)
 - [Key Derivation](./Key-derivation.md)
-- [Advanced Activation Flows](Advanced-Activation-Flows)
+- [Advanced Activation Flows](./Advanced-Activation-Flows.md)
 
diff --git a/docs/Activation-via-Custom-Credentials.md b/docs/Activation-via-Custom-Credentials.md
@@ -72,4 +72,4 @@ However, if the particular use case requires different handling, the enrollment
 - [Activation via Recovery Code](./Activation-via-Recovery-Code.md)
 - [Checking Activation Status](./Activation-Status.md)
 - [Key Derivation](./Key-derivation.md)
-- [Advanced Activation Flows](Advanced-Activation-Flows)
+- [Advanced Activation Flows](./Advanced-Activation-Flows.md)
diff --git a/docs/Activation-via-Recovery-Code.md b/docs/Activation-via-Recovery-Code.md
@@ -54,7 +54,7 @@ In the second scenario, the mobile application acts as a replacement for a typic
 
 For all cases, we recommend you to implement the following countermeasures:
 
-- Confirm the recovery activation with an OTP as described in chapter [Advanced Activation Flows](Advanced-Activation-Flows).
+- Confirm the recovery activation with an OTP as described in chapter [Advanced Activation Flows](./Advanced-Activation-Flows.md).
 - Your application should receive a push notification once the activation is recovered on another device.
 - You should also notify the user via other digital channel, like SMS or e-mail.
 - You should adequately inform the user about how sensitive Recovery Code and PUK are.
@@ -248,4 +248,4 @@ The format of Recovery PUK is very simple:
 - [Activation via Custom Credentials](./Activation-via-Custom-Credentials.md)
 - [Checking Activation Status](./Activation-Status.md)
 - [Key Derivation](./Key-derivation.md)
-- [Advanced Activation Flows](Advanced-Activation-Flows)
+- [Advanced Activation Flows](./Advanced-Activation-Flows.md)
diff --git a/docs/Activation.md b/docs/Activation.md
@@ -82,4 +82,4 @@ The following diagram shows transitions between activation states:
 - [Activation via Custom Credentials](./Activation-via-Custom-Credentials.md)
 - [Checking Activation Status](./Activation-Status.md)
 - [Key Derivation](./Key-derivation.md)
-- [Advanced Activation Flows](Advanced-Activation-Flows)
+- [Advanced Activation Flows](./Advanced-Activation-Flows.md)
diff --git a/docs/Advanced-Activation-Flows.md b/docs/Advanced-Activation-Flows.md
@@ -1,4 +1,4 @@
-# [Advanced Activation Flows]
+# Advanced Activation Flows
 
 <!-- begin box info -->
 This part of the documentation describes in detail advanced customizations of the activation process: how the commit phase can be changed as well as usage of additional activation OTP. So, before you start, you should be familiar with actors and processes defined for the [regular activation](Activation.md).