Fixed spelling mistakes in documentation.

Documentation/Tutorials/Administration-Tutorial.md

@@ -223,5 +223,5 @@ To bring the server back into service use the "clear server" command to clear th
 	MaxScale> clear server dbserver3 maintenance
 	MaxScale> 
 ```
-Note that maintenance mode is not persistent, if MaxScale restarts when a node is in maintenance mode a new instance of MaxScale will not honour this mode. If multiple MaxScale instances are configured to use the node them maintenance mode must be set within each MaxScale instance. However if multiple services within one MaxScale instance are using the server then you only need set the maintenance mode once on the server for all services to take note of the mode change.
+Note that maintenance mode is not persistent, if MaxScale restarts when a node is in maintenance mode a new instance of MaxScale will not honor this mode. If multiple MaxScale instances are configured to use the node them maintenance mode must be set within each MaxScale instance. However if multiple services within one MaxScale instance are using the server then you only need set the maintenance mode once on the server for all services to take note of the mode change.
 

Documentation/Tutorials/Galera-Cluster-Read-Write-Splitting-Tutorial.md

@@ -154,7 +154,7 @@ This monitor module will assign one node within the Galera Cluster as the curren
 [Galera Monitor]
 type=monitor
 module=galeramon
-diable_master_failback=1
+disable_master_failback=1
 servers=dbserv1, dbserv2, dbserv3
 user=maxscale
 passwd=96F99AA1315BDC3604B006F427DD9484

Documentation/Tutorials/MySQL-Replication-Read-Write-Splitting-Tutorial.md

@@ -150,7 +150,7 @@ port=3306
 socket=/tmp/ClusterMaster
 ```
 
-An address parameter may be given if the listener is required to bind to a particular network address when using hosts with multiple network addresses. The default behaviour is to listen on all network interfaces.
+An address parameter may be given if the listener is required to bind to a particular network address when using hosts with multiple network addresses. The default behavior is to listen on all network interfaces.
 
 The next stage is the configuration is to define the server information. This defines how to connect to each of the servers within the cluster, again a section is created for each server, with the type set to server, the network address and port to connect to and the protocol to use to connect to the server. Currently the protocol module for all database connections in MySQLBackend.
 ```

Documentation/Tutorials/Nagios-Plugins.md

@@ -29,7 +29,7 @@ While MaxScale resources and status can be monitored via CLI using maxadmin comm
 ![Nagios and MaxScale interaction](images/HowMaxScaleWorksWithNagios.png)
 
 
-There are three nagios plugin scripts that MaxScale provides.
+There are three Nagios plugin scripts that MaxScale provides.
 
 1. check_maxscale_threads.pl: This command provides you the status of current running threads and events in the queue on MaxScale Server.  The Performance data associated with this command current and historic wait time for threads and events
 
@@ -38,7 +38,7 @@ Current resources are: modules, services, listeners, servers, sessions, filters.
 
 3. check_maxscale_monitor.pl: This command provides you status of the configured monitor modules on MaxScale server. 
 
-In order to use these scripts on your Nagios Server, you need to copy them from the MaxScale binary package or download them from source tree on github.
+In order to use these scripts on your Nagios Server, you need to copy them from the MaxScale binary package or download them from source tree on GitHub.
 
 # MaxScale Nagios Plugin Requirements
 

Documentation/Tutorials/Notification-Service.md

@@ -53,7 +53,7 @@ MaxScale generates the feedback report containing following information:
  - MaxScale Version
  - An identifier of the MaxScale installation, i.e. the HEX encoding of SHA1 digest of the first network interface MAC address
  - Operating System (i.e Linux)
- - Operating Suystem Distribution (i.e. CentOS release 6.5 (Final))
+ - Operating System Distribution (i.e. CentOS release 6.5 (Final))
  - All the modules in use in MaxScale and their API and version
  - MaxScale server UNIX_TIME at generation time
 

Documentation/Tutorials/RabbitMQ-Setup-And-MaxScale-Integration.md

@@ -364,7 +364,7 @@ If the consumer.cnf file is not in the same directory as the binary file is, you
 # ./consumer -c path/to/file
 ```
 
-and start maxScale as well
+and start MaxScale as well
 
 ## Step 6 - Test the filter and check collected data