on master help sign in
troubleshooting: boot -> initialize
commit0daca2725d09b49b9e10c12769d228826c95c819 authorfang <git@fang.io> dateTue 16 Mar 2021, 22:41 (6 years ago) parent7e25095
1 file changed+3−3
content/using/os/ship-troubleshooting.md+3−3
content/using/os/ship-troubleshooting.md+3−3
@@ -22,11 +22,11 @@ If your issue is not covered here, please check out our [Troubleshooting Knowled
2222
2323An ounce of prevention is worth a pound of cure, so let's first go over some best practices to keep your ship in working order.
2424
25−### Only boot your ship once
25+### Only initialize your ship once
2626
27−Once your ship is booted, you should never boot it a second time. If you do boot it anew without special measures, you will experience trouble communicating with ships on the network you had talked to before.
27+Once your ship has been initialized (with the `-w` variation of the `./urbit` command), you should never do so a second time. If you do initialize it anew without special measures, you will experience trouble communicating with ships on the network you had talked to before.
2828
29−If you accidentally booted a second time, or want to intentionally start fresh, you need to perform a [personal breach](#personal-breach), which is explained in the next section.
29+If you accidentally did this a second time, or want to intentionally start fresh, you need to perform a [personal breach](#personal-breach), which is explained in the next section.
3030
3131### Do not delete your pier
3232