docs: minor markdown improvements

Author: chrisbbreuer

docs/examples/auto-generation.md

@@ -68,7 +68,7 @@ This makes it easy for other developers to know which environment variables they
 
 When you run your Vite dev server with the `updateGitignore: true` option, the plugin will automatically add `.env.keys` to your `.gitignore` file if it's not already there:
 
-```
+```bash
 # .gitignore
 node_modules
 dist

docs/examples/nextjs-convention.md

@@ -118,7 +118,7 @@ console.log('Custom Setting:', process.env.CUSTOM_SETTING) // From .env.local
 
 When using the Next.js convention, it's recommended to add the following to your `.gitignore` file:
 
-```
+```bash
 # .gitignore
 .env*.local
 .env.keys

docs/intro.md

@@ -1,4 +1,4 @@
-<p align="center"><img src="https://github.com/stacksjs/vite-plugin-dotenvx/blob/main/.github/art/cover.jpg?raw=true" alt="Social Card of this repo"></p>
+![Social Card of this repo](https://github.com/stacksjs/vite-plugin-dotenvx/blob/main/.github/art/cover.jpg?raw=true)
 
 # Introduction
 

docs/usage.md

@@ -60,7 +60,7 @@ dotenvx encrypt
 
 This will encrypt your .env file and create a `.env.keys` file with the encryption keys. The encrypted .env file will look something like this:
 
-```
+```bash
 #/-------------------[DOTENV_PUBLIC_KEY]--------------------/
 #/            public-key encryption for .env files          /
 #/       [how it works](https://dotenvx.com/encryption)     /