on master help sign in
Arvo network message doc: Boot a comet, not a moon

A number of developers new to Urbit have been reading these docs and running these examples, only to realize that booting a moon ships their planets for unknown reasons. This is a simple doc fix that can push people to comets in the meantime. And this is probably easier to do than starting a moon anyways. But maybe all of these docs should point people towards doing these on fake ships? In an ideal Urbit world, dumb examples never sink your planet, but unfortunately this can be the case now, and perhaps we should make that explicit to early developer adopters.

commit103f3f31a63fc25d3f7814bf4baae46925e2eed2 authorKeaton Dunsford <keaton@tlon.io> dateTue 30 May 2017, 19:41 (9 years ago) parenta524218
1 file changed+4−4
docs/arvo/network.md+4−4
docs/arvo/network.md+4−4
@@ -174,10 +174,10 @@ Run it with these commands:
174174 >=
175175
176176Replace `~sampel-sipnym` with another urbit. The easiest thing to do is
177−to start a moon, a sub-identity of your urbit. If you don't know how to
178−start a moon, see [the user admin section](/docs/using/admin/). Don't
179−forget to start the `%examples-pong` app on that urbit, too. You should
180−see, on the foreign urbit, this output:
177+to start a comet, a free and disposable Urbit identity. If you don't know
178+how to start a comet, see [the user setup section](/docs/using/setup/).
179+Don't forget to start the `%examples-pong` app on that urbit, too. You
180+should see, on the foreign urbit, this output:
181181
182182 [%receiving 'howdy']
183183