on master help sign in
fixes fakezod instructions (#284)
856e1bermariani
content/using/develop.md+2−2
@@ -20,7 +20,7 @@ When developing, however, we recommend [booting a development ship](#creating-a-
20
20
21## Core development {#core}
21## Core development {#core}
22
22
23−Working on the core means improving the Urbit project itself, working with the existing community of Urbit developers.
23+Working on the core means improving the Urbit project itself, working with the existing community of Urbit developers.
24
24
25Just arrived and unsure what to work on? An ideal way to get started is by experimenting with the system, talking to other developers, and reading (or [contributing to](https://github.com/urbit/docs)) the [documentation](/docs/).
25Just arrived and unsure what to work on? An ideal way to get started is by experimenting with the system, talking to other developers, and reading (or [contributing to](https://github.com/urbit/docs)) the [documentation](/docs/).
26
26
@@ -50,7 +50,7 @@ Because such a ship has no presence on the network, you don't need an Azimuth id
50To create a fake ship named `~zod`, run the command below. You can replace `zod` with any valid Urbit ship-name.
50To create a fake ship named `~zod`, run the command below. You can replace `zod` with any valid Urbit ship-name.
51
51
52```
52```
53−urbit -F zod
53+./urbit -F zod
54```
54```
55
55
56Now you should see a block of boot messages, starting with the Urbit version number. Welcome!
56Now you should see a block of boot messages, starting with the Urbit version number. Welcome!