Fix dead links in documentation (#5311)

Co-authored-by: Simon Dumas <simon.dumas@senscience.ai>

Author: imsdu

docs/src/main/paradox/docs/delta/api/content-negotiation.md

@@ -2,7 +2,7 @@
 
 When performing a request against Nexus Delta, clients can specify the desired format of the response they would like to receive.
 This is done through a mechanism called **Content Negotiation**. 
-Nexus Delta uses the HTTP @link:[Accept](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept){ open=new } Header in order to provide Content Negotiation capabilities.
+Nexus Delta uses the HTTP @link:[Accept](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Accept){ open=new } Header in order to provide Content Negotiation capabilities.
 
 **Example**
 

docs/src/main/paradox/docs/delta/api/id-resolution.md

@@ -71,7 +71,7 @@ The Nexus Fusion resolve page allows the user to authenticate (if they are not a
 call to the Nexus Delta `/v1/resolve/{resourceId}` with the user's authentication token.
 
 All calls to the `/v1/resolve-proxy-pass` endpoint lead to
-@link:[303 See Other responses](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/303).
+@link:[303 See Other responses](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/303).
 
 ### Example
 

docs/src/main/paradox/docs/releases/v1.11-to-v1.12-migration.md

@@ -1,9 +1,7 @@
 # v1.11 To v1.12 Migration
 
 # Schema changes
-Run the differents scripts starting with V1_12 in order:
-
-https://github.com/BlueBrain/nexus/tree/$git.branch$/delta/sourcing-psql/src/main/resources/scripts/postgres/init
+Run the different scripts starting with V1_12 in order from [the repository](https://github.com/BlueBrain/nexus/tree/$git.branch$/delta/sourcing-psql/src/main/resources/scripts/postgres/init).
 
 # Indexing in Elasticsearch and Blazegraph