on master help sign in
Merge pull request #403 from mattlevan/patch-3

Fix typos

commit15e154dfea9da2cd9f9b389a968576ef02850375 authorrmariani <robert@tlon.io> dateMon 25 Feb 2019, 20:00 (8 years ago) parenta0a1d98e789706
1 file changed+2−2
getting-started/using-a-star.udon+2−2
getting-started/using-a-star.udon+2−2
@@ -17,7 +17,7 @@ Stars are above planets in the network hierarchy in the sense that each star spo
1717
1818Stars are also the "parents" planets. A new planet comes into existence only when spawned by a parent star. A parent planet is the sponsor of its children planets by default. This can change if a planet chooses to find a new sponsor (see the "Escaping a Sponsor" section below).
1919
20−Planets must have a sponsor star to use most features of the Arvo network. A planet cannot boot without a sponsor, and cannot make new connections to peers as long as it is not connected to a sponsor. Sponsorless planets will still be able to message discovered peers until such any such peers change their IP addresses.
20+Planets must have a sponsor star to use most features of the Arvo network. A planet cannot boot without a sponsor, and cannot make new connections to peers as long as it is not connected to a sponsor. Sponsorless planets will still be able to message discovered peers until any such peers change their IP addresses.
2121
2222## Responsibilities
2323
@@ -43,7 +43,7 @@ Occasionally, your star might lose network connectivity due to a known timer iss
4343
4444### Escaping a Sponsor
4545
46−Planets are, of course, able to change sponsors. To do this, they must request that a different star takes them on a dependent and that planet must accept the request. Planets cannot emancipate themselves from a sponsor without having a new sponsor lined up.
46+Planets are, of course, able to change sponsors. To do this, they must request that a different star takes them on as a dependent and that star must accept the request. Planets cannot emancipate themselves from a sponsor without having a new sponsor lined up.
4747
4848All of these actions happen on Azimuth. There will be Bridge functionality to handle these actions in the future, but for now users will need to interact directly with the contracts with MetaMask, through services such as [Etherscan.io](https://etherscan.io/address/ecliptic.eth#writeContract). A sketch of the process is listed below; for now, only the Ethereum-savvy should act on these steps.
4949