@@ -127,9 +127,26 @@ Either command will create a directory called `sampel-palnet/` and begin buildin
128When your ship is finished booting, you will see either the `~sampel-palnet:dojo>` or `~sampel-palnet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-x` to switch into Dojo. At that point, you should permanently erase your keyfile from your machine.
128When your ship is finished booting, you will see either the `~sampel-palnet:dojo>` or `~sampel-palnet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-x` to switch into Dojo. At that point, you should permanently erase your keyfile from your machine.
130−To shut down your ship, use `Crtl-d`.
130+To shut down your ship, use `Ctrl-d`.
132−To start your ship up again, run `./urbit sampel-palnet` from the directory where your Urbit binary is saved. Don't boot multiple instances of your ship at the same time.
132+To start your ship up again, run `./urbit sampel-palnet/` from the directory
133+where your Urbit binary is saved. Note that in this usage,
134+`sampel-palnet/` is the path of a folder, which by default is located in the same folder as
135+the Urbit binary. This folder is called your ship's **pier**, and you
136+can put it wherever you like.
138+Never boot multiple instances of your ship at the same time. You can prevent
139+this from happening on accident by only ever keeping a single copy of your pier.
141+### Updating to the latest binary
143+Most updates to Urbit are downloaded and applied automatically as OTA (Over the
144+Air) updates. Occasionally it would be infeasible to distribute an update this
145+way, and a new `urbit` binary is released. This is announced in the [urbit-dev](https://groups.google.com/a/urbit.org/forum/#!forum/dev)
146+Google Group when it occurs (as are all OTA updates). To update to the latest binary, follow
147+the same process outlined [above](#urbit) to download and extract it into a new folder
148+(the binary linked on this page will always be the latest). Then run it as
149+before with `./urbit path/to/sampel-palnet/`.
134## The Dojo
151## The Dojo
@@ -157,19 +174,9 @@ Good, your Dojo is working correctly. Now let's run our first useful command in
158The `>=` output means that a command was successful. Now you can see your ship's files in its Unix directory.
175The `>=` output means that a command was successful. Now you can see your ship's files in its Unix directory.
160−## Updating to the latest binary
162−Most updates to Urbit are downloaded and applied automatically as OTA (Over the
163−Air) updates. Occasionally it would be infeasible to distribute an update this
164−way, and a new `urbit` binary is released. This is announced in the `urbit-dev`
165−Google Group when it occurs (as are all OTA updates). To update to the latest binary, follow
166−the same process outlined [above](#urbit) to download and extract it into a new folder
167−(the binary linked on this page will always be the latest),
168−then move your ship's **pier** (the folder with your ship's name) from the
169−folder containing the old `urbit` binary to the folder containing the new one.
170−Then delete the folder containing the old binary.
172−### Using Landscape
179+## Using Landscape
174Landscape is the Urbit web interface, and it's the best way to interact with your ship. Chrome and Brave are the recommended browsers for using Landscape. To get onto Landscape:
181Landscape is the Urbit web interface, and it's the best way to interact with your ship. Chrome and Brave are the recommended browsers for using Landscape. To get onto Landscape: