[7.16] Fixes minor typos in modeling guide

Co-authored-by: Lisa Cawley <[email protected]>

Author: github-actions[bot]

docs/modeling-guide.md

@@ -2,7 +2,7 @@
 
 The goal of the specification is to be used by different languages, from dynamically typed to statically typed.
 To achieve this goal the specification contains a series of custom types that do not have a meaning
-for the target language, but they should be translated to the most approriate construct.
+for the target language, but they should be translated to the most appropriate construct.
 
 The specification is written in [TypeScript](https://www.typescriptlang.org/), you can find all
 the basic types [here](https://www.typescriptlang.org/docs/handbook/basic-types.html),
@@ -106,8 +106,8 @@ property: UserDefinedValue
 
 ### Numbers
 
-The numeric type in TypeScript is `number`, but given that this specification target mutliple languages,
-it offers a bunch of alias that represents the type that should be used if the language supports it:
+The numeric type in TypeScript is `number`, but given that this specification targets mutliple languages,
+it offers a bunch of aliases that represent the type that should be used if the language supports it:
 
 ```ts
 type short = number
@@ -120,8 +120,8 @@ type double = number
 
 ### Strings
 
-The string type in TypeScript is `string`. It's ok to use it in the spec, but to offer a more developer
-friendly specification, we do offer a set of aliases based on which string we do expect, for example:
+The string type in TypeScript is `string`. It's okay to use it in the spec, but to offer a more developer
+friendly specification, we do offer a set of aliases based on which string we expect, for example:
 
 ```ts
 type ScrollId = string
@@ -233,7 +233,7 @@ class Foo {
 ```
 
 If the variant type is internal you should configure the parent type with
-the `@variants` js doc tag. teh syntax is:
+the `@variants` js doc tag. The syntax is:
 
 ```ts
 /** @variants internal tag='<field-name>' */
@@ -313,8 +313,8 @@ or:
 
 #### Container
 
-The container variant is used for all the types that contains all the
-variants inside the defintion. An example is `QueryContainer`.
+The container variant is used for all the types that contain all the
+variants inside the definition. An example is `QueryContainer`.
 
 The syntax is:
 
@@ -333,7 +333,7 @@ class FooContainer {
 }
 
 ```
-Some containers have properties associated to the container that are not part of the list of variants,
+Some containers have properties associated with the container that are not part of the list of variants,
 for example `AggregationContainer` and its `aggs` and `meta` properties.
 
 An annotation allows distinguishing these properties from container variants:
@@ -365,7 +365,7 @@ class AggregationContainer {
 
 In many places Elasticsearch accepts a property value to be either a complete data structure or a single value, that value being a shortcut for a property in the data structure.
 
-A typical example can be found in queries such as term query: `{"term": {"some_field": {"value": "some_text"}}}` can also be written as `{"term": {"some_field": "some_text"}}`.
+A typical example can be found in queries such as term query. `{"term": {"some_field": {"value": "some_text"}}}` can also be written as `{"term": {"some_field": "some_text"}}`.
 
 This could be modelled as a union of `SomeClass | string`, but this notation doesn't capture the relation between the string variant and the corresponding field (`value` in the above example).
 
@@ -386,7 +386,7 @@ Following you can find a list of the supported tags:
 
 #### `@since`
 
-Every API already has a `@since` tag, which describes when an API has been added.
+Every API already has a `@since` tag, which describes when an API was added.
 You can specify an additional `@since` tag for every property that has been added afterwards.
 If the tag is not defined, it's assumed that the property has been added with the API the first time
 
@@ -470,7 +470,7 @@ class Request {
 
 #### `@codegen_name`
 
-A custom name that can be used to display the property. Useful in Enums an
+A custom name that can be used to display the property. Useful in Enums and
 for request bodies where the document is the entire body.
 
 ```ts
@@ -539,7 +539,7 @@ export interface Request extends RequestBase {
 
 #### `@deprecated`
 
-Use if an endpoint or property is deprecated, you should add the version as well.
+Use if an endpoint or property is deprecated; you should add the version as well.
 
 ```ts
 class Foo {