Update README.md

README.md

@@ -20,12 +20,11 @@
     - [Publish the Config and Migrations](#publish-the-config-and-migrations)
     - [Migrate the Database](#migrate-the-database)
 - [Usage](#usage)
-    - [Generating Secure Codes](#denerating-secure-codess)
+    - [Generating Secure Codes](#generating-secure-codess)
         - [Quick Start](#quick-start)
         - [Validation](#validation)
-        - [Defining your Custom Validation Class](#defining-your-custom-validation-classs)
+        - [Defining your Custom Validation Class](#defining-your-custom-validation-class)
         - [Customizing Configs](#customizing-configs)
-        - [Using Custom Rules](#using-custom-rules)
         - [Facade](#facade)
     - [Using the Secure code Manager](#using-the-secure-code-manager)
         - [Allocating a Code](#allocating-a-code)
@@ -223,6 +222,15 @@ if ($success) {
 
 ```
 
+#### Config Validation
+By default, the values defined in the ``` secure-code.php ``` config file are validated as the library contains
+a validator that is used to ensure that your values are safe to use. To disable the config validation, you can set the
+following option in the config:
+
+```
+'validate_config' => false,
+```
+
 #### Custom Database Connection
 
 By default, Secure code will use your application's default database connection. But there may be times that you'd like to use a different connection. For example, you might be building a multi-tenant application that uses a separate connection for each tenant, and you may want to store the Secure codes in a central database.