fix: broken links

Author: CMCDragonkai

docs/reference/polykey-core/vaults.md

@@ -67,9 +67,9 @@ decrypted in memory using the Virtual File System.
 ## `VaultManager`
 
 The `VaultManager` class is responsible for handling the many vaults a polykey
-instance would have. It contains a mapping of the vault name to the
-[`Vault`](#Vault) object along with functions manage the vaults. This is what is
-exported from the `Vaults` module.
+instance would have. It contains a mapping of the vault name to the `Vault`
+object along with functions manage the vaults. This is what is exported from the
+`Vaults` module.
 
 ---
 

docs/theory/decentralized-trust-network.md

@@ -228,8 +228,8 @@ stages, however, only the final three belong to the augmentation itself:
    itself is to update Keynode and Gestalt permissions. This step links the
    Keynode and digital identity inside the user's Gestalt and updates (or
    creates) Keynode permissions in the ACL to reflect these changes (see
-   [Sharing](Gestalts-and-Digital-Identities#sharing) below for an explanation
-   of the ACL).
+   [Sharing](./gestalts-and-digital-identities.md#sharing) below for an
+   explanation of the ACL).
 3. Generating a claim on the Sigchain: A cryptolink claim between a Keynode and
    digital identity begins on the Keynode. The claim is generated by providing
    the name of both the digital identity and its provider to the Keynode, which