tailwind-ctp-intellisense @master -
refs -
log -
-
https://git.jolheiser.com/tailwind-ctp-intellisense.git
diff --git a/packages/tailwindcss-intellisense/README.md b/packages/tailwindcss-intellisense/README.md
index 075e996a09c9d8da36f00c7783b8c672ea7ddb86..befa11d7efe99140a21308e9add02c7538e3468d 100644
--- a/packages/tailwindcss-intellisense/README.md
+++ b/packages/tailwindcss-intellisense/README.md
@@ -32,8 +32,24 @@ ### CSS Syntax Highlighting
Provides syntax definitions so that Tailwind features are highlighted correctly.
+## Recommended VS Code Settings
+
+VS Code has built-it CSS validation which may display errors when using Tailwind-specific syntax, such as `@apply`. You can disable this with the `css.validate` setting:
+
+```
+In order for the extension to activate you must have [`tailwindcss` installed](https://tailwindcss.com/docs/installation/#1-install-tailwind-via-npm) and a [Tailwind config file](https://tailwindcss.com/docs/installation/#3-create-your-tailwind-config-file-optional) named `tailwind.config.js` or `tailwind.js` in your workspace.
<img src="https://raw.githubusercontent.com/bradlc/vscode-tailwindcss/master/packages/tailwindcss-intellisense/.github/banner-dark.png" alt="" />
-Intelligent suggestions for class names, as well as [CSS functions and directives](https://tailwindcss.com/docs/functions-and-directives/).
+```
+
+By default VS Code will not trigger completions when editing "string" content, for example within HTML attribute values. Updating the `editor.quickSuggestions` setting may improve your experience, particularly when editing Tailwind classes in HTML files:
+
+```
+"editor.quickSuggestions": {
+ "strings": true
+}
+```
+
+## Extension Settings
### `tailwindCSS.includeLanguages`