diff --git a/docs/dev/release-new-runtime.md b/docs/dev/release-new-runtime.md
index c272c48510607bf6b4fe01043ee121d2fe1e193e..8f919999900ffaa08b644ff16758ce8cf62798e5 100644
--- a/docs/dev/release-new-runtime.md
+++ b/docs/dev/release-new-runtime.md
@@ -4,18 +4,20 @@
 
 > The following instructions have been described in french at: [Créer une release](https://forum.duniter.org/t/industrialiser-le-demarrage-dune-nouvelle-gx/11535/41).
 
+> Newer instructions are available in french at: [MR !273](https://git.duniter.org/nodes/rust/duniter-v2s/-/merge_requests/273/)
+
 ## Process
 
 Example for `runtime-800`.
 
 ### New release with new Runtime
 
-* create a `release/runtime-800` branch locally
-* update the values:
-  * update spec version (in `runtime/<currency>/src/lib.rs`)
-  * eventually update `gdev.yml` (smiths, tech. committee, ...)
-* push the `release/runtime-800` branch
-  * in the CI/CD, wait for `Create release` button to be available and click on it (see above screenshot)
+- create a `release/runtime-800` branch locally
+- update the values:
+  - update spec version (in `runtime/<currency>/src/lib.rs`)
+  - eventually update `gdev.yml` (smiths, tech. committee, ...)
+- push the `release/runtime-800` branch
+  - in the CI/CD, wait for `Create release` button to be available and click on it (see above screenshot)
 
 The Runtime is now available on the release page [runtime-800](https://git.duniter.org/nodes/rust/duniter-v2s/-/releases/runtime-800).
 
@@ -29,25 +31,25 @@ You may want to publish a new Client version along with a Runtime update.
 
 For a reboot, you will likely want to update the raw specs:
 
-* in the CI/CD, wait for `release_gdev_specs` button to be available and click on it
-* in the CI/CD, wait for `release_gtest_specs` button to be available and click on it
-* wait for both jobs to finish
-* update the Client raw specs with `cargo xtask update-raw-specs runtime-800`
+- in the CI/CD, wait for `release_gdev_specs` button to be available and click on it
+- in the CI/CD, wait for `release_gtest_specs` button to be available and click on it
+- wait for both jobs to finish
+- update the Client raw specs with `cargo xtask update-raw-specs runtime-800`
 
 #### New version (mandatory)
 
 Update Client values:
 
-* update Client version (in `Cargo.toml`)
-* update `Cargo.lock` with `cargo build`
-  
+- update Client version (in `Cargo.toml`)
+- update `Cargo.lock` with `cargo build`
+
 #### Publish Docker image
 
 Commit everything and push the branch:
 
-* in the CI/CD, a new pipeline has been launched
-* you can stop jobs `create_g1_data`, `gdev_srtool`, `gtest_srtool` (won't be used)
-* click on `gdev_docker_deploy` and `gtest_docker_deploy`
+- in the CI/CD, a new pipeline has been launched
+- you can stop jobs `create_g1_data`, `gdev_srtool`, `gtest_srtool` (won't be used)
+- click on `gdev_docker_deploy` and `gtest_docker_deploy`
 
 The Docker images should now be available at: https://hub.docker.com/r/duniter/duniter-v2s-gdev/tags.