diff --git a/docs/networks/node-ops/access-onchain-data/evm-gateway/evm-gateway-setup.md b/docs/networks/node-ops/access-onchain-data/evm-gateway/evm-gateway-setup.md
index 3530d37764..109097842c 100644
--- a/docs/networks/node-ops/access-onchain-data/evm-gateway/evm-gateway-setup.md
+++ b/docs/networks/node-ops/access-onchain-data/evm-gateway/evm-gateway-setup.md
@@ -234,12 +234,12 @@ make DOCKER_RUN_DETACHED=true DOCKER_HOST_PORT=1234 DOCKER_HOST_MOUNT=/my/host/d
 ### Startup bootstrap indexing
 
 Once your EVM Gateway is up and running you will see it indexing the Flow network which was configured. At the present time this
-is a lengthy process (possible 1-3 days, depending on CPU core count) during which time the gateway will not respond to queries. 
+is a lengthy process (possibly 1-3 days, depending on CPU core count) during which time the gateway will not respond to queries. 
 Once the data is fully indexed the gateway can serve requests to clients.
 
-To speed up gateway setup we recommend backing up the /flow-evm-gateway/data directory to use when creating additional nodes 
+To speed up gateway setup we recommend backing up the `/${GATEWAY_HOME_DIR}/data` directory to use when creating additional nodes 
 using the same release version. We are currently working on an export/import feature that will enable gateway operators to 
-store state snapshots which can be used to bootstrap the creation of new nodes and mitigate the slow startup time.
+store state snapshots to bootstrap newly created nodes without the delay.
 
 ### Account and Key Management