@videojs/react 10.0.0-beta.24 → 10.0.0-beta.26

package/docs/concepts/why-videojs.md

@@ -34,7 +34,7 @@ Video.js aims to handle this all out of the box. (Though some features are still
 
 ### Streaming formats and sources
 
-Behind features like adaptive bitrate and quality selection are video formats like HLS or DASH — videos broken into segments that can be selected according to bandwidth and preferences. Not every browser supports HLS, and DASH support is even more limited. Video.js closes the gap so the same `src` works everywhere.
+Behind features like adaptive bitrate and quality selection are video formats like HLS or DASH – videos broken into segments that can be selected according to bandwidth and preferences. Not every browser supports HLS, and DASH support is even more limited. Video.js closes the gap so the same `src` works everywhere.
 
 Of course, your video might not be coming from a `src` like that. It might be provided by a service. However, services like YouTube, Vimeo, and Mux each speak their own API. Switching from a self-hosted file to a hosted service shouldn’t mean switching players. Video.js abstracts the source so you can change where the video comes from without rewriting the surrounding code.
 

package/docs/how-to/build-with-ai.md

@@ -12,13 +12,13 @@ AI tools might not know the Video.js API out of the box. You need to give them d
 
 Every doc page is available as markdown, so you can provide your model with focused content instead of HTML. Three ways to get it:
 
-1.  **Copy button** : each page has a “Copy Markdown” button in its header. Grab the pages relevant to your task and paste them in. The button looks something like this…
+1.  **Copy button**: each page has a “Copy Markdown” button in its header. Grab the pages relevant to your task and paste them in. The button looks something like this…
     
-2.  **`Accept: text/markdown` header** : AI tools that send this header when fetching a Video.js doc URL will receive markdown instead of HTML.
+2.  **`Accept: text/markdown` header**: AI tools that send this header when fetching a Video.js doc URL will receive markdown instead of HTML.
     
     ![Fetching a doc URL returns 188.7KB of HTML; fetching the same URL with .md returns 3.4KB of markdown](/.netlify/images?url=_astro%2Fmarkdown-negotiation.2TkZPhhc.png&w=1470&h=680)
     
-3.  **Add `.md` to any URL** : append `.md` to any doc URL to get its markdown directly. For example, the PlayButton reference is available at [`videojs.org/docs/framework/react/reference/play-button.md`](../reference/play-button.md).
+3.  **Add `.md` to any URL**: append `.md` to any doc URL to get its markdown directly. For example, the PlayButton reference is available at [`videojs.org/docs/framework/react/reference/play-button.md`](../reference/play-button.md).
     
 
 ### llms.txt
@@ -29,10 +29,10 @@ Every doc page is available as markdown, so you can provide your model with focu
 
 How you use these resources depends on your tool:
 
-*   **Any AI chat** : copy markdown from a doc page and paste it into the conversation.
-*   **Claude Code** : reference doc URLs in your project’s [`CLAUDE.md`](https://docs.anthropic.com/en/docs/claude-code/overview) so the agent knows where to find Video.js docs when it needs them.
-*   **Cursor** : add the `llms.txt` URL via the [`@Docs`](https://docs.cursor.com/context/@-symbols/@-docs) feature for indexed search across the documentation.
-*   **Other coding agents** : reference doc URLs or `llms.txt` in your project’s [`AGENTS.md`](https://agents.md) or equivalent context file.
+*   **Any AI chat**: copy markdown from a doc page and paste it into the conversation.
+*   **Claude Code**: reference doc URLs in your project’s [`CLAUDE.md`](https://docs.anthropic.com/en/docs/claude-code/overview) so the agent knows where to find Video.js docs when it needs them.
+*   **Cursor**: add the `llms.txt` URL via the [`@Docs`](https://docs.cursor.com/context/@-symbols/@-docs) feature for indexed search across the documentation.
+*   **Other coding agents**: reference doc URLs or `llms.txt` in your project’s [`AGENTS.md`](https://agents.md) or equivalent context file.
 
 ## What’s next for AI and Video.js
 

package/docs/how-to/build-your-own-component.md

@@ -8,9 +8,9 @@ Custom components subscribe to player state and dispatch actions, like built-in
 
 Before building from scratch, check if an existing approach covers your use case:
 
-*   **Change what a control renders** : use the `render` prop on any built-in component. See [UI components](../concepts/ui-components.md).
-*   **Restyle a control** : use CSS custom properties and data attributes. See [UI components](../concepts/ui-components.md).
-*   **Rearrange or remove controls** : eject a skin and modify it. See [Customize skins](./customize-skins.md).
+*   **Change what a control renders**: use the `render` prop on any built-in component. See [UI components](../concepts/ui-components.md).
+*   **Restyle a control**: use CSS custom properties and data attributes. See [UI components](../concepts/ui-components.md).
+*   **Rearrange or remove controls**: eject a skin and modify it. See [Customize skins](./customize-skins.md).
 
 Build a custom component when you need new behavior, a new state display, or integration with an external system.