Fix code block related syntax issues in markdown files

doc/02-Installation.md

@@ -108,8 +108,7 @@ The packages for RHEL/CentOS depend on other packages which are distributed as p
 [EPEL repository](http://fedoraproject.org/wiki/EPEL). Please make sure to enable this repository by following
 [these instructions](http://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F).
 
-> Please note that installing Icinga Web 2 on **RHEL/CentOS 5** is not supported due to EOL versions of PHP and
-> PostgreSQL.
+> Please note that installing Icinga Web 2 on **RHEL/CentOS 5** is not supported due to EOL versions of PHP and PostgreSQL.
 
 ### <a id="installing-from-package-example"></a> Installing Icinga Web 2
 

doc/04-Resources.md

@@ -28,7 +28,7 @@ to handle authentication and authorization, monitoring data or user preferences.
 
 #### <a id="resources-configuration-database-example"></a> Example
 
-````
+```
 [icingaweb-mysql-tcp]
 type      = db
 db        = mysql
@@ -54,8 +54,7 @@ port      = 5432
 username  = icingaweb
 password  = icingaweb
 dbname    = icingaweb
-
-````
+```
 
 ### <a id="resources-configuration-ldap"></a> LDAP
 
@@ -73,7 +72,7 @@ A LDAP resource represents a tree in a LDAP directory. LDAP is usually used for
 
 #### <a id="resources-configuration-ldap-example"></a> Example
 
-````
+```
 [ad]
 type        = ldap
 hostname    = localhost
@@ -81,8 +80,7 @@ port        = 389
 root_dn     = "ou=people,dc=icinga,dc=org"
 bind_dn     = "cn=admin,ou=people,dc=icinga,dc=org"
 bind_pw     = admin
-
-````
+```
 
 ### <a id="resources-configuration-ssh"></a> SSH
 
@@ -97,11 +95,10 @@ ssh authentication.
 
 #### <a id="resources-configuration-ssh-example"></a> Example
 
-````
+```
 
 [ssh]
 type        = "ssh"
 user        = "ssh-user"
 private_key = "/etc/icingaweb2/ssh/ssh-user"
-
-````
+```

doc/07-Preferences.md

@@ -22,7 +22,7 @@ For storing preferences in INI files you have to add the following section to th
 ```
 [preferences]
 type = ini
-````
+```
 
 ### <a id="preferences-configuration-db"></a> Store Preferences in a Database
 

doc/99-Vagrant.md

@@ -25,9 +25,9 @@ environment. This enables developers and users to test Livestatus,
 MySQL and PostgreSQL backends as well as the LDAP authentication. All you
 have to do is install Vagrant and run:
 
-````
+```
 vagrant up
-````
+```
 
 > **Note:** The first boot of the vm takes a fairly long time because
 > you'll download a plain CentOS base box and Vagrant will automatically
@@ -56,6 +56,6 @@ Both LDAP and a MySQL are configured as authentication backend. Please use one o
 All software required to run tests is installed in the virtual machine.
 In order to run all tests you have to execute the following command:
 
-````
+```
 vagrant ssh -c "icingacli test php unit"
-````
+```

modules/monitoring/doc/commandtransports.md

@@ -22,11 +22,11 @@ the order of sections in the commandtransports.ini.
 
 A local Icinga instance requires the following directives:
 
-````
+```
 [icinga2]
-transport = local
-path = /var/run/icinga2/cmd/icinga2.cmd
-````
+transport   = local
+path        = /var/run/icinga2/cmd/icinga2.cmd
+```
 
 When sending commands to the Icinga instance, Icinga Web 2 opens the file found
 on the local filesystem underneath 'path' and writes the external command to it.
@@ -36,14 +36,14 @@ on the local filesystem underneath 'path' and writes the external command to it.
 A command pipe on a remote host's filesystem can be accessed by configuring a
 SSH based command transport and requires the following directives:
 
-````
+```
 [icinga2]
-transport = remote
-path = /var/run/icinga2/cmd/icinga2.cmd
-host = example.tld
-;port = 22                              ; Optional. The default is 22
-user = icinga
-````
+transport   = remote
+path        = /var/run/icinga2/cmd/icinga2.cmd
+host        = example.tld
+user        = icinga
+;port        = 22 ; Optional. The default is 22
+```
 
 To make this example work, you'll need to permit your web-server's user
 public-key based access to the defined remote host so that Icinga Web 2 can
@@ -56,23 +56,23 @@ key file on the local filesystem that is used to access the remote host.
 To accomplish this, a new resource is required that is defined in your
 transport's configuration instead of a user:
 
-````
+```
 [icinga2]
-transport = remote
-path = /var/run/icinga2/cmd/icinga2.cmd
-host = example.tld
-;port = 22                              ; Optional. The default is 22
-resource = example.tld-icinga2
-````
+transport   = remote
+path        = /var/run/icinga2/cmd/icinga2.cmd
+host        = example.tld
+resource    = example.tld-icinga2
+;port        = 22 ; Optional. The default is 22
+```
 
 The resource's configuration needs to be put into the resources.ini file:
 
-````
+```
 [example.tld-icinga2]
-type = ssh
-user = icinga
+type        = ssh
+user        = icinga
 private_key = /etc/icingaweb2/ssh/icinga
-````
+```
 
 ## Configuring transports for different Icinga instances
 
@@ -81,7 +81,7 @@ define which transport belongs to which Icinga instance by providing the
 directive 'instance'. This directive should contain the name of the Icinga
 instance you want to assign to the transport:
 
-````
+```
 [icinga1]
 ...
 instance = icinga1
@@ -89,8 +89,8 @@ instance = icinga1
 [icinga2]
 ...
 instance = icinga2
-````
+```
 
 Associating a transport to a specific Icinga instance causes this transport to
 be used to send commands to the linked instance only. Transports without a
-linked Icinga instance are utilized to send commands to all instances.
+linked Icinga instance are utilized to send commands to all instances.