on master help sign in
CR Style Fixes
7e57beaZach Alberico
content/using/install.md+7−6
@@ -120,9 +120,9 @@ http: live (insecure, loopback) on 12321
120~sampel_commet:dojo>
120~sampel_commet:dojo>
121```
121```
122
122
123−When your ship is finished booting, you will see either the `~sampel_commet:dojo>` or `~sampel_commet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-x` to switch into Dojo.
123+When your ship is finished booting, you will see either the `~sampel_commet:dojo>` or `~sampel_commet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-X` to switch into Dojo.
124
124
125−To exit Urbit, use `control-d` or enter `|exit` into Dojo.
125+To exit Urbit, use `Ctrl-D` or enter `|exit` into Dojo.
126
126
127To start your ship up again, run the following from your `urbit` directory (note the lack of `-c` argument):
127To start your ship up again, run the following from your `urbit` directory (note the lack of `-c` argument):
128```sh
128```sh
@@ -261,9 +261,9 @@ Linux:
261
261
262Either command will create a directory called `sampel-palnet/` and begin building your ship. It may take a few minutes.
262Either command will create a directory called `sampel-palnet/` and begin building your ship. It may take a few minutes.
263
263
264−When 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.
264+When 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.
265
265
266−To shut down your ship, use `control-d`. To start your ship up again, run the following from your `urbit` directory:
266+To shut down your ship, use `Ctrl-D`. To start your ship up again, run the following from your `urbit` directory:
267
267
268```sh
268```sh
269macOS:
269macOS:
@@ -297,14 +297,15 @@ To update to the latest binary, download and extract it to replace your existing
297
297
298For example, if in your current `urbit` directory you have an `urbit-v0.10.7-<OS>` directory along with a ship directory called `mycomet`, and a new `urbit-v0.10.8-<OS>` binary was just released, then you'd run the following commands from your `urbit` directory:
298For example, if in your current `urbit` directory you have an `urbit-v0.10.7-<OS>` directory along with a ship directory called `mycomet`, and a new `urbit-v0.10.8-<OS>` binary was just released, then you'd run the following commands from your `urbit` directory:
299
299
300−First shut down your ship, by running the following in dojo (or `control-d`).
300+First shut down your ship, by running the following in dojo (or `Ctrl-D`).
301```
301```
302|exit
302|exit
303```
303```
304
304
305+**NOTE**: Your ship itself can be reused, only the binary needs to be changed. This is why we have the directory structure configured as an `urbit` directory that contains your ship and your binary. This structure makes it easy to swap in new binaries. If you have your ship *inside* the `urbit-vX.XX.X` directory, move it out before deleting that directory.
306+
305Delete the old binary directory from your `urbit` directory:
307Delete the old binary directory from your `urbit` directory:
306
308
307−**NOTE**: Your ship itself can be reused, only the binary needs to be changed. This is why we have the directory structure configured as an `urbit` directory that contains your ship and your binary. This structure makes it easy to swap in new binaries. If you have your ship *inside* the `urbit-vX.XX.X` directory, move it out before deleting that directory.
308```sh
309```sh
309macOS:
310macOS:
310rm -rf urbit-v0.10.7-darwin
311rm -rf urbit-v0.10.7-darwin