@@ -12,12 +12,18 @@ There are two kinds of breaches: **personal breaches** and **network breaches**.
13Ships 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.
13Ships 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.
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.
17There are two types of personal breaches - one where your Ethereum ownership address
23There are two types of personal breaches - one where your Ethereum ownership address
18remains the same, and one where you are switching to a new Ethereum ownership
24remains the same, and one where you are switching to a new Ethereum ownership
19address. We make the emphasis about the Ethereum _ownership_ address as
25address. 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.
22If you will be keeping the same Ethereum ownership address and would like to perform a
28If you will be keeping the same Ethereum ownership address and would like to perform a
23personal breach, follow the steps below.
29personal breach, follow the steps below.
@@ -27,31 +33,30 @@ personal breach, follow the steps below.
27- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then click `Send Transaction` and wait for the progress bar to appear.
33- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then click `Send Transaction` and wait for the progress bar to appear.
28- Download your new keyfile following these instructions: [Generate your
34- Download your new keyfile following these instructions: [Generate your
29 keyfile](@/using/operations/using-bridge.md#generate-your-keyfile).
35 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).
31- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
37- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
32- Delete your keyfile after successfully booting.
38- Delete your keyfile after successfully booting.
33- Rejoin your favorite chat channels and subscriptions.
39- Rejoin your favorite chat channels and subscriptions.
35−If you are switching to a new Ethereum ownerhsip address, you will necessarily be
41+If you are switching to a new Ethereum ownership address you will have the
36−performing a personal breach as well - there is no way to change the ownership
42+choice as to whether or not you want to breach. This is to cover the case when
37−address without also breaching. The process here is slightly different.
43+you are transferring to another address you own. The process here is slightly different.
39- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
45- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
40- Click on `ID: Identity and security settings` at the bottom, then click
46- Click on `ID: Identity and security settings` at the bottom, then click
41 `Transfer this point`.
47 `Transfer this point`.
42−- Enter the new Ethereum address you would like to transfer ownership to.
48+- Enter the new Ethereum address you would like to transfer ownership to. Click
43− Click `Generate & Sign Transaction`, then click `Send Transaction` and wait
49+ `Generate & Sign Transaction`, then click `Send Transaction` and wait for the
44− for the progress bar to complete.
50+ progress bar to complete.
45- Logout of your current session in Bridge by clicking `Logout` at the top, and
51- Logout of your current session in Bridge by clicking `Logout` at the top, and
46 then login to your new ownership address.
52 then login to your new ownership address.
47- From here, following the directions on how to [Accept your
53- From here, following the directions on how to [Accept your
48 transfer](@/using/operations/using-bridge.md#accept-your-transfer), [Set your
54 transfer](@/using/operations/using-bridge.md#accept-your-transfer), [Set your
49 networking keys](@/using/operations/using-bridge.md#set-your-networking-keys),
55 networking keys](@/using/operations/using-bridge.md#set-your-networking-keys),
50 and [Generate your
56 and [Generate your
51− keyfile](@/using/operations/using-bridge.md#generate-your-keyfile). The main
57+ keyfile](@/using/operations/using-bridge.md#generate-your-keyfile). The option
52− difference with the above method is that you do not check the `Breach
58+ whether or not to breach is in the Accept your Transfer step.
54−- Delete or archive your old [pier](@/glossary/pier.md).
59+- Delete or archive your old [pier](@/docs/glossary/pier.md).
55- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
60- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
56- Delete your keyfile after successfully booting.
61- Delete your keyfile after successfully booting.
57- Rejoin your favorite chat channels and subscriptions.
62- Rejoin your favorite chat channels and subscriptions.