update broken links

content/docs/deployment/helm/modules/encryption/_index.md

@@ -13,13 +13,13 @@ the rest of the deployment process is described in the correspondent [CSI driver
 
 ## Vault Server
 
-Hashicorp Vault must be [pre-configured](../vault) to support Encryption. The Vault server's IP address and port must be accessible 
+Hashicorp Vault must be [pre-configured](vault) to support Encryption. The Vault server's IP address and port must be accessible 
 from the Kubernetes cluster where the CSI driver is to be deployed.
 
 ## Rekey Controller
 
 The Encryption Rekey CRD Controller is an optional component that, if installed, allows encrypted volumes rekeying in a
-Kubernetes cluster. Please refer to [Rekey Configuration](../rekey) for the Rekey Controller installation details.
+Kubernetes cluster. Please refer to [Rekey Configuration](rekey) for the Rekey Controller installation details.
 
 ## Helm Chart Values
 
@@ -106,7 +106,7 @@ A secret with the AppRole credentials used by Encryption to authenticate to the
 
 > Set `role_id` and `secret_id` to the values provided by the Vault server administrator.
 
-> If a self-managed test Vault instance is used, generate role ID and secret ID following [these steps](../vault/#set-role-id-and-secret-id-to-the-role).
+> If a self-managed test Vault instance is used, generate role ID and secret ID following [these steps](vault/#set-role-id-and-secret-id-to-the-role).
 
 ```shell
 cat >auth.json <<EOF

content/docs/deployment/helm/modules/encryption/vault.md

@@ -41,7 +41,7 @@ Create server certificate signed by the CA:
 
 > Replace `<external IP>` with an IP address by which Encryption can reach the Vault server. 
 This may be the address of the Docker host where the Vault server will be running. 
-The same address should be used for `vault_addr` in [vault-client-conf](../deployment#configmap-vault-client-conf).
+The same address should be used for `vault_addr` in [vault-client-conf](../#configmap-vault-client-conf).
 
 ```shell
 cat > cert.ext <<EOF
@@ -224,7 +224,7 @@ vault write auth/approle/role/dea-role/role-id role_id=demo-role-id
 vault write auth/approle/role/dea-role/custom-secret-id secret_id=demo-secret-id
 ```
 
-> Secret ID has an expiration time after which it becomes invalid resulting in [authorization failure](../troubleshooting#expired-approle-secret-id).
+> Secret ID has an expiration time after which it becomes invalid resulting in [authorization failure](../../../../secure/encryption/troubleshooting#expired-approle-secret-id).
 > The expiration time for new secret IDs can be set in `secret_id_ttl` parameter when [the role is created](#create-a-role) or later on using
 > `vault write auth/approle/role/dea-role/secret-id-ttl secret_id_ttl=24h`.