@@ -13,10 +13,11 @@ ship (`urbit` on Linux and MacOS, `urbit.exe` on Windows). Vere manages your
13ship's [pier](https://urbit.org/docs/glossary/pier), handles events, and runs
13ship's [pier](https://urbit.org/docs/glossary/pier), handles events, and runs
14the Nock virtual machine that performs your ship's computations.
14the Nock virtual machine that performs your ship's computations.
16−Before version 1.9, Vere was split into two separate binaries: `urbit` and
16+Before version 1.9, Vere was split into two separate binaries: The `urbit`
17−`urbit-worker` (also known as the King and the Serf). As of version 1.9, these
17+"king" responsible for I/O and event persistence, and the `urbit-worker` "serf"
18+responsible for computations and state persistence. As of version 1.9, these
18have been merged into a single `urbit` (or `urbit.exe`) binary, though under the
19have been merged into a single `urbit` (or `urbit.exe`) binary, though under the
19−hood there's still two separate processes. The alternative King written in
20+hood there's still two separate processes. The alternative king written in
20Haskell, `urbit-king`, has also been deprecated, so there's now only one binary.
21Haskell, `urbit-king`, has also been deprecated, so there's now only one binary.
22Version 1.9 has introduced a couple of new features. The first is the concept of
23Version 1.9 has introduced a couple of new features. The first is the concept of