@@ -17,7 +17,7 @@ Let’s talk first about what an Urbit ID is and what it does. Then we’ll cove
1717
1818
1919
20−**Summary**
20+Summary {% .font-bold .subpixel-antialiased .pt-8 %}
2121
2222Your Urbit ID is a short, four-syllable name like ~ravmel-ropdyl that you own with an eight-syllable master passkey like ~palfun-foslup-fallyn-balfus. This name and key lets you log into Urbit OS, and it’s used to encrypt packets you send over the Urbit network. Soon it will also be a master key that allows holding and sending of Bitcoin and other cryptocurrencies. Your Urbit ID and passkey belong to you like any other cryptographic assets. No one can take them away from you (just make sure to store the key safely).
2323
@@ -31,7 +31,7 @@ Urbit IDs are distributed by a sponsorship tree. At the top of the tree are 28 (
3131
3232You can also call stars ‘infrastructure nodes’ and galaxies ‘governance nodes’, since those are more descriptive names for their roles. Stars help route packets, kind of like an ISP. And galaxies are a bit like DNS root servers or ICANN members. The difference, of course, is that Urbit IDs are owned cryptographically by many different people and accrue reputation independently.
3333
34−**Design**
34+Design {% .font-bold .subpixel-antialiased .pt-8 %}
3535
3636At a high level, there are three important things to understand about the overall Urbit ID system design.
3737
@@ -47,7 +47,7 @@ The Urbit ID sponsorship tree is not intended to be a social system in any way.
4747
4848Your relationship with your sponsor should be sort of like your ISP or a utility provider: a passive, non-invasive relationship. If it isn’t to your liking, moving to a new sponsor is very easy.
4949
50−**Digital Land**
50+Digital Land {% .font-bold .subpixel-antialiased .pt-8 %}
5151
5252Urbit IDs are property, and we think of the entire registry of Urbit IDs as a vast territory of digital land.
5353