@@ -81,9 +81,9 @@ a message is signed after another by including the signature of the first in the
8181second. This is equivalent to reading out a newspaper headline to prove a
8282message was recorded after a given day.
8383
84−However, the problem of proving one message was sent before any later ones
84+The problem of proving that one message was sent before any later ones
8585inverts the problem. You can solve this with newspapers by placing the message
86−in the text of the newspaper. However, while reading a newspaper requires no
86+in the text of the newspaper. While reading a newspaper requires no
8787central party, writing one does. For a long time, this sort of message was
8888always handled by a central party. SSL revocations are managed by a few central
8989parties. When you buy property, it's not sufficient to have the previous owner
@@ -92,7 +92,7 @@ the owner may sell their property to multiple people and there would be no way
9292to determine who is the new owner. With the land registry, all you need to do is
9393ask the registry which sale happened first, and that's the one that counts.
9494
95−However, Urbit is yours and it's forever. Trusting central registries
95+Again, Urbit is yours and it's forever. Trusting central registries
9696jeopardizes both. The keen reader will notice that the problem of determining
9797which key rotation happened first is exactly the double-spend problem that
9898Satoshi solved with his proof of work algorithm for Bitcoin. His first block
@@ -102,11 +102,11 @@ it after that date.[^1]
102102
103103Some argue that blockchain is only good for money. This is myopic and is
104104generally based on the experience that its most valuable application so far has
105−been money. However, blockchain is a cryptographic primitive to do what was
106−previously impossible: prove that one message was signed before another without
107−a central party. Blockchain was discovered by someone trying to create digital
108−money, and he needed that primitive, but that doesn't mean that's all it's good
109−for.
105+been money. The deeper problem that the blockchain cryptographic primitive
106+allows one to solve a previously impossible task: prove that one message was
107+signed before another without a central party. Blockchain was discovered by
108+someone trying to create digital money, and he needed that primitive, but that
109+doesn't mean that's all it's good for.
110110
111111Thus, we store our PKI data on a blockchain for our second kind of name:
112112[planets](/docs/glossary/planet). A planet is a 32-bit address which has key information stored on the
@@ -116,7 +116,7 @@ everyone on the network will listen to the blockchain for key data. Thus, we
116116have global consistency, permanence, and self sovereignty. We know of no other
117117solution that can provide these properties.
118118
119−However, while small individually, the aggregate PKI data for all nodes on the
119+While small individually, the aggregate PKI data for all nodes on the
120120network may become very large. This is not an issue for comets because nobody
121121needs to store comet keys except for those which they're talking with, and even
122122those can be garbage-collected and re-requested and verified. For planets, there
@@ -136,7 +136,7 @@ state locally, dramatically reducing gas costs to the point that Tlon offers a
136136free-to-use public "roller" which aggregates transactions and submits them as a
137137batch.
138138
139−However, 4 billion is not enough addresses for every device on the planet today,
139+Of course, 4 billion is not enough addresses for every device on the planet today,
140140much less in a few decades. So, we apply our maxim of re-examining our choices
141141at each level for each use case. Examining the idea maze above, we cannot use
142142the blockchain option for everything since the data is too big. However, it's
@@ -150,7 +150,7 @@ for its own moons, and anyone who needs to talk to your moons can ask you for
150150the keys.
151151
152152This is the sense in which moons are true ships: they're permanent names and you
153−own them completely, as long as you own the planet. However, they're not
153+own them completely, as long as you own the planet. But they're not
154154independent ships — their keys can always be revoked by their planet.
155155
156156To create a sane network, we require global consistency for all our names. There