Fix markdown issue

Markdown is tested on Dillinger.io and the interpreter is not exactly
the same as the one on Github, so I fix the Markdown to be more
readable.

docs/setup/beacons.md

@@ -1,6 +1,7 @@
 # Beacons
 
 > **Version Support**
+> 
 > Beacons will be introduced in v2.4.0
 
 Cachet will periodically communicate with our remote server. This is done so

docs/setup/cors.md

@@ -13,5 +13,6 @@ You may configure your Cachet installation for CORS very easily. To blacklist ev
 - You'll see a Allowed domains textarea, fill in any domains that you
   want to access the API as a comma separated list:
 
-> _Text_
-> https://demo.cachethq.io,https://status.cachethq.io
+```
+https://demo.cachethq.io,https://status.cachethq.io
+```

docs/setup/installation.md

@@ -5,7 +5,6 @@ This guide will detail how to install Cachet on your server.
 ## Download the source code with Git
 
 > **Check out the latest version!**  
-> 
 > The tags below are examples of what will be shown.
 > You should always run git checkout on the latest tag.
 
@@ -36,13 +35,11 @@ file to `.env` regardless of what environment you're working on.
 It's now just a case of editing this new .env file and setting the values of your setup.
 
 > **Environment Configuration Notice**  
->
 > Any values with spaces in them should be contained within double quotes.
 
 The `.env` file set environment variables that will be used by the application.
 
 > **SQLite hosts**  
->
 > If you're using SQLite then your .env file should not contain a
 > `DB_HOST` key. You'll also need to touch ./database/database.sqlite
 > and give it the required permissions.
@@ -62,7 +59,6 @@ If you are installing Cachet as a contributor, you can forget the `--no-dev`
 option.
 
 > **Tip for Windows users**  
->
 > If you're stuck at the Composer stage, you can run
 > `composer install --no-dev -o --no-scripts`
 > which usually fixes any issues on Windows servers.
@@ -82,7 +78,6 @@ php artisan app:install
 > This will result in all of your encrypted/hashed data being lost.
 
 > **Getting a 500 - Internal Server Error?**  
->
 > If you get a 500 error when visiting your status page, you may need to
 > run `chmod -R 777 storage/` for it to work or `rm -rf bootstrap/cache/*`
 
@@ -91,7 +86,6 @@ You can also try to give permissions to cache chmod -R 777 bootstrap/
 ## Running Cachet on Apache
 
 > **Required Apache Modules**  
->
 > You need to enable `mod_rewrite` for Apache. On Debian-based systems you can do this by
 >
 > `sudo a2enmod rewrite`