docs(site): note framework-native architecture extends to new frameworks

Per @sampotts review on #1526.

https://claude.ai/code/session_01Uv795VrAR51b65fKTTn8gT

Author: claude

site/src/content/docs/concepts/why-videojs.mdx

@@ -51,7 +51,7 @@ Pre-built feature bundles are still there if you'd rather not assemble the list
 
 ### Framework-native
 
-Many player libraries wrap a single web component for every framework. That works, until you reach the seams: refs you can't pass through, state that doesn't reconcile, prop names that aren't quite React or HTML. Video.js v10 ships idiomatic APIs in each framework: React components and hooks for React, custom elements and controllers for HTML. The player feels like the rest of your app.
+Many player libraries wrap a single web component for every framework. That works, until you reach the seams: refs you can't pass through, state that doesn't reconcile, prop names that aren't quite React or HTML. Video.js v10 ships idiomatic APIs in each framework: React components and hooks for React, custom elements and controllers for HTML. The player feels like the rest of your app, and the same approach extends to new frameworks as we add them.
 
 <TabsRoot client:idle>
   <TabsList client:idle label="Framework-native APIs">