Move component v-model to its own page (#2153)

Author: skirtles-code

.vitepress/config.ts

@@ -194,6 +194,7 @@ export const sidebar: ThemeConfig['sidebar'] = {
         },
         { text: 'الخاصيات', link: '/guide/components/props' },
         { text: 'الأحداث', link: '/guide/components/events' },
+        { text: 'Component v-model', link: '/guide/components/v-model' },
         {
           text: 'السمات الإحتياطية',
           link: '/guide/components/attrs'

src/api/built-in-directives.md

@@ -362,7 +362,7 @@ Create a two-way binding on a form input element or a component.
 - **See also:**
 
   - [Form Input Bindings](/guide/essentials/forms.html)
-  - [Component Events - Usage with `v-model`](/guide/components/events.html#usage-with-v-model)
+  - [Component Events - Usage with `v-model`](/guide/components/v-model.html)
 
 ## v-slot {#v-slot}
 

src/api/reactivity-utilities.md

@@ -96,7 +96,7 @@ Can be used to create a ref for a property on a source reactive object. The crea
   </script>
   ```
 
-  When `toRef` is used with component props, the usual restrictions around mutating the props still apply. Attempting to assign a new value to the ref is equivalent to trying to modify the prop directly and is not allowed. In that scenario you may want to consider using [`computed`](./reactivity-core.html#computed) with `get` and `set` instead. See the guide to [using `v-model` with components](/guide/components/events.html#usage-with-v-model) for more information.
+  When `toRef` is used with component props, the usual restrictions around mutating the props still apply. Attempting to assign a new value to the ref is equivalent to trying to modify the prop directly and is not allowed. In that scenario you may want to consider using [`computed`](./reactivity-core.html#computed) with `get` and `set` instead. See the guide to [using `v-model` with components](/guide/components/v-model.html) for more information.
 
   `toRef()` will return a usable ref even if the source property doesn't currently exist. This makes it possible to work with optional properties, which wouldn't be picked up by [`toRefs`](#torefs).