problem: outdated config examples

rel: #7

docs/04-upstream-config.adoc

@@ -32,7 +32,8 @@ Run it with `-reindex` option, or set `txindex=1` in the config.
 ----
 version: v1
 
-defaults:
+cluster:
+  defaults:
   - chains:
       - ethereum
     options:
@@ -41,36 +42,35 @@ defaults:
       - kovan
     options:
       min-peers: 2
-
-upstreams:
-  - id: us-nodes
-    chain: auto
-    connection:
-      grpc:
-        host: 35.226.252.117
-        port: 443
-        tls:
-          ca: ca.crt
-          certificate: client.crt
-          key: client.p8.key
-  - id: infura-eth
-    chain: ethereum
-    labels:
-      provider: infura
-    options:
-      disable-validation: true
-    connection:
-      ethereum:
-        rpc:
-          url: "https://mainnet.infura.io/v3/${INFURA_USER}"
-          basic-auth:
-            username: ${INFURA_USER}
-            password: ${INFURA_PASSWD}
-        ws:
-          url: "wss://mainnet.infura.io/ws/v3/${INFURA_USER}"
-          basic-auth:
-            username: ${INFURA_USER}
-            password: ${INFURA_PASSWD}
+  upstreams:
+    - id: us-nodes
+      chain: auto
+      connection:
+        grpc:
+          host: 35.226.252.117
+          port: 443
+          tls:
+            ca: ca.crt
+            certificate: client.crt
+            key: client.p8.key
+    - id: infura-eth
+      chain: ethereum
+      labels:
+        provider: infura
+      options:
+        disable-validation: true
+      connection:
+        ethereum:
+          rpc:
+            url: "https://mainnet.infura.io/v3/${INFURA_USER}"
+            basic-auth:
+              username: ${INFURA_USER}
+              password: ${INFURA_PASSWD}
+          ws:
+            url: "wss://mainnet.infura.io/ws/v3/${INFURA_USER}"
+            basic-auth:
+              username: ${INFURA_USER}
+              password: ${INFURA_PASSWD}
 ----
 
 There're two main segments for upstreams configuration:
@@ -81,21 +81,21 @@ There're two main segments for upstreams configuration:
 In the example above we have:
 
 - default configuration for _Ethereum Mainnet_ which accepts upstream as valid when it not in fast synchronization mode
-  and has at least 10 peers. For _Kovan Testnet_ nodes the requirements are much relieved
+and has at least 10 peers.For _Kovan Testnet_ nodes the requirements are much relieved
 - as upstreams it has 2 configurations
-  * balancer connects to another Dshackle/another machine by using gRPC protocol
-    ** accepts (i.e. proxies) any blockchain available on that remote
-    ** verifies TLS certificate of the server
-    ** uses client certificate for authentication, i.e. remote server is accepting only clients authenticated by a
-       certificate
-  * connects to Infura provided _Ethereum Mainnet_
-    ** configuration is using placeholders for `${INFURA_USER}` and `${INFURA_PASSWD}` which will be replaced with
-       corresponding environment variables values
-    ** uses Basic Authentication to authenticate requests on Infura
-    ** label `[provider: infura]` is set for that particular upstream, which can be selected during a request. For example for
-      some requests you may want to use nodes with that label only, i.e. _"send that tx to infura nodes only"_,
-      or _"read only from archive node, with label [archive: true]"_
-    ** upstream validation (peers, sync status, etc) is disabled for that particular upstream
+* balancer connects to another Dshackle/another machine by using gRPC protocol
+** accepts (i.e. proxies) any blockchain available on that remote
+** verifies TLS certificate of the server
+** uses client certificate for authentication, i.e. remote server is accepting only clients authenticated by a
+certificate
+* connects to Infura provided _Ethereum Mainnet_
+** configuration is using placeholders for `${INFURA_USER}` and `${INFURA_PASSWD}` which will be replaced with
+corresponding environment variables values
+** uses Basic Authentication to authenticate requests on Infura
+** label `[provider: infura]` is set for that particular upstream, which can be selected during a request.For example for
+some requests you may want to use nodes with that label only, i.e. _"send that tx to infura nodes only"_,
+or _"read only from archive node, with label [archive: true]"_
+** upstream validation (peers, sync status, etc) is disabled for that particular upstream
 
 === Configuration options