Merge pull request #1628 from tlvince/refactor/no-process-env

Docs: add newline to no-process-env (fixes #1627)
eslint · Jan 7, 2015 · 1c175e5 · 1c175e5
2 parents 6c7b464 + 8645915
commit 1c175e5
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/docs/rules/no-process-env.md b/docs/rules/no-process-env.md
@@ -19,18 +19,18 @@ The following patterns are considered okay and do not cause warnings:
 
 ```js
 var config = require("./config");
-  
-if(config.env === "development") {    
+
+if(config.env === "development") {
     //...
 }
 ```
 
 ## When Not To Use It
 
-It should be not used in your configuration/settings file where `process.env` is used to assign values to parameters to be accessed throughout the project. 
+It should be not used in your configuration/settings file where `process.env` is used to assign values to parameters to be accessed throughout the project.
 
 
 ## Further Reading
 
 * [How to store Node.js deployment settings/configuration files? - Stack Overflow](http://stackoverflow.com/questions/5869216/how-to-store-node-js-deployment-settings-configuration-files)
-* [Storing Node.js application config data - Ben Hall's blog](http://blog.benhall.me.uk/2012/02/storing-application-config-data-in/)
+* [Storing Node.js application config data - Ben Hall's blog](http://blog.benhall.me.uk/2012/02/storing-application-config-data-in/)