@@ -133,18 +133,6 @@ in this example.
133133
134134Put `<key>` in a file and that file becomes `<keyfile>`.
135135
136−To breach a moon -- that is, to reset its presence on the network so that it's treated as a freshly spawned ship by others -- run from the parent ship:
137−
138−```
139−|moon-breach ~faswep-navred-sampel-palnet
140−```
141−
142−To cycle the keys of a moon without breaching, run:
143−
144−```
145−|moon-cycle-keys ~sampel-sipnym-wicdev-wisryt
146−```
147−
148136You can use the resulting output in the same installation flow from the [Installing Urbit](@/using/install.md) guide, following the same scheme as for booting a planet. That scheme is:
149137
150138```sh
@@ -174,6 +162,19 @@ $ ./urbit -w faswep-navred-sampel-palnet -k <keyfile> -c mymoon
174162
175163Moons are automatically synced to their parent `%kids` desk, and can control applications on their parent planet using `|link`.
176164
165+To breach a moon -- that is, to reset its presence on the network so that it's treated as a freshly spawned ship by others -- run from the parent ship:
166+
167+```
168+|moon-breach ~faswep-navred-sampel-palnet
169+```
170+
171+To cycle the keys of a moon without breaching, run:
172+
173+```
174+|moon-cycle-keys ~sampel-sipnym-wicdev-wisryt
175+```
176+
177+
177178### Escaping A Sponsor
178179
179180To use the network as a planet or star, you must be sponsored by an active star or galaxy, respectively. If your sponsor isn't suiting your needs, you can escape to a different one. The [Bridge](https://bridge.urbit.org/) software doesn't yet support escaping. For the time being, however, you can follow this guide.