From cff4e5ea6c359019b11a4868b0f384c36b64e27e Mon Sep 17 00:00:00 2001
From: woodser <13068859+woodser@users.noreply.github.com>
Date: Tue, 7 Oct 2025 06:19:58 -0400
Subject: [PATCH] update docs to avoid restarting seed nodes at the same time

---
 docs/create-mainnet.md   | 2 +-
 docs/deployment-guide.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/create-mainnet.md b/docs/create-mainnet.md
index 4118a0f548..f01274c403 100644
--- a/docs/create-mainnet.md
+++ b/docs/create-mainnet.md
@@ -72,8 +72,8 @@ In a new terminal window, run: `make seednode`.
 In a new terminal window, run: `make seednode2`.
 
 > **Notes**
-> * Avoid all seed nodes going offline at the same time. If all seed nodes go offline at the same time, the network will be reset, including registered arbitrators, the network filter object, and trade history. In that case, arbitrators need to restart or re-register, and the network filter object needs to be re-applied. This should be done immediately or clients will cancel their offers due to the signing arbitrators being unregistered and no replacements being available to re-sign.
 > * At least 2 seed nodes should be run because the seed nodes restart once per day.
+> * Avoid all seed nodes going offline at the same time. If all seed nodes go offline at the same time, network information like registered arbitrators and the network filter object will be reset. In that case, re-apply the network filter object (ctrl+f) and restart the arbitrators in order to re-register them with the seed nodes.
 
 ## Start and register the arbitrator
 
diff --git a/docs/deployment-guide.md b/docs/deployment-guide.md
index 1001a725fd..eb41f71d0c 100644
--- a/docs/deployment-guide.md
+++ b/docs/deployment-guide.md
@@ -133,8 +133,8 @@ Each seed node requires a locally running Monero node. You can use the default p
 Rebuild all seed nodes any time the list of registered seed nodes changes.
 
 > [!note]
-> * Avoid all seed nodes going offline at the same time. If all seed nodes go offline at the same time, the network will be reset, including registered arbitrators, the network filter object, and trade history. In that case, arbitrators need to restart or re-register, and the network filter object needs to be re-applied. This should be done immediately or clients will cancel their offers due to the signing arbitrators being unregistered and no replacements being available to re-sign.
 > * At least 2 seed nodes should be run because the seed nodes restart once per day.
+> * Avoid all seed nodes going offline at the same time. If all seed nodes go offline at the same time, network information like registered arbitrators and the network filter object will be reset. In that case, re-apply the network filter object (ctrl+f) and restart the arbitrators in order to re-register them with the seed nodes.
 
 ## Register keypairs with privileges