@@ -5,21 +5,17 @@ template = "doc.html"
5description = "A guide to getting involved with the Urbit project."
5description = "A guide to getting involved with the Urbit project."
8−We accept submissions for improving our [code](https://github.com/urbit/urbit/) and [documentation](https://github.com/urbit/docs/) alike.
8+We welcome submissions for improving our [code](https://github.com/urbit/urbit/) and [documentation](https://github.com/urbit/docs/) alike. If you're looking to get involved, there are a few things you can do to get started right away:
10−If you're looking to get involved, there are a few things you can do:
12−- Join the [urbit-dev](https://groups.google.com/a/urbit.org/forum/#!forum/dev) mailing list.
10+- Join the [urbit-dev](https://groups.google.com/a/urbit.org/forum/#!forum/dev) mailing list
13- [Ask us about Hoon School](mailto:support@urbit.org), a course we run to teach the Hoon programming language and Urbit application development.
11- [Ask us about Hoon School](mailto:support@urbit.org), a course we run to teach the Hoon programming language and Urbit application development.
14- Check out the "good contributor issues" tag in the [urbit](https://github.com/urbit/urbit/labels/good%20contributor%20issue) and [arvo](https://github.com/urbit/arvo/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+contributor+issue%22) Github repositories.
12- Check out the "good contributor issues" tag in the [urbit](https://github.com/urbit/urbit/labels/good%20contributor%20issue) and [arvo](https://github.com/urbit/arvo/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+contributor+issue%22) Github repositories.
15−- Reach out to [support@urbit.org](mailto:support@urbit.org) to say hi and ask any questions you might have.
13+- Reach out to [support@urbit.org](mailto:support@urbit.org) to say hi and ask any questions you might have. We're always happy to try to point you in the right direction.
17−If you're getting set up to work on the Urbit or Arvo code base for the first time, start with our [Getting Started](./docs/getting-started/_index.md) guide, then have a look at [CONTRIBUTING.md](https://github.com/urbit/urbit/blob/master/CONTRIBUTING.md) in the Urbit repository.
19−Many contributors start by contributing to the [documentation](https://github.com/urbit/docs), [urbit.org](https://github.com/urbit/urbit.org), or [bridge](https://github.com/urbit/bridge). If you're not yet comfortable with Hoon, we recommend starting there.
15+Many contributors start by contributing to the [documentation](https://github.com/urbit/docs), [urbit.org](https://github.com/urbit/urbit.org), or [bridge](https://github.com/urbit/bridge) repositories. If you're not yet comfortable with Hoon, we recommend starting there.
21−If smart contracts (Solidity) are more your jam, have a look at [Azimuth](https://github.com/urbit/azimuth), Urbit's identity layer.
17+If you're just getting set up to work on the Urbit or Arvo code base for the first time, see our [Getting Started](./docs/getting-started/_index.md) guide, then have a look at [CONTRIBUTING.md](https://github.com/urbit/urbit/blob/master/CONTRIBUTING.md) in the Urbit repository.
23## Code style
19## Code style
25−Before contributing Hoon code, you should familiarize yourself with the [Hoon style guide](./docs/learn/hoon/style.md). For a good example of idiomatic Hoon, see [ford.hoon](https://github.com/urbit/arvo/blob/master/sys/vane/ford.hoon).
21+Before contributing Hoon code, you should familiarize yourself with the [Hoon style guide](./docs/learn/hoon/style.md). For a good example of idiomatic Hoon, see [Ford](https://github.com/urbit/arvo/blob/master/sys/vane/ford.hoon).