on master help sign in
Update ship-troubleshooting.md
commitcfa2bed0ce6f5c5ff3cf9d7b90b6ef9ef526e3be authorrmariani <robert@tlon.io> dateWed 18 Sep 2019, 15:16 (7 years ago) parent1105a99
1 file changed+1−1
reference/ship-troubleshooting.md+1−1
reference/ship-troubleshooting.md+1−1
@@ -34,7 +34,7 @@ If you accidentally booted with the same keyfile twice, the only remedy is perfo
3434
3535**Turn your ship off and on again.** Use `ctrl-d` to gracefully exit your ship, and then start it again. This can solve many issues.
3636
37−**Perform a personal breach.** {#personal-breach} A breach is when ships on the network reset their continuity; all other ships. A personal breach is when a single ship resets its own event log and sends an announcement to the network, asking all ships that have communicated with it to reset its networking information in their state. This makes it as though the ship was just started for the first time again, since everyone has network has forgotten about it.
37+**Perform a personal breach.** {#personal-breach} A breach is when ships on the network reset their continuity. The breaching ship clears its own event log and sends an announcement to the network, asking all ships that have communicated with it to reset its networking information in their state. This makes it as though the ship was just started for the first time again, since everyone has network has forgotten about it.
3838
3939Personal breaches often fix connectivity issues, but should only be used as a last resort.
4040