diff --git a/docs/the_nimbus_book/src/pi-guide-mainnet.md b/docs/the_nimbus_book/src/pi-guide-mainnet.md index 1f3e2d8b0..026048351 100644 --- a/docs/the_nimbus_book/src/pi-guide-mainnet.md +++ b/docs/the_nimbus_book/src/pi-guide-mainnet.md @@ -1,9 +1,9 @@ # Validating with a Raspberry Pi: Mainnet advice -Whether or not your Pi is up to the task will depend on a number of factors such as SSD speed, network connectivity, etc. So it's best to verify performance on a testnet first. +Whether or not your Pi is up to the task will depend on a number of factors such as SSD speed, network connectivity, etc. As such, it's best to verify performance on a testnet first. The best thing you can do is to set your Pi to run Pyrmont. **If you have no trouble syncing and attesting on Pyrmont, your setup should be more than good enough for mainnet** as well (Mainnet is expected to use fewer resources).
-Although we don't expect it to happen, we recommend buying a spare Pi, and enterprise grade SSD, on the off-chance yours fails. Keep your original SD around, so you can copy the image + Nimbus software quickly over to your spare SSD. +Although we don't expect a modern Pi to fail, we recommend buying a spare Pi, and enterprise grade SSD, on the off-chance it does; keep your original SD around, to make it easy for you to copy the image over.We've been running lots of PIs and NanoPCs 24/7 for 3 years and never got a hardware fail. It is easy (and cheap) to get redundancy of components (even spare PIs in different locations, more of this to come).
— Ethereum on ARM (@EthereumOnARM) November 28, 2020