Proofread

Author: adam-dupaski

content/en/docs/appstore/connectors/sap/sap-odata-connector.md

@@ -275,7 +275,7 @@ The OData Connector for SAP solutions module gives you access to additional acti
 This section describes all the actions of the OData Connector for SAP solutions. They are categorized as being either for [entity and attribute manipulation](#EntityManipulation) or [helper actions](#HelperActions).
 
 {{% alert color="info" %}}
-Version 5.3.0 of the OData Connector for SAP solutions adds support for services using OData version 4. Currently, only **Get List** and **Get Entry** are supported for services using OData version 4.
+Version 5.3.0 of the OData Connector for SAP solutions adds support for services using OData v4. Currently, only **Get List** and **Get Entry** are supported for services using OData v4.
 {{% /alert %}}
 
 Some inputs are necessary for the connector to work and these are marked **(required)**. Other inputs are not required, but in some cases this must be made explicit by setting them to *empty*.

content/en/docs/catalog/consume/consume.md

@@ -53,7 +53,7 @@ Access to the data is through the published REST OData service, with reading, qu
 The following operations are affected by using external entities in a consuming app:
 
 * Aggregations – you can count a list of external entities, but you cannot show other aggregations such as sum, average, minimum, and maximum.
-    * [OData version 3.0](https://www.odata.org/documentation/odata-version-3-0/) does not support these operations; the only exception is that you can use the [aggregate list](/refguide/aggregate-list/) microflow activity, which for all aggregations except **Count** will retrieve everything and perform the aggregation in memory
+    * [OData v3.0](https://www.odata.org/documentation/odata-version-3-0/) does not support these operations; the only exception is that you can use the [aggregate list](/refguide/aggregate-list/) microflow activity, which for all aggregations except **Count** will retrieve everything and perform the aggregation in memory
 * [XPath](/refguide/xpath/) – you can use XPath to filter external entities; all XPath constructs are supported, except the following:
     * Three conversions from date/time: `day-of-year-from-dateTime`, `weekday-from-dateTime`, and `week-from-dateTime`
     * Aggregations: `avg()`, `max()`, `min()`, and `sum()`

content/en/docs/refguide/modeling/integration/odata-services/consumed-odata-services/consumed-odata-service.md

@@ -139,7 +139,7 @@ Click the **Properties** tab for the consumed OData service which displays the p
 * **Service ID** – The unique identifier of the service in the Catalog.
 * **Application ID** – The unique identifier of the application that the service was published from in the Catalog.
 * **Metadata** – The contents of the metadata file defining the service.
-* **OData version** – The OData version: can be OData 3 or OData 4.
+* **OData version** – The OData version (can be v3 or v4).
 * **Use QuerySegment** – When set to `No`, the application retrieves data using a `GET HTTP` method and places data query arguments in the URL's query string. When set to `Yes`, then a `POST HTTP` method is used, `/$query` is appended to the resource path of the URL, and the query string is provided as the request body. This enables limiting the length of the URL and avoiding potential problems with the systems involved. This feature is not available for OData v3 or if the consumed service explicitly indicates that it is not supported. For details, see [Passing Query Options in the Request Body](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_PassingQueryOptionsintheRequestBody) in the OData specification. 
 
 ## 3 Updating or Switching a Consumed OData Service {#updating}

content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/_index.md

@@ -12,9 +12,9 @@ In Studio Pro, entities can be exposed as [OData resources](/refguide/published-
 
 A published OData service is a REST service with an OpenAPI contract, which means that OpenAPI compatible REST clients can easily interact with it. 
 
-The standard used for OData in Mendix is [OData version 4](http://www.odata.org/documentation), which returns data in JSON format.
+The standard used for OData in Mendix is [OData v4](http://www.odata.org/documentation), which returns data in JSON format.
 
-The option to publish [OData version 3](http://www.odata.org/documentation/odata-version-3-0) services, which return data in Atom XML format, is deprecated and will be removed in a future version.
+The option to publish [OData v3](http://www.odata.org/documentation/odata-version-3-0) services, which return data in Atom XML format, is deprecated and will be removed in a future version.
 
 Not all parts of the standard are implemented. If something is not documented here, it is has not yet been added.
 
@@ -63,7 +63,7 @@ This list gives an overview of all published attributes and associations.
 
 ### 2.6 Enumerations
 
-This list gives an overview of all [enumerations](/refguide/enumerations/) that are published by the service (for OData version 4 only). When a published entity has an attribute with an enumeration type then the enumeration appears in this list. The list does not appear when there are no published enumerations. There is no need to add enumerations yourself, because Studio Pro will add them when needed.
+This list gives an overview of all [enumerations](/refguide/enumerations/) that are published by the service (for OData v4 only). When a published entity has an attribute with an enumeration type then the enumeration appears in this list. The list does not appear when there are no published enumerations. There is no need to add enumerations yourself, because Studio Pro will add them when needed.
 
 Click **Edit** to change the exposed name of the enumeration (the name as it appears to clients of the service) and to provide documentation.
 

content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/published-odata-attribute.md

@@ -38,7 +38,7 @@ The type of the attribute.
 
 ### 2.6 Exposed As
 
-This field is shown when the type is an enumeration that was previously exposed as a string, and only for OData version 4. Change the value to **Enumeration** to publish the enumeration. This informs clients of the possible values of this attribute.
+This field is shown when the type is an enumeration that was previously exposed as a string, and only for OData v4. Change the value to **Enumeration** to publish the enumeration. This informs clients of the possible values of this attribute.
 
 ### 2.7 Capabilities
 

content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/published-odata-resource.md

@@ -107,7 +107,7 @@ Having an [index](/refguide/indexes/) for the key attribute(s) makes retrieving
 You can set unique and required constraints using [validation rules](/refguide/validation-rules/).
 
 {{% alert color="info" %}}
-Selecting more than one attribute as the key is only available for published OData services that use OData version 4.
+Selecting more than one attribute as the key is only available for published OData services that use OData v4.
 {{% /alert %}}
 
 ## 9 Capabilities {#capabilities}

content/en/docs/refguide/modeling/integration/odata-services/wrap-services-odata.md

@@ -92,7 +92,7 @@ When you use a microflow to provide data, any security constraints are applied t
 
 * **HttpRequest** – The first accepted parameter is an HTTP request of the entity type **System.HttpRequest**. This parameter is optional.
 
-    When a consumer sends a request to the published OData service, the  `HttpRequest` string attribute *Uri* will contain the OData query that consumer requested. Based on that information, the microflow needs to decide what should be returned. For more information on how an OData v4 requests work, see [OData Version 4.0. Part 2: URL Conections Plus Errata 03](https://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part2-url-conventions.html).
+    When a consumer sends a request to the published OData service, the  `HttpRequest` string attribute *Uri* will contain the OData query that consumer requested. Based on that information, the microflow needs to decide what should be returned. For more information on how an OData v4 requests work, see [OData v4.0. Part 2: URL Conections Plus Errata 03](https://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part2-url-conventions.html).
 
 * **ODataResponse** – The second accepted parameter is an OData response of the entity type **System.ODataResponse**. This parameter is optional.
 

content/en/docs/refguide7/desktop-modeler/integration/published-odata-services/_index.md

@@ -13,7 +13,7 @@ In the Modeler, entities can be exposed as [OData resources](/refguide7/publishe
 
 ## 2 OData Version
 
-The standard used for OData in Mendix is [OData version 3](http://www.odata.org/documentation/odata-version-3-0)) with the default representation set to Atom XML. Not all parts of the standard are implemented. If something is not documented here, it is has not yet been added.
+The standard used for OData in Mendix is [OData v3](http://www.odata.org/documentation/odata-version-3-0)) with the default representation set to Atom XML. Not all parts of the standard are implemented. If something is not documented here, it is has not yet been added.
 
 ## 3 Query Options
 

content/en/docs/refguide8/modeling/integration/consumed-odata-services/consumed-odata-service.md

@@ -127,7 +127,7 @@ Click the **Properties** tab for the consumed OData service which displays the p
 * **Service ID** – the unique identifier of the service in the Catalog
 * **Application ID** – the unique identifier of the application that the service was published from in the Catalog
 * **Metadata** – the contents of the metadata file defining the service
-* **OData version** – the OData version: can be OData 3 or OData 4
+* **OData version** – the OData version (can be v3 or v4)
 
 ## 4 Updating or Switching a Consumed OData Service {#updating}
 

content/en/docs/refguide8/modeling/integration/published-odata-services/_index.md

@@ -16,7 +16,7 @@ aliases:
 
 In Studio Pro, entities can be exposed as [OData resources](/refguide8/published-odata-resource/) by adding a new published OData service. You can expose any number of related resources in a published OData service. By default, the non-qualified names of entities are used in the URI to uniquely identify them, but you can override the name of the resource as well.
 
-The standard used for OData in Mendix is [OData version 3](http://www.odata.org/documentation/odata-version-3-0) with the default representation set to Atom XML. Not all parts of the standard are implemented. If something is not documented here, it is has not yet been added.
+The standard used for OData in Mendix is [OData v3](http://www.odata.org/documentation/odata-version-3-0) with the default representation set to Atom XML. Not all parts of the standard are implemented. If something is not documented here, it is has not yet been added.
 
 This document describes the options available to you when you create a published OData service, and ends with some runtime considerations.