Review: Drop obsolete "single" from object datasource

Author: mlaponder

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md

@@ -60,7 +60,7 @@ This defines a property's type. A `type` must be one of the following:
     * [file](#file)
     * [datasource](#datasource)
         * [List data source](#list-datasource)
-        * [Single object data source](#single-object-datasource)
+        * [Object data source](#object-datasource)
     * [selection](#selection)
 
 ### XML Elements
@@ -745,7 +745,7 @@ Then the Studio Pro UI for the property appears like this:
 
 ### Datasource {#datasource}
 
-The datasource property allows widgets to work with data from the Mendix Platform. It comes in two variants controlled by the `isList` attribute: a **list data source** (`isList="true"`) for working with collections of objects, and a **single object data source** (`isList="false"`) for working with a single object.
+The datasource property allows widgets to work with data from the Mendix Platform. It comes in two variants controlled by the `isList` attribute: a **list data source** (`isList="true"`) for working with collections of objects, and an **object data source** (`isList="false"`) for working with a single object.
 
 If no data source has been configured by the user, any properties that are linked to the datasource property are automatically omitted from the props passed to the client component (even if they are marked as required).
 
@@ -755,7 +755,7 @@ If no data source has been configured by the user, any properties that are linke
 |----------------|----------|----------------|------------------------------------------------------------------------------------------------------------|
 | `type`         | Yes      | String         | Must be `datasource`                                                                                       |
 | `key`          | Yes      | String         | See [key](#key)                                                                                            |
-| `isList`       | Yes      | Boolean        | `true` for a list data source, `false` for a single object data source                                     |
+| `isList`       | Yes      | Boolean        | `true` for a list data source, `false` for an object data source                                           |
 | `required`     | No       | Boolean        | This decides if the user is required to specify a datasource, `true` by default                            |
 | `defaultType`  | No       | String         | Default type for the property, see [Default Data Sources](#data-source-defaults)                           |
 | `defaultValue` | No       | String         | Default value for the property, see [Default Data Sources](#data-source-defaults)                          |
@@ -769,7 +769,7 @@ The format of `defaultValue` depends on the chosen `defaultType`:
 | Data source type         | Format      | Example                                                               | Supported for                      |
 |--------------------------|-------------|-----------------------------------------------------------------------|------------------------------------|
 | `Database` `Association` | Entity Path | `ModuleName.EntityName` or `ModuleName.A/ModuleName.A_B/ModuleName.B` | List data source                   |
-| `Microflow` `Nanoflow`   | Document ID | `ModuleName.DocumentName`                                             | List and single object data source |
+| `Microflow` `Nanoflow`   | Document ID | `ModuleName.DocumentName`                                             | List and object data source |
 
 #### List Data Source {#list-datasource}
 
@@ -790,15 +790,15 @@ Then the Studio Pro UI for the property appears like this:
 
 {{< figure src="/attachments/apidocs-mxsdk/apidocs/pluggable-widgets/pluggable-widgets-property-types/datasource-list.png" class="no-border" >}}
 
-#### Single Object Data Source {#single-object-datasource}
+#### Object Data Source {#object-datasource}
 
 {{% alert color="info" %}}
-The single object data source was introduced in Mendix [11.11](/releasenotes/studio-pro/11.11/).
+The object data source was introduced in Mendix [11.11](/releasenotes/studio-pro/11.11/).
 {{% /alert %}}
 
-A single object data source (`isList="false"`) allows a widget to work with a single object. The client component receives a prop of type [`DynamicValue<ObjectItem>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#dynamic-value).
+An object data source (`isList="false"`) allows a widget to work with a single object. The client component receives a prop of type [`DynamicValue<ObjectItem>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#dynamic-value).
 
-A widget may have at most one single object data source property.
+A widget may have at most one object data source property.
 
 The available source types differ from list data sources:
 
@@ -826,7 +826,7 @@ Then the Studio Pro UI for the property appears like this:
 
 The [`action`](#action), [`attribute`](#attribute), [`association`](#association), [`expression`](#expression), [`text template`](#texttemplate), [`widgets`](#widgets), and [`selection`](#selection) properties can be linked to a data source using the `dataSource` attribute on those properties. The client type received by the component depends on the data source type:
 
-| Property type  | List data source client type | Single object data source client type |
+| Property type  | List data source client type | Object data source client type |
 |:---------------|:-----------------------------|:--------------------------------------|
 | `action`       | [`ListActionValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listactionvalue) | [`ActionValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#action-value) |
 | `attribute`    | [`ListAttributeValue<T>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listattributevalue) | [`EditableValue<T>`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#editable-value) |
@@ -852,7 +852,7 @@ The selection property allows a widget to read and set a selection that can be u
 | `onChange`     | No       | Property Path       | The path to an [`action`](#action) property that will be run by the Mendix Platform when the selection is changed by the widget |
 
 {{% alert color="warning" %}}
-The `dataSource` attribute must refer to a [list data source](#list-datasource). Linking a selection property to a single object data source is not supported.
+The `dataSource` attribute must refer to a [list data source](#list-datasource). Linking a selection property to an object data source is not supported.
 {{% /alert %}}
 
 #### XML Elements