From 94c64bef727a6f81317f0473d379a133e9d35ef4 Mon Sep 17 00:00:00 2001
From: Nathaniel Sabanski <sabanski.n@gmail.com>
Date: Sat, 30 Nov 2024 05:49:03 -0800
Subject: [PATCH] Added more notes to Tailwind comparison.

---
 README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index c87898c..38435f5 100644
--- a/README.md
+++ b/README.md
@@ -47,9 +47,10 @@ Or, 🌐 CDN: `<script src="https://cdn.jsdelivr.net/gh/gnat/css-scope-inline@ma
 
 Use whatever you'd like, but there's a few advantages with this approach over Tailwind, Twind, UnoCSS:
 
-* No [repeat styles](https://tailwindcss.com/docs/reusing-styles) on child elements (..no [@apply](https://tailwindcss.com/docs/reusing-styles#extracting-classes-with-apply), no `[&>thing]` on each style).
-* No endless visual noise on every `<div>`. Use a local `<style>` per group.
-* No difference in syntax between local and global styles. Universal CSS.
+* No [repeated styles](https://tailwindcss.com/docs/reusing-styles) on child elements (..no [@apply](https://tailwindcss.com/docs/reusing-styles#extracting-classes-with-apply), no `[&>thing]` on each style).
+* No repeated prefixes for media queries, hover, focus, etc.
+* No visual noise on every `<div>`. Use a local `<style>` per group.
+* Share syntax between local and external styles. It's just CSS.
 * Regain your "inspect, play with styles, paste" workflow in your web browser!
 * No suffering from lost syntax highlighting on properties and units.
 * No high risk of eventually requiring a build step.