diff --git a/Documentation/Release-Notes/MaxScale-1.2.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.2.0-Release-Notes.md
index de4b7a461..c1252a932 100644
--- a/Documentation/Release-Notes/MaxScale-1.2.0-Release-Notes.md
+++ b/Documentation/Release-Notes/MaxScale-1.2.0-Release-Notes.md
@@ -34,31 +34,30 @@ Now you can configure MaxScale monitor module to automatically launch a script w
 
 Here is a list of bugs fixed since the release of MaxScale 1.1.1.
 
-| Key | Summary | 
-| --- | -------- | 
-| [MXS-24](https://mariadb.atlassian.net/browse/MXS-24) | bugzillaId-604: Module load path documentation issues ... | 
-| [MXS-40](https://mariadb.atlassian.net/browse/MXS-40) | Display logged in users | 
-| [MXS-113](https://mariadb.atlassian.net/browse/MXS-113) | MaxScale seems to fail if built against MariaDB 10.0 libraries | 
-| [MXS-116](https://mariadb.atlassian.net/browse/MXS-116) | Do not run maxscale as root. | 
-| [MXS-117](https://mariadb.atlassian.net/browse/MXS-117) | Allow configuration of the log file directory | 
-| [MXS-125](https://mariadb.atlassian.net/browse/MXS-125) | inconsistency in maxkeys/maxpassword output and parameters | 
-| [MXS-128](https://mariadb.atlassian.net/browse/MXS-128) | cyclic dependency utils -> log_manager -> utils | 
-| [MXS-136](https://mariadb.atlassian.net/browse/MXS-136) | Check for MaxScale replication heartbeat table existence before creating | 
-| [MXS-137](https://mariadb.atlassian.net/browse/MXS-137) | cannot get sql for queries with length >= 0x80 | 
-| [MXS-139](https://mariadb.atlassian.net/browse/MXS-139) | Schemarouter authentication for wildcard grants fails without optimize_wildcard | 
-| [MXS-140](https://mariadb.atlassian.net/browse/MXS-140) | strip_db_esc does not work without auth_all_servers | 
-| [MXS-162](https://mariadb.atlassian.net/browse/MXS-162) | Fix Incorrect info in Configuration Guide |
-| [MXS-165](https://mariadb.atlassian.net/browse/MXS-165) | Concurrency issue while incrementing sessions in qlafilter | 
-| [MXS-166](https://mariadb.atlassian.net/browse/MXS-166) | Memory leak when creating a new event | 
-| [MXS-171](https://mariadb.atlassian.net/browse/MXS-171) | Allow reads on master for readwritesplit | 
-| [MXS-176](https://mariadb.atlassian.net/browse/MXS-176) | Missing dependencies in documentation | 
-| [MXS-180](https://mariadb.atlassian.net/browse/MXS-180) | MariaDB10 binlog router compatibilty |
-| [MXS-181](https://mariadb.atlassian.net/browse/MXS-181) | Poor performance on TCP connection due to Nagle's algoritm | 
-| [MXS-182](https://mariadb.atlassian.net/browse/MXS-182) | SHOW SLAVE STATUS and maxadmin "show services" for binlog router needs updated when used with MariaDB 10 Master | 
-| [MXS-212](https://mariadb.atlassian.net/browse/MXS-212) | Stopped services accept connections | 
-| [MXS-225](https://mariadb.atlassian.net/browse/MXS-225) | RPM Debug build packages have no debugging symbols | 
-| [MXS-227](https://mariadb.atlassian.net/browse/MXS-227) | Memory leak in Galera Monitor | 
-| [MXS-244](https://mariadb.atlassian.net/browse/MXS-244) | Memory leak when using prepared statements without arguments | 
+ * [MXS-24](https://mariadb.atlassian.net/browse/MXS-24):  bugzillaId-604: Module load path documentation issues ...  
+ * [MXS-40](https://mariadb.atlassian.net/browse/MXS-40):  Display logged in users  
+ * [MXS-113](https://mariadb.atlassian.net/browse/MXS-113):  MaxScale seems to fail if built against MariaDB 10.0 libraries  
+ * [MXS-116](https://mariadb.atlassian.net/browse/MXS-116):  Do not run maxscale as root.  
+ * [MXS-117](https://mariadb.atlassian.net/browse/MXS-117):  Allow configuration of the log file directory  
+ * [MXS-125](https://mariadb.atlassian.net/browse/MXS-125):  inconsistency in maxkeys/maxpassword output and parameters  
+ * [MXS-128](https://mariadb.atlassian.net/browse/MXS-128):  cyclic dependency utils -> log_manager -> utils  
+ * [MXS-136](https://mariadb.atlassian.net/browse/MXS-136):  Check for MaxScale replication heartbeat table existence before creating  
+ * [MXS-137](https://mariadb.atlassian.net/browse/MXS-137):  cannot get sql for queries with length >= 0x80  
+ * [MXS-139](https://mariadb.atlassian.net/browse/MXS-139):  Schemarouter authentication for wildcard grants fails without optimize_wildcard  
+ * [MXS-140](https://mariadb.atlassian.net/browse/MXS-140):  strip_db_esc does not work without auth_all_servers  
+ * [MXS-162](https://mariadb.atlassian.net/browse/MXS-162):  Fix Incorrect info in Configuration Guide 
+ * [MXS-165](https://mariadb.atlassian.net/browse/MXS-165):  Concurrency issue while incrementing sessions in qlafilter  
+ * [MXS-166](https://mariadb.atlassian.net/browse/MXS-166):  Memory leak when creating a new event  
+ * [MXS-171](https://mariadb.atlassian.net/browse/MXS-171):  Allow reads on master for readwritesplit  
+ * [MXS-176](https://mariadb.atlassian.net/browse/MXS-176):  Missing dependencies in documentation  
+ * [MXS-179](https://mariadb.atlassian.net/browse/MXS-179):  Keep configuration  changes in synch across MaxScale Mate Nodes  
+ * [MXS-180](https://mariadb.atlassian.net/browse/MXS-180):  MariaDB10 binlog router compatibilty 
+ * [MXS-181](https://mariadb.atlassian.net/browse/MXS-181):  Poor performance on TCP connection due to Nagle's algoritm  
+ * [MXS-182](https://mariadb.atlassian.net/browse/MXS-182):  SHOW SLAVE STATUS and maxadmin "show services" for binlog router needs updated when used with MariaDB 10 Master  
+ * [MXS-212](https://mariadb.atlassian.net/browse/MXS-212):  Stopped services accept connections  
+ * [MXS-225](https://mariadb.atlassian.net/browse/MXS-225):  RPM Debug build packages have no debugging symbols  
+ * [MXS-227](https://mariadb.atlassian.net/browse/MXS-227):  Memory leak in Galera Monitor  
+ * [MXS-244](https://mariadb.atlassian.net/browse/MXS-244):  Memory leak when using prepared statements without arguments 
 
 ## Known Issues and Limitations