diff --git a/docs/docs/what-you-dont-need-plugins-for.md b/docs/docs/what-you-dont-need-plugins-for.md
index 49f7bef355771..4c5b9503d8b88 100644
--- a/docs/docs/what-you-dont-need-plugins-for.md
+++ b/docs/docs/what-you-dont-need-plugins-for.md
@@ -7,7 +7,6 @@ Most third-party functionality you want to add to your website will follow stand
 Some examples:
 
 - Importing JavaScript packages that provide general functionality, such as `lodash` or `axios`
-- Using React components or component libraries you want to include in your UI, such as `Ant Design`, `Material UI`, or the typeahead from your component library.
 - 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.