updated readme

README.md

@@ -7,7 +7,7 @@
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![Twitter Follow](https://img.shields.io/twitter/follow/imagekitio?label=Follow&style=social)](https://twitter.com/ImagekitIo)
 
-The plugin seamlessly integrates with your Netlify site, delivering high-quality optimized images with the help of [ImageKit](https://imagekit.io/).
+The plugin seamlessly integrates with your Netlify site, delivering high-quality optimized images using [ImageKit](https://imagekit.io/).
 
 - [Prerequisites](#prerequisites)
 - [Setup ImageKit Netlify plugin](#setup-imagekit-netlify-plugin)
@@ -20,7 +20,7 @@ The plugin seamlessly integrates with your Netlify site, delivering high-quality
 
 ## Prerequisites
 
-Before starting, you need to have an ImageKit account to use the plugin. Then, you must set up a URL endpoint pointing to a web proxy origin as described below.
+Before starting, you need an ImageKit account to use the plugin. Then, you must set up a URL endpoint pointing to a web proxy origin, as described below.
 
 - Add web proxy origin by following [these steps](https://imagekit.io/docs/integration/web-proxy).
 
@@ -34,7 +34,7 @@ https://ik.imagekit.io/{imagekit_id}/{origin_identifier}
 
 ## Setup ImageKit Netlify plugin
 
-Currently you can integrate plugin with the help of [file-based installation](https://docs.netlify.com/integrations/build-plugins/#file-based-installation).
+Currently, you can integrate the plugin with the help of [file-based installation](https://docs.netlify.com/integrations/build-plugins/#file-based-installation).
 
 ### File-based installation
 
@@ -75,13 +75,13 @@ The environment variable can be set in multiple ways through [Netlify UI, Netlif
  It specifies the paths, relative to the [publish directory](https://docs.netlify.com/configure-builds/overview/#set-the-publish-directory), where images are stored and should be served through the ImageKit server. If images are stored in multiple directories, you can provide an array to `imagesPath`, and all such images will be redirected to ImageKit. If no value is provided, the default value is set to images.
 
  > **Publish Directory:**
- >When deploying a front-end project on Netlify, the deployment is done after running the build command, which generates a folder containing the build output. The name of this folder can vary depending on the framework being used. For example, in a `React` project, the folder might be named `build` or `dist`. This folder's path must be specified as the publish directory in Netlify.
+ >When deploying a front-end project on Netlify, the deployment is done after running the build command, which generates a folder containing the build output. The name of this folder can vary depending on the framework being used. For example, the folder might be named `build` or `dist` in a `React` project. This folder's path must be specified as the publish directory in Netlify.
  >
  >Find a comprehensive list of build commands and publish directories for various frameworks on Netlify [here](https://docs.netlify.com/frameworks/).
 
  <br>
 
- In the last it is needed to add `netlify-plugin-imagekit` as a dev dependency as mentioned [here](https://docs.netlify.com/integrations/build-plugins/#add-dependency).
+ Lastly, add `netlify-plugin-imagekit` as a dev dependency as mentioned [here](https://docs.netlify.com/integrations/build-plugins/#add-dependency).
 
 ```
 // using npm
@@ -92,20 +92,20 @@ yarn add --dev netlify-plugin-imagekit
 ```
 
 ## How does it work?
-After following above steps, the ImageKit plugin will work out of the box. Internally it uses the below mechanism to deliver highly optimize image. 
+After following above steps, the ImageKit plugin will work out of the box. Internally it uses the below mechanism to deliver highly optimized images. 
 
-### 1. Modify URLs in production ready HTML files
+### 1. Modify URLs in production-ready HTML files
 This is useful in scenarios where proper HTML files are generated after the build process. For these frameworks, the plugin taps into the `onPostBuild` hook, using `jsdom` to create a node-based representation of the DOM for each output HTML file. It then walks through each node, and upon finding an img or picture tag, it replaces the `src` or `srcset` path with an ImageKit URL.
 
-While this approach works well for many situations, especially during the initial page load, it fails when using a framework with client-side routing or features that alter the DOM, or that does not generate HTML files on build, such as `React`. This necessitates the use of the mechanism described below.
+While this approach works well for many situations, especially during the initial page load, it fails when using a framework with client-side routing or features that alter the DOM or that does not generate HTML files on build, such as `React`. This necessitates the use of the mechanism described below.
 
 ### 2. Redirect assets through the ImageKit Server
 
 In this approach, all asset paths relative to the publish directory as `imagesPath` is specified. Then, using the redirect feature of [Netlify Redirects and rewrites](https://docs.netlify.com/routing/redirects/), we redirect the existing image URLs from the Netlify server to the ImageKit server. The ImageKit server fetches the original image, optimizes it, and then serves it back to the end user.
 
 ## Limitations
 
-- When external or third-party URLs are used instead of static assets in frameworks like `React` that do not generate HTML files after the build process or mutate the DOM on the client side, these URLs will not be replaced by ImageKit URLs.
+- When external or third-party URLs are used instead of static assets in frameworks like `React` that do not generate HTML files after the build process or mutate the DOM on the client side, these URLs will not be replaced by ImageKit URLs. To address this issue, you can use the ImageKit client-side SDK, [imagekit-react](https://github.com/imagekit-developer/imagekit-react?tab=readme-ov-file#quick-examples) to serve third-party URLs through the ImageKit server.
 
 - Another limitation is that when base64 URLs are used for images, no separate request is made to the backend to fetch the images. As a result, these images cannot be replaced.