diff --git a/Documentation/Changelog.md b/Documentation/Changelog.md
index 4645b3876..de8f69942 100644
--- a/Documentation/Changelog.md
+++ b/Documentation/Changelog.md
@@ -2,6 +2,9 @@
 
 ## MariaDB MaxScale 2.3
 
+* Runtime Configuration of the Cache
+* User Specified Syslog Facility and Level for Authentication Errors
+
 For more details, please refer to:
 
 * [MariaDB MaxScale 2.3.0 Release Notes](Release-Notes/MaxScale-2.3.0-Release-Notes.md)
diff --git a/Documentation/Getting-Started/Configuration-Guide.md b/Documentation/Getting-Started/Configuration-Guide.md
index ebd6943fc..148f311e7 100644
--- a/Documentation/Getting-Started/Configuration-Guide.md
+++ b/Documentation/Getting-Started/Configuration-Guide.md
@@ -825,7 +825,7 @@ The default facility is `LOG_USER` and the default level is `LOG_WARNING`.
 
 The available events are:
 
-#### 'authentication_failure'
+##### 'authentication_failure'
 
 This event occurs when there is an authentication failure.
 ```
diff --git a/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md
index 56fe43eee..dec626e23 100644
--- a/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md
+++ b/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md
@@ -51,10 +51,18 @@ API that provides the same information in a more easy to process format.
 ## New Features
 
 ### Runtime Configuration of the Cache
+
 With the variable `@maxscale.cache.enabled` it is now possible for a
 client to specify whether the cache should be used. Please see the
 [Cache](../Filters/Cache.md) documentation for details.
 
+### User Specified Syslog Facility and Level for Authentication Errors
+
+It is now possible for the end user to specify the syslog facility and level
+for authentication errors. Please see
+[the configuration guide](../Getting-Started/Configuration-Guide.md#events)
+for details.
+
 ## Bug fixes
 
 [Here is a list of bugs fixed in MaxScale 2.3.0.](https://jira.mariadb.org/issues/?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%202.3.0)