diff --git a/content/concepts/consensus-network/amendments/contribute-code-flow.md b/content/concepts/consensus-network/amendments/contribute-code-flow.md
index 76d1375c75..befceef1a0 100644
--- a/content/concepts/consensus-network/amendments/contribute-code-flow.md
+++ b/content/concepts/consensus-network/amendments/contribute-code-flow.md
@@ -50,7 +50,7 @@ The general development path breaks down as follows:
 
 1. Create a fork or branch in the [`rippled` repository](https://github.com/XRPLF/rippled) to develop your code.
 
-  **Tip:** If you're not sure where to start, _Dev Null Productions_ provides a detailed and thorough [`rippled` Source Code Guide](https://xrpintel.com/source).
+    **Tip:** If you're not sure where to start, _Dev Null Productions_ provides a detailed and thorough [`rippled` Source Code Guide](https://xrpintel.com/source).
 
 2. Run unit and integration tests. Running a server in _stand-alone mode_ is useful for testing your changes in an isolated environment, but you may want to stand up a private network for extensive changes.
 
diff --git a/dactyl-config.yml b/dactyl-config.yml
index 6173350561..7f42d87e7b 100644
--- a/dactyl-config.yml
+++ b/dactyl-config.yml
@@ -964,6 +964,11 @@ pages:
         targets:
             - ja
 
+    -   md: concepts/consensus-network/amendments/contribute-code-flow.md
+        targets:
+            - en
+            - ja
+
     -   md: concepts/consensus-network/amendments/known-amendments.md
         targets:
             - en
@@ -1925,11 +1930,6 @@ pages:
         targets:
             - ja
 
-    -   md: tutorials/manage-the-rippled-server/configuration/propose-amendments.md
-        targets:
-            - en
-            - ja
-
     -   md: tutorials/manage-the-rippled-server/configure-peering/configure-peering.md
         targets:
             - en