Fix links

Signed-off-by: Hugues de Valon <[email protected]>

Author: hug-dev

README.md

@@ -38,7 +38,7 @@ will check if your files are formatted correctly.
 
 ## Contributing
 
-Please check the [**Contribution Guidelines**](https://parallaxsecond.github.io/parsec-book/contributing.html)
+Please check the [**Contribution Guidelines**](https://parallaxsecond.github.io/parsec-book/contributing/index.html)
 to know more about the contribution process.
 
 ## License

src/contributing/adding_new_operation_how_to.md

@@ -153,11 +153,11 @@ At this point, you will now have a safe Rust interface for the PSA operation you
 
 Add the new operation to the correct
 [provider](https://github.com/parallaxsecond/parsec/tree/master/src/providers) (in this case, [Mbed
-Crypto](https://github.com/parallaxsecond/parsec/tree/master/src/providers/mbed_provider)) as a
-`psa_xxx_internal` method. The operation method should take the user inputs, arrange them in a way
+Crypto](https://github.com/parallaxsecond/parsec/tree/master/src/providers/mbed_crypto_provider)) as
+a `psa_xxx_internal` method. The operation method should take the user inputs, arrange them in a way
 that [`psa-crypto`](#psa-crypto) accepts, and provide any extra logic or storage if required (e.g.
 an output buffer). The external implementation is to be added to the provider’s
-[`mod.rs`](https://github.com/parallaxsecond/parsec/blob/master/src/providers/mbed_provider/mod.rs)
+[`mod.rs`](https://github.com/parallaxsecond/parsec/blob/master/src/providers/mbed_crypto_provider/mod.rs)
 file, which outputs a trace entry and passes the call back to the internal implementation.
 
 A default implementation is added to

src/parsec_service/README.md

@@ -20,7 +20,7 @@ They cover the following concepts:
    and running the service
 - [Installation](install_parsec_linux.md) - installing Parsec as a systemd daemon
 - [Configuration](configuration.md) - how to configure Parsec
-- [Testing](test.md) - details about the kinds of tests we employ and how to set up your environment
+- [Testing](tests) - details about the kinds of tests we employ and how to set up your environment
    in preparation for running them
 
 *Copyright 2019 Contributors to the Parsec project.*

src/parsec_service/build_run.md

@@ -18,7 +18,7 @@ one](https://github.com/parallaxsecond/parsec/blob/master/e2e_tests/provider_cfg
 The `mbed-crypto-provider` feature is going to be used as an example in this guide. This can be
 replaced by a subset of the features mentioned above, space or comma separated. If you would like to
 test the TPM or PKCS check the [related
-guides](test.md#testing-the-tpm-provider-using-the-software-tpm).
+guides](tests#testing-the-tpm-provider-using-the-software-tpm).
 
 For the `DomainSocket` listener, the socket folder needs to be created:
 
@@ -51,8 +51,8 @@ via a command-line argument:
 cargo run --features mbed-crypto-provider -- --config e2e_tests/provider_cfg/mbed-crypto/config.toml
 ```````
 
-From another terminal, it is now possible to execute the [end-to-end
-tests](test.md#end-to-end-tests) on Parsec!
+From another terminal, it is now possible to execute the [end-to-end tests](tests#end-to-end-tests)
+on Parsec!
 
 ```````
 cd e2e_tests