fmt

docs/src/guides/advanced/16_decentralization.md

@@ -34,7 +34,8 @@ If you are using the recommended file-based configuration then you'll need to ad
 ```yaml
 consensus:
   server_addr: '0.0.0.0:3054'
-  public_addr: '???'
+  public_addr:
+    '???'
     # Address under which the node is accessible to the other nodes.
     # It can be a public domain, like `example.com:3054`, in case the main node is accessible from the internet,
     # or it can be a kubernetes cluster domain, like `server-v2-core.<cluster name>.svc.cluster.local:3054` in
@@ -70,7 +71,8 @@ content:
 
 ```yaml
 server_addr: '0.0.0.0:3054'
-public_addr: '???'
+public_addr:
+  '???'
   # Address under which the node is accessible to the other nodes.
   # It can be a public domain, like `example.com:3054`, in case the main node is accessible from the internet,
   # or it can be a kubernetes cluster domain, like `server-v2-core.<cluster name>.svc.cluster.local:3054` in
@@ -86,8 +88,8 @@ genesis_spec:
       weight: 1
   leader: validator:public:??? # same as above - main node will be the only validator and the only leader.
   seed_peers:
-      - key: 'node:public:ed25519:...' # node public key of the main node (copy this PUBLIC key from the secrets you generated)
-        addr: '???' # same as public_addr above
+    - key: 'node:public:ed25519:...' # node public key of the main node (copy this PUBLIC key from the secrets you generated)
+      addr: '???' # same as public_addr above
 ```
 
 And a `consensus_secrets.yaml` file with the with the secrets you generated previously: