docs(consensus): Minor fixes to decentralization docs (#3307)

matter-labs · Nov 21, 2024 · 7f9a999 · 7f9a999
1 parent 11d0b51
commit 7f9a999
Show file tree

Hide file tree

Showing 5 changed files with 106 additions and 276 deletions.
diff --git a/contracts b/contracts
diff --git a/docs/src/guides/advanced/16_decentralization.md b/docs/src/guides/advanced/16_decentralization.md
@@ -8,7 +8,7 @@ and enabled as follows:
 Run the following to generate consensus secrets:
 
 ```
-docker run --entrypoint /usr/bin/zksync_external_node "matterlabs/external-node:2.0-v25.1.0" generate-secrets > consensus_secrets.yaml
+docker run --entrypoint /usr/bin/zksync_external_node "matterlabs/external-node:2.0-v25.0.0" generate-secrets > consensus_secrets.yaml
 chmod 600 consensus_secrets.yaml
 ```
 
@@ -55,12 +55,12 @@ long) to achieve that:
 
 ## Gitops repo config
 
-If you are using the matterlabs gitops repo to configure the main node, it is even more complicated becase the
+If you are using the matterlabs gitops repo to configure the main node, it is even more complicated because the
 `consensus_config.yaml` file is rendered from a helm chart. See the
 [example](https://github.com/matter-labs/gitops-kubernetes/blob/main/apps/environments/mainnet2/server-v2/server-v2-core.yaml),
 to see where you have to paste the content of the `consensus_config.yaml` file.
 
-You need to embed the `consenus_secrets.yaml` file into a kubernetes config:
+You need to embed the `consensus_secrets.yaml` file into a kubernetes config:
 
 ```yaml
 apiVersion: v1
+1 −1		l1-contracts/contracts/chain-registrar/ChainRegistrar.sol
+16 −5		l1-contracts/deploy-scripts/DeployL1.s.sol
+2 −1		l1-contracts/test/foundry/unit/concrete/chain-registrator/ChainRegistrar.t.sol