Chore(Doc): What-you-dont-need-plugins-for: Grammar change to aid readability (#20503)

* docs(What-you-dont-need-plugins-for): Grammar change to aid readability. Also added hyperlink to styled-component

* docs(What-you-dont-need-plugins-for): Grammar change to aid readability

Author: Ekwuno

docs/docs/what-you-dont-need-plugins-for.md

@@ -9,4 +9,6 @@ Some examples:
 - Importing JavaScript packages that provide general functionality, such as `lodash` or `axios`
 - Integrating visualization libraries, such as `Highcharts` or `d3`.
 
-As a general rule, you may use _any_ npm package you might use without Gatsby, with Gatsby. What plugins offer is a prepackaged integration into the core Gatsby APIs to save you time and energy, with minimal configuration. In the case of `Styled Components`, you could manually render the `Provider` component near the root of your application, or you could just use `gatsby-plugin-styled-components` which takes care of this step for you in addition to any other difficulties you may run into configuring Styled Components to work with server side rendering.
+As a general rule, any npm package you might use while working on another JavaScript or React application can also be used ,with a Gatsby application. What plugins offer is a prepackaged integration into the core Gatsby APIs to save you time and energy, with minimal configuration.
+
+A good use case would be using `Styled Components`, you could manually render the `Provider` component near the root of your application, or you could use [gatsby-plugin-styled-components ](https://www.gatsbyjs.org/packages/gatsby-plugin-styled-components/) which takes care of this step for you in addition to any other difficulties when configuring Styled Components to work with server-side rendering.