Typo

Author: adamwathan

src/pages/building-react-and-vue-support-for-tailwind-ui/index.mdx

@@ -217,7 +217,7 @@ To me, something about doing all of this for people felt like going too far, at
 
 I wrestled with it for a long time, but ultimately decided that right now we were trying to solve two main problems:
 
-1. **Give people code using the syntax they actually need**, like giving React users JSX instead of HTML so they don't have to manually convert things like `for` to `labelFor`.
+1. **Give people code using the syntax they actually need**, like giving React users JSX instead of HTML so they don't have to manually convert things like `for` to `htmlFor`.
 2. **Make the interactive elements work out of the box**, so dropdowns, mobile menus, toggles, and everything else was ready to go, instead of having to write all of that boilerplate JS yourself.
 
 I decided that the right solution was to focus on solving those problems, and be careful not to do anything that would turn Tailwind UI into a different product.