style(readme): correct lint errors

README.md

@@ -8,9 +8,7 @@ automatically load dotenv files based on `NODE_ENV`
 [![test][test-img]][test-url]
 [![semantic][semantic-img]][semantic-url]
 
-<img src="https://raw.githubusercontent.com/motdotla/dotenv/master/dotenv.png" alt="dotenv" align="right" />
-
-> `autoenv` uses [`dotenv`][] to **automatically** load environment variables from a [compatible][] `.env` file into [`process.env`][].
+`autoenv` uses [`dotenv`][] to **automatically** load environment variables from a [compatible][] `.env` file into [`process.env`][].
 
 ## Install
 
@@ -22,27 +20,29 @@ npm install --only=production --save autoenv
 
 Create a default `.env` file in the root directory of your project.
 
-``` dosini
+``` ini
 DB_HOST=localhost
 DB_USER=root
 DB_PASS=s1mpl3
 ```
 
 Create additional `.env.xyz` files matching as many environment variants you want:
 
-    my_project/
-    ├── .env
-    ├── .env.development
-    ├── .env.staging
-    └── .env.production
+``` plain
+my_project/
+├── .env
+├── .env.development
+├── .env.staging
+└── .env.production
+```
 
 The **default** `.env` will always be loaded, if a matching `.env.${NODE_ENV}` file is present, it will be loaded and overrides the values in `.env`
 
 ## Usage
 
 As early as possible in your application, require and configure dotenv.
 
-``` javascript
+``` js
 require('autoenv')
 ```
 
@@ -69,7 +69,7 @@ That's it.
 
 `process.env` now has the keys and values you defined in your `.env` file.
 
-``` javascript
+``` js
 const db = require('db')
 db.connect({
   host: process.env.DB_HOST,

docs/README.md

@@ -1,7 +1,4 @@
-
-<img src="https://raw.githubusercontent.com/motdotla/dotenv/master/dotenv.png" alt="dotenv" align="right" />
-
-> `autoenv` uses [`dotenv`][dotenv] to **automatically** load environment variables from a [compatible](#config) `.env` file into [`process.env`][process-env].
+`autoenv` uses [`dotenv`][dotenv] to **automatically** load environment variables from a [compatible](#config) `.env` file into [`process.env`][process-env].
 
 ## Install
 
@@ -13,15 +10,15 @@ npm install --only=production --save autoenv
 
 Create a default `.env` file in the root directory of your project.
 
-```dosini
+```ini
 DB_HOST=localhost
 DB_USER=root
 DB_PASS=s1mpl3
 ```
 
 Create additional `.env.xyz` files matching as many environment variants you want:
 
-```
+```plain
 my_project/
 ├── .env
 ├── .env.development
@@ -35,7 +32,7 @@ The **default** `.env` will always be loaded, if a matching `.env.${NODE_ENV}` f
 
 As early as possible in your application, require and configure dotenv.
 
-```javascript
+```js
 require('autoenv')
 ```
 
@@ -54,7 +51,6 @@ $ node index.js
 
 You can use the `--require` (`-r`) command line option to preload autoenv. By doing this, you do not need to `require` in your application code.
 
-
 ```bash
 $ node -r autoenv index.js
 ```
@@ -63,7 +59,7 @@ That's it.
 
 `process.env` now has the keys and values you defined in your `.env` file.
 
-```javascript
+```js
 const db = require('db')
 db.connect({
   host: process.env.DB_HOST,