@@ -24,14 +24,18 @@ Troubleshooting](../ship-troubleshooting) guide. Also reach out for help in the
2424Help channel in the Urbit Community group `~bitbet-bolbel/urbit-community`, or,
2525failing that, in the `#ship-starting-support` channel in our [Discord
2626server](https://discord.gg/n9xhMdz) to see if there is another option.
27+Connectivity issues are typically related to a bug, and you may be able to help
28+us fix it by emailing us at `support@urbit.org`.
2729
28−There are two types of breaches - one where your Ethereum ownership address
29−remains the same, and one where you are switching to a new Ethereum ownership
30−address. We make the emphasis about the Ethereum _ownership_ address as changing
31−your [proxies](@/docs/glossary/proxies.md) does not require a breach.
30+There are two separate sequences of actions you need to take in order to breach.
31+One flow is for when you wish to keep Ethereum ownership address of the ship the
32+same, and the other is for when you are transferring the ship to a new Ethereum
33+ownership address. We make the emphasis about the Ethereum _ownership_ address
34+as changing your [proxies](@/docs/glossary/proxies.md) does not require a
35+breach.
3236
33−If you will be keeping the same Ethereum ownership address and would like to perform a
34−breach, follow the steps below.
37+If you will be keeping your ship at the same Ethereum ownership address and
38+would like to perform a breach, follow the steps below.
3539
3640- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
3741- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
@@ -43,7 +47,7 @@ breach, follow the steps below.
4347- Delete your keyfile after successfully booting.
4448- Rejoin your favorite chat channels and subscriptions.
4549
46−If you are switching to a new Ethereum ownership address you will have the
50+If you are transferring a ship to a new Ethereum ownership address you will have the
4751choice as to whether or not you want to breach. This is to cover the case when
4852you are transferring to another address you own. The process here is slightly different.
4953
@@ -74,7 +78,7 @@ was released that could not be implemented via an [OTA
7478update](@/docs/glossary/ota-updates.md). The continuity era is given by an
7579integer in Ames that is incremented when the network breaches. Only ships with
7680the same such value are able to communicate with one another. The most recent
77−network breach occurred in December 2020, and we expect it to be the final one.
81+network breach occurred in December 2020, and we expect it to have been the final one.
7882
7983If another network breach does occur, we will provide accompanying documentation
8084on what to do to transfer your ship and all of its data to the new era.