diff --git a/docs/installation.md b/docs/installation.md
index 4cd389c..3ea10c9 100644
--- a/docs/installation.md
+++ b/docs/installation.md
@@ -15,7 +15,7 @@ Consult the table below to confirm which version to run for each network.
 
 | Network     | Version |
 |-------------|---------|
-| Arc Testnet | v0.6.0  |
+| Arc Testnet | v0.8.0  |
 
 ## Pre-built Binary
 
@@ -61,7 +61,7 @@ source "$ARC_HOME/env"
 To install a specific version, run `arcup` with `--install`:
 
 ```sh
-arcup --install v0.6.0
+arcup --install v0.8.0
 ```
 
 Next, verify that the three Arc binaries are installed:
diff --git a/docs/running-an-arc-node.md b/docs/running-an-arc-node.md
index 58e7e5b..deb5fdd 100644
--- a/docs/running-an-arc-node.md
+++ b/docs/running-an-arc-node.md
@@ -237,9 +237,9 @@ curl -s -X POST http://localhost:8545 \
 ```
 
 The produced output is in JSON format.
-The `result` field represents the next block height, in hexadecimal
-(you can use `printf "%0d"` to translate it into decimal).
-It should increase over time.
+The `result` field contains the latest block number known to the execution
+layer, encoded as a hexadecimal quantity (use `printf "%d\n" <hex>` to convert
+to decimal). It should increase over time as the node follows the chain.
 If it remains `0x0`, check the logs of the consensus layer for errors.
 Common causes are a missing or incomplete snapshot, mismatched `$ARC_RUN`
 between the two processes, or the consensus layer not reaching any follow