@@ -49,11 +49,11 @@ If you plan to distribute planets in any capacity, you must keep your star runni
50To make this as simple as possible, we’re building Terraform-based tooling for star and planet hosting via Google Cloud Platform. Once it’s ready we’ll open source the tooling so you can host stars and planets for yourself and others.
50To make this as simple as possible, we’re building Terraform-based tooling for star and planet hosting via Google Cloud Platform. Once it’s ready we’ll open source the tooling so you can host stars and planets for yourself and others.
52−In the meantime, there are existing instructions for those familiar with booting a Linux instance on GCP, AWS, Digital Ocean, etc.
52+In the meantime, there are [existing instructions](@/install.md) for those familiar with booting a Linux instance on GCP, AWS, Digital Ocean, etc.
54### Distributing planets
54### Distributing planets
56−You can distribute planets from your star via Bridge. As a reminder if you do distribute planets, please boot and run your star on the Arvo network, otherwise those planets won't be able to connect, which has a negative effect on the network as a whole, as orphan planets are left with very limited functionality.
56+You can distribute planets from your star via [Bridge](https://bridge.urbit.org/). As a reminder if you do distribute planets, please boot and run your star on the Arvo network, otherwise those planets won't be able to connect, which has a negative effect on the network as a whole, as orphan planets are left with very limited functionality.
58### Software updates
58### Software updates
@@ -61,16 +61,15 @@ By default, your star accepts software updates from its galaxy and routes them t
62#### Breaches
62#### Breaches
64−To ensure new planets can connect to you, you're expected to participate in network-wide breaches, by updating to the latest Urbit version, deleting (or archiving) your pier, and then booting your ship. If you don’t participate, you will be left behind by the rest of the network and won’t be able to communicate with anyone who has updated to the new era.
64+To ensure new planets can connect to your ship, users are expected to participate in network-wide breaches by [updating to the latest Urbit version](@/install.md), deleting (or archiving) your pier, and then booting your ship using the new binary. If you don’t participate, you won’t be able to communicate with anyone on the network who has updated to the new era.
66+Network-wide breaches are distinct from personal breaches, wherein an individual ship cycles its personal network keys using bridge, and then follows the same steps outlined above.
67### Star-owner etiquette
68### Star-owner etiquette
69−If you distribute planets, boot and run your star on the Arvo network, or the planets won't be able to boot for the first time or connect.
70+- If you distribute planets, boot and run your star on the Arvo network, or the planets won't be able to boot for the first time or connect.
71−A star is networking infrastructure. For that reason, the machine running your star or galaxy must have sufficient bandwidth and processing power for your dependent planets.
71+- A star is networking infrastructure. For that reason, the machine running your star or galaxy must have sufficient bandwidth and processing power for your dependent planets.
73−When messaging others, communicate using your star only when speaking in an official/infrastructural capacity. Otherwise, use your personal planet.
72+- When messaging others, communicate using your star only when speaking in an official/infrastructural capacity. Otherwise, use your personal planet.
@@ -86,16 +85,15 @@ We host regular contributor calls where you can discuss the technical matters of
87#### The urbit-dev mailing list
86#### The urbit-dev mailing list
89−Those interested in developing on Urbit are encouraged to add themselves to the urbit-dev mailing list:https://groups.google.com/a/urbit.org/forum/#!forum/dev.
88+Those interested in developing on Urbit are encouraged to add themselves to [the urbit-dev mailing list](https://groups.google.com/a/urbit.org/forum/#!forum/dev).
91#### Support
90#### Support
93−We are a small team, but we do our best to answer support related inquiries. Please email us at support@urbit.org with questions.
92+We are a small team, but we do our best to answer support related inquiries. Please email us at [support@urbit.org](mailto:support@urbit.org) with questions.
95#### Roadmap for further development
94#### Roadmap for further development
97−We periodically publish our ongoing development roadmap. You can find the latest here: [https://urbit.org/posts/2019-10-3-roadmap/].
96+We periodically publish our ongoing development roadmap. You can find the latest [here](https://urbit.org/posts/2019-10-3-roadmap/).
100## Governance {#governance}
98## Governance {#governance}