-[mailing list](http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev),
-introduce yourself (people will happily say "hello" back"). Read through
-[recent posts](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/)
-and the [[charter]], and let everyone know, on the list that you're
-happy with it and agree to it.
-2. The next thing you should do is read through the [bugs
-list](http://bugs.libre-riscv.org) and see if there are any bugs that
-pique your interest. A fascinating way to do that is to view the
-[dependency graph](https://bugs.libre-soc.org/showdependencygraph.cgi?id=1&display=web&rankdir=LR)
-3. After that, go ahead and take a look at the [git repositories](https://git.libre-riscv.org).
-
+ [mailing list](http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev),
+ introduce yourself (people will happily say "hello" back"). Read through
+ [recent posts](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/)
+ and the [[charter]], and let everyone know, on the list that you're
+ happy with it and agree to it.
+2. The next thing you should do is read through the
+ [bugs list](http://bugs.libre-riscv.org) and
+ see if there are any bugs that pique your interest.
+ A fascinating way to do that is to view the
+ [dependency graph](https://bugs.libre-soc.org/showdependencygraph.cgi?id=1&display=web&rankdir=LR)
+3. After that, go ahead and take a look at the
+ [git repositories](https://git.libre-riscv.org).