rev

node-operators/networks/run-a-node/flags.md

@@ -42,15 +42,7 @@ This guide will cover some of the most common flags and show you how to access a
     - **`fast-unsafe`** - same as `fast`, but skips downloading the state proofs
     - **`warp`** - downloads the latest state and proof
 - **`--prometheus-port`** - specifies a custom Prometheus port
-
-## Lazy Loading Flags {: #lazy-loading-flags }
-
-Lazy loading lets a Moonbeam node operate while downloading network state in the background, eliminating the need to wait for full synchronization before use. 
-
 - **`fork-chain-from-rpc`** - allows lazy loading by relying on a specified RPC for network state until the node is fully synchronized e.g. `--fork-chain-from-rpc 'https://moonbeam.public.blastapi.io'`
-
-You can further customize your use of the lazy loading functionality with the following optional parameters:
-
 - **`block`** - specifies the block number from which to start forking the chain
 - **`fork-state-overrides`** - path to a JSON file containing state overrides to be applied when forking 
 - **`runtime-override`** - path to a WASM file to override the runtime when forking

node-operators/networks/run-a-node/overview.md

@@ -98,6 +98,9 @@ Upon spooling up a node with this feature, you'll see output like the following:
 
 --8<-- 'code/node-operators/networks/run-a-node/terminal/lazy-loading.md'
 
+!!! note
+    Lazy loading is resource-intensive. Ensure your node meets the minimum [System Requirements](#requirements). 
+
 You can further customize your use of the lazy loading functionality with the following optional parameters:
 
 - **`block`** - specifies the block number from which to start forking the chain