@@ -7,21 +7,19 @@ category = "arvo"
77
88Continuity on the [Ames](../ames) network occasionally needs to be broken at
99this early stage in order to correct a networking error or to make major changes
10−to Arvo. These infrequent events are known as **breaches** which either cause an
11−individual ship to forget its network message history, called a **personal
12−breach**, or cause the entire network to forget its history, called a **network
13−breach**.
10+to [Arvo](../arvo). These infrequent events are known as **breaches**, which cause an
11+individual ship to forget its network message history.
1412
15−Personal breaches are always initiated by the user, frequently in response to a
13+Breaches are always initiated by the user, frequently in response to a
1614connectivity error. The easiest way to do this is with [Bridge](../bridge).
1715There are two types of personal breaches: changing networking keys, and changing
1816the Urbit ID ownership address.
1917
20−Network breaches happen when a major Arvo revision that cannot be implemented
21−via an [OTA update](../ota-updates) occurs. When this happens, a new binary will
22−need to be downloaded, and your ship's [pier](../pier) needs to be moved to the
23−directory containing the new binary. The most recent network breach occurred in
24−December 2020, and we expect it to be the final one.
18+Historically, there were also "network breaches", which happened when a major
19+Arvo revision that could not be implemented via an [OTA update](../ota-updates)
20+occured. Network breaches were effectively breaching every ship on the network
21+at once. The most recent network breach occurred in December 2020, and we expect
22+it to be the final one.
2523
2624### Further Reading
2725