Fix links in documentation

documentation/docs/decentralized_identifiers/create.mdx

@@ -33,4 +33,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.

documentation/docs/tutorials/validate_university_degree.mdx

@@ -14,7 +14,7 @@ keywords:
 
 # Digitally Validate a Degree
 
-In this tutorial, you will use the [WASM binding of the IOTA Identity framework](libraries/wasm/getting_started) to digitally prove the existence and validity of a degree.
+In this tutorial, you will use the [WASM binding of the IOTA Identity framework](../libraries/wasm/getting_started) to digitally prove the existence and validity of a degree.
 
 To follow along, please clone [the tutorials repository](https://github.com/adrian-grassl/iota-identity-tutorial/) and install the npm/yarn package [@iota/identity-wasm**@dev**](https://www.npmjs.com/package/@iota/identity-wasm), as described in the [WASM binding documentation](../libraries/wasm/getting_started#install-the-library).
 
@@ -91,7 +91,7 @@ In this process, you will complete the different steps from the perspective of o
 
 The first thing you will need to do in this tutorial is to create a DID(Decentralized Identifier) Document for Alice.
 
-After this step, you will find Alice's weakhold file in [./weakhold/Alice.json](./weakhold/Alice.json).
+After this step, you will find Alice's weakhold file in `./weakhold/Alice.json`.
 
 - [createDid.js](https://github.com/adrian-grassl/iota-identity-tutorial/blob/master/createDid.js)
 
@@ -103,7 +103,7 @@ After this step, you will find Alice's weakhold file in [./weakhold/Alice.json](
 
 Once you have created the Alice's DID(Decentralized Identifier), you should do the same for the University of Oslo.
 
-After this step, you will find the University of Oslo's weakhold file in [./weakhold/UniversityofOslo.json](./weakhold/UniversityofOslo.json).
+After this step, you will find the University of Oslo's weakhold file in `./weakhold/UniversityofOslo.json`.
 
 - [createDid.js](https://github.com/adrian-grassl/iota-identity-tutorial/blob/master/createDid.js)
 
@@ -117,7 +117,7 @@ Since the university will need to verify Alice's degree, you should add a "degre
 
 The University will have to sign more than just Alice's degree, so you should generate this verification method with a set of Merkle keys. These signatures can all be proved by a single public key, while retaining the ability to revoke them separately.
 
-Note that the newly added verification method is of the *type* [MerkleKeyCollection](../decentralized_identifiers/merkle_key_collection.mdx).
+Note that the newly added verification method is of the *type* [MerkleKeyCollection](../decentralized_identifiers/merkle_key_collection.md).
 
 - [addVerificationMethod.js](https://github.com/adrian-grassl/iota-identity-tutorial/blob/master/addVerificationMethod.js)
 
@@ -293,4 +293,4 @@ The IOTA Foundation verifies Alice's and the University's signatures again by ch
 ```javascript
 let signedVpPath = './signedCredentials/signedVP.json';
 checkVerifiablePresentation(signedVpPath);
-```
+```