Clarify Vanilla Emotion auto-prefixing capabilities in documentation (#…

…1662)

* Update docs/introduction.mdx to be more clear with auto-prefixing support

* Mention style prop again

* Re-order bullet points in CSS prop usage

docs/introduction.mdx

@@ -20,9 +20,9 @@ The [emotion](https://www.npmjs.com/package/emotion) package is framework agnost
 
 - Requires no additional setup, babel plugin, or other config changes.
 
-- Works in situations where configuration is restricted or not possible such as with [Create React App](https://facebook.github.io/create-react-app)
+- Has support for auto vendor-prefixing, nested selectors, and media queries.
 
-- The `css` prop is not used or needed.
+- Works in situations where configuration is restricted or not possible such as with [Create React App](https://facebook.github.io/create-react-app)
 
 - You simply prefer to use the `css` function to generate class names and `cx` to compose them.
 
@@ -61,9 +61,8 @@ The ["@emotion/core"](https://www.npmjs.com/package/@emotion/core) package requi
 
 - Best when using React with a build environment that can be configured.
 
-- CSS prop support
-
-  - Similar to the `style` prop but adds support for nested selectors, media queries, and auto-prefixing.
+- `css` prop support
+  - Similar to the `style` prop, but also has support for auto vendor-prefixing, nested selectors, and media queries.
 
   - Allows developers to skip the `styled` API abstraction and style components and elements directly.