The "Running Bitcoin Core" section tells the reader how long the initial blockchain sync takes, but not what it costs in disk space or bandwidth. Following this guide end to end, one can start an initial block download without ever being told it will consume several hundred gigabytes of storage. bitcoind does warn about this at startup, but init.cpp only emits it when CheckDiskSpace fails so a user with a large drive is never told, and the warning arrives after the build and configuration steps are already done.
170e37353d6008d1675a6e063ab72e482f1b64f3 adds the storage and bandwidth cost to the existing sentence. It also shows the signet and regtest alternatives, following the pattern used elsewhere in this guide of pairing a cost with a way to opt out of it (-DENABLE_WALLET=OFF, -DWITH_QRENCODE=OFF, and so on).The exact figure is left as "several hundred gigabytes" rather than the current value. m_assumed_blockchain_size is already regularly updated per release in chainparams.cpp; a second copy here would have no update process attached to it.
0a85eab2228d6dffb8a8b44e09d206fb2fc26230 moves the command that starts the node out of "Other commands:" and into the running flow. A section titled "Running Bitcoin Core" previously never showed how to run it. The start command sat at the bottom of the page under a heading implying it was secondary.
Tested by running bitcoind -signet and bitcoind -regtest as documented.
