chore: standartize Array casing

Author: NataliaTepluhina

src/api/built-in-components.md

@@ -173,7 +173,7 @@
 
 - **`include` and `exclude`**
 
-  The `include` and `exclude` props allow components to be conditionally cached. Both props can be a comma-delimited string, a RegExp or an Array:
+  The `include` and `exclude` props allow components to be conditionally cached. Both props can be a comma-delimited string, a RegExp or an array:
 
   ```html
   <!-- comma-delimited string -->

src/api/instance-methods.md

@@ -1,6 +1,6 @@
 # Instance Methods
 
-## $watch
+## \$watch
 
 - **Arguments:**
 
@@ -59,7 +59,7 @@
   })
   ```
 
-  When watched value is an Object or Array, any changes to its properties or elements won't trigger the watcher because they reference the same Object/Array:
+  When watched value is an object or array, any changes to its properties or elements won't trigger the watcher because they reference the same object/array:
 
   ```js
   const app = Vue.createApp({
@@ -81,16 +81,16 @@
       })
     },
     methods: {
-      // These methods won't trigger a watcher because we changed only a property of Object/Array,
-      // not the Object/Array itself
+      // These methods won't trigger a watcher because we changed only a property of object/array,
+      // not the object/array itself
       changeArticleText() {
         this.article.text = 'Vue 3 is awesome'
       },
       addComment() {
         this.comments.push('New comment')
       },
 
-      // These methods will trigger a watcher because we replaced Object/Array completely
+      // These methods will trigger a watcher because we replaced object/array completely
       changeWholeArticle() {
         this.article = { text: 'Vue 3 is awesome' }
       },
@@ -121,7 +121,7 @@
 
 - **Option: deep**
 
-  To also detect nested value changes inside Objects, you need to pass in `deep: true` in the options argument. Note that you don't need to do so to listen for Array mutations.
+  To also detect nested value changes inside Objects, you need to pass in `deep: true` in the options argument. Note that you don't need to do so to listen for array mutations.
 
   ```js
   vm.$watch('someObject', callback, {
@@ -160,7 +160,7 @@
 
   ```js
   let unwatch = null
-  
+
   unwatch = vm.$watch(
     'value',
     function() {
@@ -176,24 +176,24 @@
 - **Option: flush**
 
   The `flush` option allows for greater control over the timing of the callback. It can be set to `'pre'`, `'post'` or `'sync'`.
-  
+
   The default value is `'pre'`, which specifies that the callback should be invoked before rendering. This allows the callback to update other values before the template runs.
-  
+
   The value `'post'` can be used to defer the callback until after rendering. This should be used if the callback needs access to the updated DOM or child components via `$refs`.
 
   If `flush` is set to `'sync'`, the callback will be called synchronously, as soon as the value changes.
 
   For both `'pre'` and `'post'`, the callback is buffered using a queue. The callback will only be added to the queue once, even if the watched value changes multiple times. The interim values will be skipped and won't be passed to the callback.
-  
+
   Buffering the callback not only improves performance but also helps to ensure data consistency. The watchers won't be triggered until the code performing the data updates has finished.
-  
+
   `'sync'` watchers should be used sparingly, as they don't have these benefits.
 
   For more information about `flush` see [Effect Flush Timing](../guide/reactivity-computed-watchers.html#effect-flush-timing).
 
 - **See also:** [Watchers](../guide/computed.html#watchers)
 
-## $emit
+## \$emit
 
 - **Arguments:**
 
@@ -266,21 +266,21 @@
       </div>
     `
   })
-  
+
   app.mount('#emit-example-argument')
   ```
 
 - **See also:**
   - [`emits` option](./options-data.html#emits)
   - [Emitting a Value With an Event](../guide/component-basics.html#emitting-a-value-with-an-event)
 
-## $forceUpdate
+## \$forceUpdate
 
 - **Usage:**
 
   Force the component instance to re-render. Note it does not affect all child components, only the instance itself and child components with inserted slot content.
 
-## $nextTick
+## \$nextTick
 
 - **Arguments:**
 

src/api/options-data.md

@@ -177,7 +177,7 @@
 
 - **Details:**
 
-  An object where keys are expressions to watch and values are the corresponding callbacks. The value can also be a string of a method name, or an Object that contains additional options. The component instance will call `$watch()` for each entry in the object at instantiation. See [$watch](instance-methods.html#watch) for more information about the `deep`, `immediate` and `flush` options.
+  An object where keys are expressions to watch and values are the corresponding callbacks. The value can also be a string of a method name, or an Object that contains additional options. The component instance will call `$watch()` for each entry in the object at instantiation. See [\$watch](instance-methods.html#watch) for more information about the `deep`, `immediate` and `flush` options.
 
 - **Example:**
 
@@ -255,7 +255,7 @@
 
 - **Details:**
 
-  A list/hash of custom events that can be emitted from the component. It has an Array-based simple syntax and an alternative Object-based syntax that allows to configure an event validation.
+  A list/hash of custom events that can be emitted from the component. It has an array-based simple syntax and an alternative Object-based syntax that allows to configure an event validation.
 
   In Object-based syntax, the value of each property can either be `null` or a validator function. The validation function will receive the additional arguments passed to the `$emit` call. For example, if `this.$emit('foo', 1)` is called, the corresponding validator for `foo` will receive the argument `1`. The validator function should return a boolean to indicate whether the event arguments are valid.
 

src/guide/component-custom-events.md

@@ -51,7 +51,7 @@ It is recommended to define all emitted events in order to better document how a
 
 ### Validate Emitted Events
 
-Similar to prop type validation, an emitted event can be validated if it is defined with the Object syntax instead of the Array syntax.
+Similar to prop type validation, an emitted event can be validated if it is defined with the Object syntax instead of the array syntax.
 
 To add validation, the event is assigned a function that receives the arguments passed to the `$emit` call and returns a boolean to indicate whether the event is valid or not.
 

src/guide/forms.md

@@ -60,7 +60,7 @@ Single checkbox, boolean value:
 
 <common-codepen-snippet title="Handling forms: checkbox" slug="PoqyJVE" :preview="false" />
 
-Multiple checkboxes, bound to the same Array:
+Multiple checkboxes, bound to the same array:
 
 ```html
 <div id="v-model-multiple-checkboxes">
@@ -145,7 +145,7 @@ Vue.createApp({
 If the initial value of your `v-model` expression does not match any of the options, the `<select>` element will render in an "unselected" state. On iOS this will cause the user not being able to select the first item because iOS does not fire a change event in this case. It is therefore recommended to provide a disabled option with an empty value, as demonstrated in the example above.
 :::
 
-Multiple select (bound to Array):
+Multiple select (bound to array):
 
 ```html
 <select v-model="selected" multiple>

src/guide/introduction.md

@@ -184,7 +184,7 @@ You can change `seen` from `true` to `false` in the sandbox below to check the e
 
 <common-codepen-snippet title="Conditional rendering" slug="oNXdbpB" tab="js,result" />
 
-There are quite a few other directives, each with its own special functionality. For example, the `v-for` directive can be used to display a list of items using the data from an Array:
+There are quite a few other directives, each with its own special functionality. For example, the `v-for` directive can be used to display a list of items using the data from an array:
 
 ```html
 <div id="list-rendering">

src/guide/render-function.md

@@ -389,7 +389,7 @@ render() {
 
 ### Slots
 
-We can access slot contents as Arrays of VNodes from [`this.$slots`](../api/instance-properties.html#slots):
+We can access slot contents as arrays of VNodes from [`this.$slots`](../api/instance-properties.html#slots):
 
 ```js
 render() {
@@ -408,7 +408,7 @@ render() {
 }
 ```
 
-For component VNodes, we need to pass the children to `h` as an Object rather than an Array. Each property is used to populate the slot of the same name:
+For component VNodes, we need to pass the children to `h` as an object rather than an array. Each property is used to populate the slot of the same name:
 
 ```js
 render() {
@@ -435,7 +435,7 @@ render() {
   // Calls to resolveComponent should be outside the slot function
   const Button = Vue.resolveComponent('MyButton')
   const Icon = Vue.resolveComponent('MyIcon')
-  
+
   return Vue.h(
     Button,
     null,
@@ -449,7 +449,7 @@ render() {
           this.text
         ]
       }
-    } 
+    }
   )
 }
 ```
@@ -472,15 +472,15 @@ render() {
     {
       // If we want to pass on a slot function we can
       header: this.$slots.header,
-      
+
       // If we need to manipulate the slot in some way
       // then we need to wrap it in a new function
       default: (props) => {
         const children = this.$slots.default ? this.$slots.default(props) : []
-        
+
         return children.concat(Vue.h('div', 'Extra child'))
       }
-    } 
+    }
   )
 }
 ```