manuelly new lines are useless; markdown and html will do it

Signed-off-by: Marek Küthe <m.k@mk16.de>

docs/getting-started/index.md

@@ -1,14 +1,10 @@
 # Getting started
 
-Firstly we'd like to say that we're glad you'd like to join our network and
-greater community! This document will provide you with the directions you
-will need to follow in order to get connected.
+Firstly we'd like to say that we're glad you'd like to join our network and greater community! This document will provide you with the directions you will need to follow in order to get connected.
 
 ## Steps to follow
 
-Below you can follow the steps one-by-one to get yourself familiar with our
-practices and inner-workings and by the end you should have all the information
-and configuration details needed to get connected!
+Below you can follow the steps one-by-one to get yourself familiar with our practices and inner-workings and by the end you should have all the information and configuration details needed to get connected!
 
 1. [Rules](rules)
     * We have **few** but **strict** rules nonetheless

docs/index.md

@@ -11,65 +11,40 @@
 
 <img src="./img/map.png" class="floating_right" alt="CRXN logo">
 
-CRXN stands for **C**ommunity **R**un e**X**pansive **N**etwork. It's a computer network _run by the community for the community_.
-We provide an IPv6 (that's the freshest Internet Protocol out there to date) and on CRXN anything that can speak IPv6
-will be able to function correctly - a network without borders! We are focused with having a network that really focuses
-on the "end-to-end" principal of IP - that is to say that if you want to run something and make it available to other then
-you won't have to worry about NAT-traversal, port forwarding, lack of raw IP support and all the other non-sense that IPv4
-created (due to lack of addresses).
+CRXN stands for **C**ommunity **R**un e**X**pansive **N**etwork. It's a computer network _run by the community for the community_. We provide an IPv6 (that's the freshest Internet Protocol out there to date) and on CRXN anything that can speak IPv6 will be able to function correctly - a network without borders! We are focused with having a network that really focuses on the "end-to-end" principal of IP - that is to say that if you want to run something and make it available to other then you won't have to worry about NAT-traversal, port forwarding, lack of raw IP support and all the other non-sense that IPv4 created (due to lack of addresses).
 
-Compared to the clearnet (normal Internet) there isn't much fuss involved around getting
-a network ID assigned to you and so forth, we truly are for the community and all our members take some of their own time
-to work on their network and the greater CRXN inter-network as a whole.
+Compared to the clearnet (normal Internet) there isn't much fuss involved around getting a network ID assigned to you and so forth, we truly are for the community and all our members take some of their own time to work on their network and the greater CRXN inter-network as a whole.
 
-It's a great place to test out new protocols, networking projects, play games, exchange ideas and learn about networking,
-routing and network sub-systems themselves. You also get to learn how CRXN is put together which is a great way to learn
-networking with those that run networks already themselves.
+It's a great place to test out new protocols, networking projects, play games, exchange ideas and learn about networking, routing and network sub-systems themselves. You also get to learn how CRXN is put together which is a great way to learn networking with those that run networks already themselves.
 
 ## Our goals
 
 The network has a few goals that we always want to maintain as to not lose our allure:
 
 1. Be a network for learning
-    * We don't want to shun people away from using some new
-    routing protocol as it might be cool and interesting to
-    learn
+    * We don't want to shun people away from using some new routing protocol as it might be cool and interesting to learn
 2. Be reliable
-    * Of course when learning people should also make sure
-    their routers don't just accept any route without making
-    sure its valid - hence network operators should make sure
-    their networks operate even when some are causing mayhem
-    (malicious or learning by trial and error)
+    * Of course when learning people should also make sure their routers don't just accept any route without making sure its valid - hence network operators should make sure their networks operate even when some are causing mayhem (malicious or learning by trial and error)
     * Also shouldn't be painfully slow
 3. Diverse routing
-    * We want to try out protocols like **ospf**, **babel**, **bgp**
-    and so on and so forth
-    * We want to build a network out of a mix and match of these all
-    working in harmony together
+    * We want to try out protocols like **ospf**, **babel**, **bgp** and so on and so forth
+    * We want to build a network out of a mix and match of these all working in harmony together
     * Monocultures suck!
 4. Usable
-    * We have DNS, we have voice chat servers and we have IRC (we
-    even have gaming!) but we can always do with much **much more**!
-    * We want the users, _you_, to make the network usable for your
-    needs - who knows it might provide a service that helps out
-    someone else
+    * We have DNS, we have voice chat servers and we have IRC (we even have gaming!) but we can always do with much **much more**!
+    * We want the users, _you_, to make the network usable for your needs - who knows it might provide a service that helps out someone else
 5. Peering
-    * We want people to setup redundant links using whatever protocols
-    they want, be it **wireguard**, **GRE**, **fastd** etc.
+    * We want people to setup redundant links using whatever protocols they want, be it **wireguard**, **GRE**, **fastd** etc.
     * We want there to be interesting links and diversity
 6. _Chaos and Order_
     * The network should never stop experimenting
     * But it should have 99% uptime and safety fallbacks
-    * If you want to experiment - then go ahead and try cause
-    as little disruption as possible
-    * If you run a node - make it secure - sign routes etc.
-    to prevent others from experimenting from messing your
-    network up
+    * If you want to experiment - then go ahead and try cause as little disruption as possible
+    * If you run a node - make it secure - sign routes etc. to prevent others from experimenting from messing your network up
 
 We aim to create a more open Internet available to everyone and a place to learn about IP routing and networking in general.
 
-We don't use any particular tooling, the only thing that is standard is the IPv4 and IPv6 part. What tunnelling software, physical
-mediums or routing daemon you choose to use is up to you - this falls in line with our _open_ ethos.
+We don't use any particular tooling, the only thing that is standard is the IPv4 and IPv6 part. What tunnelling software, physical mediums or routing daemon you choose to use is up to you - this falls in line with our _open_ ethos.
 
 ## About the network
 
@@ -77,11 +52,9 @@ A few details about the network.
 
 ### Protocol support
 
-We only use IPv6 on CRXN because it has many features, such as link-local addresses, that make
-setting up dynamic routing protocols near-zero-config.
+We only use IPv6 on CRXN because it has many features, such as link-local addresses, that make setting up dynamic routing protocols near-zero-config.
 
-It's also the modern way of the Internet and means you will get a large space of addresses
-assigned to you.
+It's also the modern way of the Internet and means you will get a large space of addresses assigned to you.
 
 ### The range
 
@@ -97,9 +70,7 @@ We keep track of allocations on a Git-based repository called [_EntityDB_](https
 
 ### Joining the network
 
-Does it sound interesting enough for you already? Want to get connected? Then head on over
-to our [Getting started](getting-started/) section where you can find all the guides you need in order to get connected,
-follow the rules and have fun!
+Does it sound interesting enough for you already? Want to get connected? Then head on over to our [Getting started](getting-started/) section where you can find all the guides you need in order to get connected, follow the rules and have fun!
 
 ---
 

docs/people.md

@@ -49,8 +49,6 @@ Hackint IRC: `mark22k`
 
 ### Rany `~rany`
 
-<!-- <img src="people/rany.png"> -->
-
 Administer of EntityDB.
 
 Roles: EntityDB
@@ -61,8 +59,6 @@ Matrix: `@rany:fairydust.space`
 
 ### Alex Denes `~caskd`
 
-<!-- <img src="people/caskd.png"> -->
-
 European CRXN adminstration, runs the CRXN DNS root name server.
 
 Roles: Network services, CRXN DNS

docs/routing/forwarding.md

@@ -2,23 +2,15 @@
 
 ## Enabling forwarding
 
-We will be setting up the machine that runs bird as a router so therefore
-we need to make your Linux kernel's network stack not drop IPv6 packets
-that it receives (addressed to it via Ethernet) but are not addressed to
-it via IPv6 address - in other words it must try do something with these packets,
-namely attempt to forward them one hop closer to their initial destination.
+We will be setting up the machine that runs bird as a router so therefore we need to make your Linux kernel's network stack not drop IPv6 packets that it receives (addressed to it via Ethernet) but are not addressed to it via IPv6 address - in other words it must try do something with these packets, namely attempt to forward them one hop closer to their initial destination.
 
-Enabling forwarding on all interfaces can be achieved as follows (you will need
-to be root):
+Enabling forwarding on all interfaces can be achieved as follows (you will need to be root):
 
 ```bash
 echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
 ```
 
-However, after reboot it won't be saved and will go back to its defaults. Therefore
-what you need to do is to enable forwarding on boot-up, this can be done by
-adding an additional line to your `/etc/sysctl.conf` (which holds a bunch of
-these statements), it should look like this:
+However, after reboot it won't be saved and will go back to its defaults. Therefore what you need to do is to enable forwarding on boot-up, this can be done by adding an additional line to your `/etc/sysctl.conf` (which holds a bunch of these statements), it should look like this:
 
 ```bash
 net.ipv6.conf.all.forwarding=1