reformat index

[libreriscv.git] / index.mdwn

diff --git a/index.mdwn b/index.mdwn
index 700b1846c046f30a757ce35e2558bd1223e54d21..c673bb88c50a7f5eef5ee1b7ff6e6d24ca5bc2ff 100644 (file)
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,4 +1,4 @@
-# Welcome to LibreSoC
+# Welcome to LibreSOC
 
 > We're building a chip. A fast chip. A safe chip. A trusted chip.
 
@@ -6,7 +6,8 @@
 
 > Oh and here, have the source code...
 
-Sounds cool? Learn more about the [why](why_a_libresoc) behind LibreSOC and our [goals](About_Us).
+Sounds cool? Learn more about the [why](why_a_libresoc) behind LibreSOC
+and [our mission](The_Mission).
 
 # Our Team
 
@@ -14,7 +15,10 @@ We are proud of our talented and diverse [team](about_us).
 
 # How Can I Help?
 
-If you would like to fund us, see [[funding]]. We currently have some funding and always appreciate more!  If you are a Corporation or an individualyou can donate tax-free to NLNet, and they can in turn gift our developers.  Contact lkcl@lkcl.net for more information.
+If you would like to fund us, see [[funding]]. We currently have some
+funding and always appreciate more!  If you are a Corporation or an
+individual you can donate tax-free to NLNet, and they can in turn gift
+our developers.  Contact lkcl@lkcl.net for more information.
 
 If you want to write code with us, keep reading.
 
@@ -23,22 +27,19 @@ If you want to write code with us, keep reading.
 introduce yourself, and read through
 [recent posts](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/)
 and the [[charter]].
-
 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.
-
 3. After that, go ahead and take a look at the resources section below. 
-Try and clone a repository with ``git clone https://git.libre-riscv.org/git/repositoryname.git``
-
-4. If you plan to do HDL work, you should familiarize yourself with our [[HDL_workflow]].
-
+Try and clone a repository with
+``git clone https://git.libre-riscv.org/git/repositoryname.git``
+4. If you plan to do HDL work, you should familiarize yourself with our
+   [[HDL_workflow]].
 5. We do have funding available (see [[nlnet]]) upon completion of issues -
 we are also working on procuring more funding which gets the project to
 nanometre scale tapeout.
-
-6. After all this, if you feel that Libre-SoC is a good cause that
-you would like to contribute to, add yourself to the [[current_members]]
+6. After all this, if you feel that Libre-SoC is a something that
+you would like to contribute to, add yourself to the [current_members](about_us)
 page, fill in some information about yourself, and join the mailing list
 and say hello.
 
@@ -51,7 +52,8 @@ the Libre-SoC.
 
 The highest priority needed at the moment is a c++ engineer to work on
 a MESA 3D driver. This will begin life similar to SwiftShader however
-retaining the vectorisation and predication intrinsics as well as hardware accelerated opcodes (all of which SwiftShader lacks)
+retaining the vectorisation and predication intrinsics as well as hardware
+accelerated opcodes (all of which SwiftShader lacks)
 
 Medium to long-term we need HDL engineers. Particularly those familiar
 with nMigen or just python.  Most of the techniques being used require
@@ -75,6 +77,7 @@ bugtracker).
 | Archives | <http://lists.libre-riscv.org/pipermail> |
 | Git repositories | <http://git.libre-riscv.org> |
 | Kazan (Vulkan driver) | <https://salsa.debian.org/Kazan-team/kazan> |
+| Standards           | [[standards]] |
 | Further Information | [[resources]] |
 
 # Main Pages
@@ -89,6 +92,7 @@ bugtracker).
 * [[ztrans_proposal]]
 * [[simple_v_extension/specification/mv.x]]
 * [[simple_v_extension/specification/ld.x]]
+* [[future_feature_proposals]]
 * Specifications and [[resources]]
 
 # Spike Emulator