Cleaned up documentation

Fixed spelling mistakes, cleaned up formatting and added missing links.

Filters/Named-Server-Filter.md

@@ -1,10 +1,10 @@
-Named Server Filter
+# Named Server Filter
 
-# Overview
+## Overview
 
 The **namedserverfilter** is a filter module for MaxScale which is able to route queries to servers based on regular expression matches.
 
-# Configuration
+## Configuration
 
 The configuration block for the Named Server filter requires the minimal filter options in it’s section within the maxscale.cnf file, stored in /etc/maxscale.cnf.
 

Filters/Query-Log-All-Filter.md

@@ -107,3 +107,7 @@ filters=ProductsSelectLogger
 ```
 
 The  result  of  then  putting  this  filter  into  the  service  used  by  the  application  would  be  a  log  file  of  all  select  queries  that  mentioned  the  table  but  did  not  mention  the  PRODUCT_ID  primary  key  in  the  predicates  for  the  query.
+Executing `SELECT * FROM PRODUCTS` would log the following into `/var/logs/qla/SelectProducts`:
+```
+07:12:56.324 7/01/2016, SELECT * FROM PRODUCTS
+```

Filters/Regex-Filter.md

@@ -1,6 +1,6 @@
-Regex Filter
+# Regex Filter
 
-# Overview
+## Overview
 
 The regex filter is a filter module for MaxScale that is able to rewrite query content using regular expression matches and text substitution. It uses the PCRE2 syntax which differs from the POSIX regular expressions used in MaxScale versions prior to 1.3.0.
 
@@ -8,7 +8,7 @@ For all details about the PCRE2 syntax, please read the [PCRE2 syntax documentat
 
 Please note that the PCRE2 library uses a different syntax to refer to capture groups in the replacement string. The main difference is the usage of the dollar character instead of the backslash character for references e.g. `$1` instead of `\1`. For more details about the replacement string differences, please read the [Creating a new string with substitutions](http://www.pcre.org/current/doc/html/pcre2api.html#SEC34) chapter in the PCRE2 manual.
 
-# Configuration
+## Configuration
 
 The configuration block for the Regex filter requires the minimal filter options in it’s section within the maxscale.cnf file, stored in /etc/maxscale.cnf.
 
@@ -80,7 +80,12 @@ log_file=/tmp/regexfilter.log
 
 ### `log_trace`
 
-The optional log_trace parameter toggles the logging of non-matching and matching queries with their replacements into the trace log file. This is the preferred method of diagnosing the matching of queries since the trace log can be disabled mid-session if such a need rises.
+The optional log_trace parameter toggles the logging of non-matching and
+matching queries with their replacements into the log file on the *info* level.
+This is the preferred method of diagnosing the matching of queries since the
+log level can be changed at runtime. For more details about logging levels and
+session specific logging, please read the [Configuration Guide](../Getting-Started/Configuration-Guide.md#global-settings)
+and the [MaxAdmin](../Reference/MaxAdmin.md#change-maxscale-logging-options) documentation on changing the logging levels.
 
 ```
 log_trace=true

Filters/Tee-Filter.md

@@ -1,10 +1,10 @@
-TEE Filter
+# Tee Filter
 
-# Overview
+## Overview
 
 The tee filter is a filter module for MaxScale is a "plumbing" fitting in the MaxScale filter toolkit. It can be used in a filter pipeline of a service to make a copy of requests from the client and dispatch a copy of the request to another service within MaxScale. 
 
-# Configuration
+## Configuration
 
 The configuration block for the TEE filter requires the minimal filter parameters in it’s section within the maxscale.cnf file, stored in /etc/maxscale.cnf, that defines the filter to load and the service to send the duplicates to. Currently the tee filter does not support multi-statements.
 

Filters/Top-N-Filter.md

@@ -1,10 +1,10 @@
-Top Filter
+# Top Filter
 
-# Overview
+## Overview
 
 The top filter is a filter module for MaxScale that monitors every SQL statement that passes through the filter. It measures the duration of that statement, the time between the statement being sent and the first result being returned. The top N times are kept, along with the SQL text itself and a list sorted on the execution times of the query is written to a file upon closure of the client session.
 
-# Configuration
+## Configuration
 
 The configuration block for the TOP filter requires the minimal filter options in it’s section within the maxscale.cnf file, stored in /etc/maxscale.cnf.