@@ -12,12 +12,18 @@ There are two kinds of breaches: **personal breaches** and **network breaches**.
1212
1313Ships on the Ames network sometimes need to reset their continuity. A personal breach is when an individual ship announces to the network: "I forgot who I am, let's start over from scratch." That is, it 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 on the network has forgotten about it.
1414
15−Personal breaches often fix connectivity issues, but should only be used as a last resort. Before performing a personal breach, look at alternative fixes in the [Ship Troubleshooting](../ship-troubleshooting) guide. Also reach out for help in `~/~dopzod/urbit-help`, or, failing that, in the `#ship-starting-support` channel in our [Discord server](https://discord.gg/n9xhMdz) to see if there is another option.
15+Personal breaches often fix connectivity issues, but should only be used as a
16+last resort. Before performing a personal breach, look at alternative fixes in
17+the [Ship Troubleshooting](../ship-troubleshooting) guide. Also reach out for
18+help in the Help channel in the Urbit Community group
19+`~bitbet-bolbel/urbit-community`, or, failing that, in the
20+`#ship-starting-support` channel in our [Discord
21+server](https://discord.gg/n9xhMdz) to see if there is another option.
1622
1723There are two types of personal breaches - one where your Ethereum ownership address
1824remains the same, and one where you are switching to a new Ethereum ownership
1925address. We make the emphasis about the Ethereum _ownership_ address as
20−changing your [proxies](@/glossary/proxies.md) does not require a breach.
26+changing your [proxies](@/docs/glossary/proxies.md) does not require a breach.
2127
2228If you will be keeping the same Ethereum ownership address and would like to perform a
2329personal breach, follow the steps below.
@@ -27,31 +33,30 @@ personal breach, follow the steps below.
2733- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then click `Send Transaction` and wait for the progress bar to appear.
2834- Download your new keyfile following these instructions: [Generate your
2935 keyfile](@/using/operations/using-bridge.md#generate-your-keyfile).
30−- Delete or archive your old [pier](@/glossary/pier.md).
36+- Delete or archive your old [pier](@/docs/glossary/pier.md).
3137- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
3238- Delete your keyfile after successfully booting.
3339- Rejoin your favorite chat channels and subscriptions.
3440
35−If you are switching to a new Ethereum ownerhsip address, you will necessarily be
36−performing a personal breach as well - there is no way to change the ownership
37−address without also breaching. The process here is slightly different.
41+If you are switching to a new Ethereum ownership address you will have the
42+choice as to whether or not you want to breach. This is to cover the case when
43+you are transferring to another address you own. The process here is slightly different.
3844
3945- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
4046- Click on `ID: Identity and security settings` at the bottom, then click
4147 `Transfer this point`.
42−- Enter the new Ethereum address you would like to transfer ownership to.
43− Click `Generate & Sign Transaction`, then click `Send Transaction` and wait
44− for the progress bar to complete.
48+- Enter the new Ethereum address you would like to transfer ownership to. Click
49+ `Generate & Sign Transaction`, then click `Send Transaction` and wait for the
50+ progress bar to complete.
4551- Logout of your current session in Bridge by clicking `Logout` at the top, and
4652 then login to your new ownership address.
4753- From here, following the directions on how to [Accept your
4854 transfer](@/using/operations/using-bridge.md#accept-your-transfer), [Set your
4955 networking keys](@/using/operations/using-bridge.md#set-your-networking-keys),
5056 and [Generate your
51− keyfile](@/using/operations/using-bridge.md#generate-your-keyfile). The main
52− difference with the above method is that you do not check the `Breach
53− continuity` box.
54−- Delete or archive your old [pier](@/glossary/pier.md).
57+ keyfile](@/using/operations/using-bridge.md#generate-your-keyfile). The option
58+ whether or not to breach is in the Accept your Transfer step.
59+- Delete or archive your old [pier](@/docs/glossary/pier.md).
5560- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
5661- Delete your keyfile after successfully booting.
5762- Rejoin your favorite chat channels and subscriptions.