Fix dead links

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

Author: hug-dev

src/README.md

@@ -7,7 +7,7 @@ Find here all the technical documentation of Parsec, alongside user and develope
 
 Go straight to the [overview](overview.md) to learn more about the project! Then, depending on what
 you want to know, you can go to the [users](parsec_users.md), [client
-developpers](parsec_client/README.d), [service developpers](parsec_service/README.md) or
+developpers](parsec_client/README.md), [service developpers](parsec_service/README.md) or
 [security](parsec_security/README.md) sections.
 
 # Disclaimer

src/contributing/adding_new_operation_how_to.md

@@ -15,8 +15,8 @@ Create the specification page for the Parsec Book, under
 also be found in the menu on the left of all pages). Include operation details such as parameters,
 results, errors specific to the operation, a description, and a link to the
 [protobuf](#parsec-operations) contract (which will be created further on). Also update all API
-tables on the [Service API](../service_api_coverage.md) and [Client API](../clients_api_coverage.md)
-pages to reflect the new addition (create any API tables if they are missing).
+tables on the [Parsec Operations Coverage](../parsec_client/operations/service_api_coverage.md) page
+to reflect the new addition (create any API tables if they are missing).
 
 The opcode used should be the next available one. To find this, go to
 [`parsec-interface-rs/src/requests/mod.rs`](https://github.com/parallaxsecond/parsec-interface-rs/blob/master/src/operations/mod.rs)

src/parsec_client/operations/psa_algorithm.md

@@ -7,8 +7,8 @@ Some of the algorithms defined here are deprecated and should not be used withou
 is at the discretion of the system administrator whether those algorithms are permitted or not.
 
 **Notice:** not all possible algorithms are currently supported by Parsec. Please see the [API
-coverage](../../service_api_coverage.md) for an overview of what Parsec currently supports. Some of
-the attributes might not be supported by some providers as it is not in their interface.
+coverage](service_api_coverage.md) for an overview of what Parsec currently supports. Some of the
+attributes might not be supported by some providers as it is not in their interface.
 
 ## Algorithm type
 

src/parsec_client/operations/psa_key_attributes.md

@@ -6,9 +6,9 @@ to do with that key.
 Some of the algorithms defined here are deprecated and should not be used without a valid reason. It
 is at the discretion of the system administrator whether those algorithms are permitted or not.
 
-**Notice:** not all possible attributes are currently supported by Parsec. Please see the [API
-coverage](../../service_api_coverage.md) for an overview of what Parsec currently supports. Some of
-the attributes might not be supported by some providers as it is not in their interface.
+**Notice:** not all possible attributes are currently supported by Parsec. Please see the
+[Operations Coverage](service_api_coverage.md) for an overview of what Parsec currently supports.
+Some of the attributes might not be supported by some providers as it is not in their interface.
 
 ## KeyAttributes type
 

src/parsec_security/parsec_threat_model/threat_model.md

@@ -325,7 +325,7 @@ cleared.
 ## Operational mitigations
 
 Most of these operational mitigations are implemented when following the [Recommendations on a
-Secure Parsec Deployment guide](secure_deployment.md).
+Secure Parsec Deployment guide](../secure_deployment.md).
 
 | ID   | Justification                                                                                                                                                      | Details                                                                                                                                                  |
 |------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|

src/parsec_security/secure_deployment.md

@@ -3,7 +3,7 @@
 The following recommendations should be applied in order for Parsec to respect some of the
 operational mitigations. These recommendations have been thought of for a Linux system and should be
 modified/ported for other operating systems. The linked [operational
-mitigations](parsec_thread_model/threat_model.md#operational-mitigations) are noted with `O-n`.
+mitigations](parsec_threat_model/threat_model.md#operational-mitigations) are noted with `O-n`.
 
 - The service must be running as the `parsec` user (O-0).
 - Key mappings must only be read/write by the `parsec` user (O-3).

src/parsec_service/install_parsec_linux.md

@@ -3,9 +3,9 @@
 Parsec can be built and installed as a Linux daemon using systemd. The daemon is a systemd user
 daemon run by the `parsec` user. Some manual steps are needed to make sure that permissions are set
 up correctly so that Parsec is installed respecting the operational mitigations of our [threat
-model](../threat_model/threat_model.md). Similarly to the threat model, this guide proposes
-different alternatives in case an Identity Provider is available or not. The role and description of
-an Identity Provider in Parsec is described in the [System
+model](../parsec_security/parsec_threat_model/threat_model.md). Similarly to the threat model, this
+guide proposes different alternatives in case an Identity Provider is available or not. The role and
+description of an Identity Provider in Parsec is described in the [System
 Architecture](https://parallaxsecond.github.io/parsec-book/parsec_service/system_architecture.html)
 page. Currently, Parsec does not support integration with any Identity Provider. To securely install
 Parsec, please follow the steps of deployment **without an Identity Provider**.