Fix missing word.

Author: taylorotwell

configuration.md

@@ -97,7 +97,7 @@ When using environment configuration, you may want to "append" environment [serv
 <a name="protecting-sensitive-configuration"></a>
 ## Protecting Sensitive Configuration
 
-For "real" applications, it is advisable to keep all of your sensitive configuration out of your configuration files. Things such database passwords, Stripe API keys, and encryption keys should be kept out of your configuration files whenever possible. So, where should we place them? Thankfully, Laravel provides a very simple solution to protecting these types of configuration items using "dot" files.
+For "real" applications, it is advisable to keep all of your sensitive configuration out of your configuration files. Things such as database passwords, Stripe API keys, and encryption keys should be kept out of your configuration files whenever possible. So, where should we place them? Thankfully, Laravel provides a very simple solution to protecting these types of configuration items using "dot" files.
 
 First, [configure your application](/docs/configuration#environment-configuration) to recognize your machine as being in the `local` environment. Next, create a `.env.local.php` file within the root of your project. The root of your project is typically where your `composer.json` file lives. The `.env.local.php` should return an array of key-value pairs, much like a typical Laravel configuration file: