Update connect-light-node documentation (#68)

* update connect-light-node documentation

* update epoch value

src/connect-light-node.md

@@ -7,7 +7,7 @@ Note that if you spin up multiple services like this using the same `priv-key` s
 - ⚠️ change `lightpush-peer` to the node you wish. Note that the multiaddress is logged by every peer at startup.
 
 ```jsx
-docker run --network waku-simulator_simulation alrevuelta/go-waku-light:07b8f32 \
+docker run --network waku-simulator_simulation alrevuelta/go-waku-light:4fabb22 \
 --eth-endpoint=http://foundry:8545 \
 --contract-address=0xCf7Ed3AccA5a467e9e704C703E8D87F634fB0Fc9 \
 send-messages-loop \
@@ -18,14 +18,15 @@ send-messages-loop \
 --pubsub-topic=/waku/2/rs/66/0 \
 --cluster-id=66 \
 --lightpush-peer=/ip4/10.2.0.16/tcp/60000/p2p/16Uiu2HAmAA99YfoLitSXgY1bHaqjaTKhyrU4M4y3D1rVj1bmcgL8 \
---message-every-secs=5
+--message-every-secs=5 \
+--epoch-size-secs=1
 ```
 
 Note that in some examples, it could be interesting to run multiple instances, either in parallel or one after the other. For example if you set `amount-message-to-send=1` this will send just 1 message and exit. You can for example run this 100 times, where a fresh RLN membership will be created on every run, create a new peerId, send a message and exit.
 
 ```bash
 for i in {1..5}; do
-    docker run --rm --network waku-simulator_simulation alrevuelta/go-waku-light:07b8f32 \
+    docker run --rm --network waku-simulator_simulation alrevuelta/go-waku-light:4fabb22 \
     --eth-endpoint=http://foundry:8545 \
     --contract-address=0xCf7Ed3AccA5a467e9e704C703E8D87F634fB0Fc9 \
     send-messages-loop \
@@ -37,6 +38,7 @@ for i in {1..5}; do
     --cluster-id=66 \
     --lightpush-peer=/ip4/10.2.0.16/tcp/60000/p2p/16Uiu2HAm6a4kUT7YutsbwgQcmWw5VLzN3zj1StwiBVf2LUH9kb4A \
     --message-every-secs=5 \
+    --epoch-size-secs=1 \
     --amount-message-to-send=1
     
     if [ $? -ne 0 ]; then