@@ -10,16 +10,17 @@ and _rift_. This numbering system partition messages according to the quantity
1010of networking key changes and quantity of
1111[breaches](@/using/id/guide-to-breaches.md), respectively. This is explained in
1212more detail below. These values are utilized by [Ames](@/docs/arvo/ames/ames.md)
13−and [Jael](@/docs/arvo/jael/jael-api.md) to ensure that you are communicating
14−with a ship using its most recent set of keys.
13+and [Jael](@/docs/arvo/jael/jael-api.md) to ensure that communication between
14+ships is always done with the most recent set of networking keys, and that
15+networking state is appropriately reset when a breach has occurred.
1516
1617Before it has been spawned, every ship begin with a `life` and `rift` of 0. For
1718galaxies, stars, and planets, these values are stored in the Azimuth PKI, while
1819for moons, these values are stored by their parent. Comets cannot change their
1920networking keys, nor can they breach, and so their `life` and `rift` are always 0.
2021
21−You can check your current life and rift number by running the `+keys our`
22−generator in dojo. You can inspect another ship's life and rift by running
22+You can check your current `life` and `rift` number by running the `+keys our`
23+generator in dojo. You can inspect another ship's `life` and `rift` by running
2324`+keys ~sampel-palnet`.
2425
2526## Life