@@ -35,7 +35,7 @@ If you accidentally booted with the same keyfile twice, the only remedy is perfo
3535
3636**Turn your ship off and on again.** Use `ctrl-d` to gracefully exit your ship, and then start it again. This can solve many issues.
3737
38−### Perform a personal breach. {#personal-breach}
38+### Perform a personal breach. {#personal-breach}
3939
4040A breach is when ships on the network reset their continuity. The breaching ship 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 has network has forgotten about it.
4141
@@ -86,11 +86,18 @@ This can happen if they have the wrong keys of yours, or if you have the wrong k
8686in the Dojo, where `~sampel-palnet` is the other ship's name. Then, compare it to the scry information that you saved. If that information matches up, it means that the other ship is the problem. If it **doesn't** match up, your ship has wrong information about the other ship. If you have such wrong information, you can fix this by running:
8787
8888```
89−|start %eth-manage
90−:eth-manage %look-ethnode
89+:azimuth-tracker|listen ~ %app %azimuth-tracker
9190```
9291
93−If they have wrong keys of yours, you need to somehow ask them to to run that same command.
92+The last line above syncs from an Ethereum node for _all_ ships on the network. If you only wanted to sync with certain ships, run:
93+
94+```
95+:azimuth-tracker|listen ~[~sampel-palnet ~zod ~marzod] %app %azimuth-tracker
96+```
97+
98+`~sampel-palnet ~zod ~marzod` are example ship-names; replace these with any number of desired ships-names.
99+
100+The above commands work if you have the wrong keys of other ships. If other ships have wrong keys of _yours_, you need to somehow ask them to to run such a command.
94101
95102### I can talk to some ships, but I can't talk to my sponsor and some other ships
96103