readme styling fixes

Author: bmstefanski

README.md

@@ -11,18 +11,18 @@
 
 <br />
 
-## Motivation
+## ❔ Motivation
 
-This library makes it possible to use `next/image` with dynamic domains. If you work with external providers, like Facebook, Instagram, Etsy, Medium, and others, the images often have dynamic subdomains. For example, you might get the first image from `scontent-akl1-1.cdninstagram.com` and the second one from `scontent-akl3-1.cdninstagram.com`. Although adding them one by one to the config could work temporarily, it would not be reliable since they can change at any time. The whole issue can be resolved by adding a regex pattern to `next.config.js`, but unfortunately, Next.js doesn't support that.
+This library makes it possible to use `next/image` with dynamic domains. If you work with external providers, like Facebook, Instagram, Etsy, Medium, and others, the images often have dynamic subdomains. For example, you might get the first image from `scontent-akl1-1.cdninstagram.com` and the second one from `scontent-akl3-1.cdninstagram.com`. Although adding them one by one to the config could work temporarily, it would not be reliable since they can change at any time. The whole issue could be resolved by adding a regex pattern to `next.config.js`, but unfortunately, Next.js doesn't support that.
 
 If you want to follow the discussion about Next.js supporting it outside of the box, please refer to this [Discussion](https://github.com/vercel/next.js/discussions/18429) and this [Pull Request](https://github.com/vercel/next.js/pull/27345)
 
-You have to remember that (as always) there're some cons:
+You have to remember that there're some cons:
 
 - You can create a security loophole if your regex isn't strict enough
 - Since it is a proxy, it will increase bandwidth costs. But the increase will be marginal unless you're working on big scale project (i.e. mils of requests per month)
 
-## Installation
+## 🧰 Installation
 
 ```
 $ npm i --save next-image-proxy
@@ -32,7 +32,7 @@ $ npm i --save next-image-proxy
 $ yarn add next-image-proxy
 ```
 
-## Use
+## 💻 Use
 
 It is really simple to setup, you just need to add a new API route that exports one function. The name of the endpoint is up to you.
 
@@ -49,10 +49,10 @@ and now you prefix the image you want to use:
 ```tsx
 import NextImage from 'next/image'
 
-{ /* O.F.C. */ }
-return (
-  <NextImage src={`api/imageProxy?imageUrl=${originalUrl}`} />
-)
+{
+  /* O.F.C. */
+}
+return <NextImage src={`api/imageProxy?imageUrl=${originalUrl}`} />
 ```
 
 ## 🤲🏻 Contributing