iotaledger · eike-hass · Jun 28, 2022 · Jun 27, 2022 · Jun 27, 2022
diff --git a/documentation/docs/concepts/decentralized_identifiers/create.mdx b/documentation/docs/concepts/decentralized_identifiers/create.mdx
@@ -38,4 +38,4 @@ Next, the identity is created and published to the IOTA Tangle. This operation w
 
 ### Identity Generation Process
 
-The generation of an identity starts with a randomly generated asymmetric key pair. This can be generated by the IOTA Identity framework or can be provided as a parameter during the creation process. The public key is hashed using the `Blake2b-256` algorithm. This hash becomes the DID, creating a permanent and provable link between the initial keypair and the DID. The public key is then embedded into the initial DID Document and is used for verifying signatures created with the corresponding private key. This process can be observed and manipulated in depth by using the low-level API available for the IOTA Identity framework. These low-level APIs are available in [Rust](../libraries/rust/api_reference) and [WASM](../libraries/wasm/api_reference) but are only recommended for complex use cases that require maximum flexibility in the framework.
+The generation of an identity starts with a randomly generated asymmetric key pair. This can be generated by the IOTA Identity framework or can be provided as a parameter during the creation process. The public key is hashed using the `Blake2b-256` algorithm. This hash becomes the DID, creating a permanent and provable link between the initial keypair and the DID. The public key is then embedded into the initial DID Document and is used for verifying signatures created with the corresponding private key. This process can be observed and manipulated in depth by using the low-level API available for the IOTA Identity framework. These low-level APIs are available in [Rust](../../libraries/rust/api_reference) and [WASM](../../libraries/wasm/api_reference) but are only recommended for complex use cases that require maximum flexibility in the framework.
diff --git a/documentation/docs/concepts/decentralized_identifiers/resolve.mdx b/documentation/docs/concepts/decentralized_identifiers/resolve.mdx
@@ -104,7 +104,7 @@ async function buildAndResolve(client, did) {
 </TabItem>
 </Tabs>
 
-In the example above the resolver will automatically try to resolve the DID from the network specified in the `did` (See [DID Format](./../specs/did/iota_did_method_spec#did-format)).
+In the example above the resolver will automatically try to resolve the DID from the network specified in the `did` (See [DID Format](../../specs/did/iota_did_method_spec#did-format)).
 If the resolver was not built with a client configured for the given network name then an error will be thrown. Note that the `ResolverBuilder` can configure the `Resolver` to use
 multiple networks as long as they have distinct valid names (max six characters).
 

diff --git a/documentation/docs/getting_started/create_and_publish.mdx b/documentation/docs/getting_started/create_and_publish.mdx
@@ -13,7 +13,7 @@ keywords:
 import CodeSnippet from '../../src/components/CodeSnippetComponent'
 import createDidRustExample from  '!!raw-loader!../../../examples/account/create_did.rs';
 
-If you want to benefit from Self-Sovereign Identity, you need to create a [Decentralized Identity](../decentralized_identifiers/overview). This identity consists of many parts that have different functions. This page will cover the basics about identity creation and publishing to the Tangle.
+If you want to benefit from Self-Sovereign Identity, you need to create a [Decentralized Identity](../concepts/decentralized_identifiers/overview). This identity consists of many parts that have different functions. This page will cover the basics about identity creation and publishing to the Tangle.
 
 ## Identity Generation Process
 
@@ -36,7 +36,7 @@ Select your programming language of choice and press the green play button to ex
     rustGithubLink = "https://github.com/iotaledger/identity.rs/blob/support/v0.6/examples/account/create_did.rs"
 />
 
-The first step in this example is the creation of an account. The account is a stateful object that manages one or more identities. The account provides an interface to execute high-level operations on identities, such as [creating](../decentralized_identifiers/create) and [updating](../decentralized_identifiers/update)) them.
+The first step in this example is the creation of an account. The account is a stateful object that manages one or more identities. The account provides an interface to execute high-level operations on identities, such as [creating](../concepts/decentralized_identifiers/create) and [updating](../concepts/decentralized_identifiers/update)) them.
 
 Next, the identity is created and published to the IOTA Tangle. This operation will:
 

diff --git a/documentation/docs/getting_started/overview.md b/documentation/docs/getting_started/overview.md
@@ -12,9 +12,9 @@ keywords:
 
 # Overview
 
-Using the [standards proposed by W3C](https://www.w3.org/TR/did-core/), this section explains the IOTA Identity implementation. You can use this implementation to create a new digital identity for anyone or anything at any time. To do so, you must first generate a [Decentralized Identifier (DID)](../decentralized_identifiers/overview) that will serve as a reference to the [DID Document](../decentralized_identifiers/overview#did-documents). The DID Document contains public keys and other mechanisms to enable the subject to prove their association with the DID.
+Using the [standards proposed by W3C](https://www.w3.org/TR/did-core/), this section explains the IOTA Identity implementation. You can use this implementation to create a new digital identity for anyone or anything at any time. To do so, you must first generate a [Decentralized Identifier (DID)](../concepts/decentralized_identifiers/overview) that will serve as a reference to the [DID Document](../concepts/decentralized_identifiers/overview#did-documents). The DID Document contains public keys and other mechanisms to enable the subject to prove their association with the DID.
 
-However, you cannot tell much about the subject from a DID. You need to combine the DID with [Verifiable Credentials](../verifiable_credentials/overview). Verifiable Credentials are statements about the creator of the DID. They can be shared and verified online in a "Bring Your Own Identity" (BYOI) manner, and the DID creator remains in complete control of the process.
+However, you cannot tell much about the subject from a DID. You need to combine the DID with [Verifiable Credentials](../concepts/verifiable_credentials/overview). Verifiable Credentials are statements about the creator of the DID. They can be shared and verified online in a "Bring Your Own Identity" (BYOI) manner, and the DID creator remains in complete control of the process.
 
 You can use this framework in processes such as:
 
@@ -36,4 +36,4 @@ The IOTA Identity framework is developed in the Rust programming language. We al
 
 The following applications are currently utilizing the IOTA Identity framework:
 
-- [Selv app](https://selv.iota.org/)
+- [Selv app](https://selv.iota.org/)