@@ -31,13 +31,13 @@ Urbit OS is a completely new, carefully architected software stack: a VM, progra
3131
3232The main thing to understand about our ‘overlay OS’, as we call it, is that the foundation is a single, simple function. This function is the Urbit OS virtual machine. We call it ‘Nock’. The entire Urbit OS system compiles down to Nock, and Nock is just 33 lines of code.
3333
34−Nock is similar in spirit to WASM or the JVM: it’s a uniform machine code for every Urbit ship. A frozen foundation makes for some nice features:
34+Nock is similar in spirit to WASM or the JVM: it’s a uniform machine code for every Urbit [ship](https://urbit.org/docs/glossary/ship/). A frozen foundation makes for some nice features:
3535
3636The state of your Urbit OS is a pure function of its event history. It’s auditable, inspectable, repeatable. You can actually trust it.
37−Writing decentralized apps becomes vasty simpler than in the old world, since every node computes exactly the same way.
37+Writing decentralized apps becomes vastly simpler than in the old world, since every node computes exactly the same way.
3838The entire Urbit OS stack, from programming language to applications, is upgradeable over the network. For ordinary users, this makes for almost no system administration.
3939
40−Since Nock is a protocol for computing itself, any two nodes on the urbit network can easily share data, communicate and connect their software. 20th century systems could never do this without a MEGACORP acting as the intermediary.
40+Since Nock is a protocol for computing itself, any two nodes on the Urbit network can easily share data, communicate and connect their software. 20th century systems could never do this without a MEGACORP acting as the intermediary.
4141
4242<img class="full ba w-100 mv4" src="https://media.urbit.org/site/understanding-urbit/network-os/urbit-os-diagram-apart.svg"/>
4343