Remove duplicate words

dbreseman · dbreseman · commit 01f551c6c705 · 2024-08-16T10:52:25.000+02:00
diff --git a/content/en/docs/appstore/use-content/modules/aws/amazon-location-service.md b/content/en/docs/appstore/use-content/modules/aws/amazon-location-service.md
@@ -335,7 +335,7 @@ The domain model is a data model that describes the information in your applicat
 
 | Name | Description |
 | --- | --- |
-| N/A | This has no attributes but holds a `SearchPlaceIndexForPositionSummary` object and and an associated list of `SearchForPositionResult` objects. |
+| N/A | This has no attributes but holds a `SearchPlaceIndexForPositionSummary` object and an associated list of `SearchForPositionResult` objects. |
 
 #### 4.1.36 SearchForPositionResult
 
diff --git a/content/en/docs/appstore/use-content/partner-solutions/apd/rg-apd/rg-one-apm/rg-one-measurements-tool.md b/content/en/docs/appstore/use-content/partner-solutions/apd/rg-apd/rg-one-apm/rg-one-measurements-tool.md
@@ -41,7 +41,7 @@ The **Measurement configuration** tab allows you to do the following:
 * **Calculate with expression**
     * If yes, the **Expression** field appears (see below for the expression details)
     * If yes, the **Parameter** field appears (this parameter can be used in the expression)
-* Set the **Frequency (s)** that the measurement is run in in seconds
+* Set the **Frequency (s)** that the measurement is run in seconds
 * **Store in database** stores the measurement in the database
 * You can only measure for triggers; for charts you need the database to be stored in the database
 * The **Remove data after (days)** configures the automatic cleanup (purge) of the data
diff --git a/content/en/docs/appstore/use-content/partner-solutions/ats/rg-ats/v1/rg-one-data-management.md b/content/en/docs/appstore/use-content/partner-solutions/ats/rg-ats/v1/rg-one-data-management.md
@@ -99,7 +99,7 @@ When importing data records all existing records in the dataset will be removed
 {{% /alert %}}
 
 {{% alert color="info" %}}
-When importing data from from Excel, ATS will try to convert data that doesn't match the expected data type. In case a conversion is not possible (for example, from a string to an integer) the resulting value will be empty. Always check your data after import to be sure all data was completely imported.
+When importing data from Excel, ATS will try to convert data that doesn't match the expected data type. In case a conversion is not possible (for example, from a string to an integer) the resulting value will be empty. Always check your data after import to be sure all data was completely imported.
 {{% /alert %}}
 
 You can simply export a dataset by clicking the **Export to Excel** button.
diff --git a/content/en/docs/appstore/use-content/services/pusher.md b/content/en/docs/appstore/use-content/services/pusher.md
@@ -11,7 +11,7 @@ aliases:
 
 The [Pusher](https://marketplace.mendix.com/link/component/107957/) service allows you to trigger a microflow or nanoflow directly from the server on non-native client apps. This means it is triggered from the other session, without waiting for end-users to interact with the page.
 
-In the standard situation, updates in the client are triggered by a user interaction, by timed actions, or by data-grid refresh time. For information not created by the same user session that needs to be updated immediately in the client app, the Mendix core product does not support a viable option to accomplish this. As an alternative, you need need to refresh the page constantly with timers or constant clicking. This is not user-friendly, and it is not preferred when scaling.
+In the standard situation, updates in the client are triggered by a user interaction, by timed actions, or by data-grid refresh time. For information not created by the same user session that needs to be updated immediately in the client app, the Mendix core product does not support a viable option to accomplish this. As an alternative, you need to refresh the page constantly with timers or constant clicking. This is not user-friendly, and it is not preferred when scaling.
 
 With this service, you can create a notify event on the server that directly causes an action in the client application. The event is based on a persistable object that is available in the server and the client page. From a microflow, the notify action will send a message to every listening widget that is listening to the same object and the action name.
 
diff --git a/content/en/docs/catalog/manage/landscape.md b/content/en/docs/catalog/manage/landscape.md
@@ -46,7 +46,7 @@ By default, the **Search** pane is on the left of the Landscape screen. When a s
 
 When you click any of the nodes or connections, the metadata pane on the right displays further details.
 
-You can pan around the landscape and and zoom using the mouse. You can also collapse both the search pane and the metadata pane so that the full screen area is available for viewing.
+You can pan around the landscape and zoom using the mouse. You can also collapse both the search pane and the metadata pane so that the full screen area is available for viewing.
 
 ### 2.3 Nodes
 
diff --git a/content/en/docs/deployment/deploying-to-mindsphere.md b/content/en/docs/deployment/deploying-to-mindsphere.md
@@ -138,7 +138,7 @@ Add the *RegisterSingleSignOn* microflow as the **After startup** microflow or a
 If you are using the Siemens Insights Hub Starter Application, this will already be set up as the *After startup* microflow.
 {{% /alert %}}
 
-If you are are modifying an existing app, you can do this on the *Runtime* tab of the **App** > **Settings** dialog box accessed through the **App Explorer**.
+If you are modifying an existing app, you can do this on the *Runtime* tab of the **App** > **Settings** dialog box accessed through the **App Explorer**.
 
 {{< figure src="/attachments/deployment/deploying-to-mindsphere/image4.png" alt="App settings dialog" class="no-border" >}}
 
diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-rest-action.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-rest-action.md
@@ -177,7 +177,7 @@ This option allows you to send binary data (for example, the contents of a FileD
 
 This option allows you to generate a multipart/form-data request for multiple parts. Each part is a pair with a key and a value (microflow expression). 
 
-FileDocuments and images are are also supported for this option when used as variables in microflow expressions.
+FileDocuments and images are also supported for this option when used as variables in microflow expressions.
 
 For each part, you can specify the HTTP headers. For each part, by default, the **Content-Disposition**  (for file documents and images) and **Content-Type** (for all parts) headers are added. You can specify different values for these headers, or add other headers.
 
diff --git a/content/en/docs/refguide/modeling/pages/chart-widgets/charts-configuration.md b/content/en/docs/refguide/modeling/pages/chart-widgets/charts-configuration.md
@@ -50,7 +50,7 @@ Add series and configure their properties, each series represents a dataset. For
 
 1. Data source<a id="data-source"></a>
 
-    The data for each each series can originate from a different data source. You can add additional data series in the **Chart properties** tab.
+    The data for each series can originate from a different data source. You can add additional data series in the **Chart properties** tab.
 
     {{< figure src="/attachments/refguide/modeling/pages/chart-widgets/charts-configuration/series-item-data-source.png" alt="Edit series Data source tab" class="no-border" >}}
 
diff --git a/content/en/docs/refguide8/modeling/application-logic/activities/integration-activities/call-rest-action.md b/content/en/docs/refguide8/modeling/application-logic/activities/integration-activities/call-rest-action.md
@@ -174,7 +174,7 @@ This option allows you to send binary data (for example, the contents of a FileD
 
 This option allows you to generate a multipart/form-data request for multiple parts. Each part is a pair with a key and a value (microflow expression). 
 
-FileDocuments and images are are also supported for this option when used as variables in microflow expressions.
+FileDocuments and images are also supported for this option when used as variables in microflow expressions.
 
 #### 6.3.1 Content Type
 
diff --git a/content/en/docs/refguide8/modeling/pages/chart-widgets/charts-configuration.md b/content/en/docs/refguide8/modeling/pages/chart-widgets/charts-configuration.md
@@ -50,7 +50,7 @@ Add series and configure their properties, each series represents a dataset. For
 
 1. Data source<a id="data-source"></a>
 
-    The data for each each series can originate from a different data source. You can add additional data series in the **Chart properties** tab.
+    The data for each series can originate from a different data source. You can add additional data series in the **Chart properties** tab.
 
     {{< figure src="/attachments/refguide8/modeling/pages/chart-widgets/charts-configuration/series-item-data-source.png" alt="Edit series Data source tab" class="no-border" >}}
 
diff --git a/content/en/docs/refguide9/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-rest-action.md b/content/en/docs/refguide9/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-rest-action.md
@@ -175,7 +175,7 @@ This option allows you to send binary data (for example, the contents of a FileD
 
 This option allows you to generate a multipart/form-data request for multiple parts. Each part is a pair with a key and a value (microflow expression). 
 
-FileDocuments and images are are also supported for this option when used as variables in microflow expressions.
+FileDocuments and images are also supported for this option when used as variables in microflow expressions.
 
 For each part, you can specify the HTTP headers. For each part, by default, the **Content-Disposition**  (for file documents and images) and **Content-Type** (for all parts) headers are added. You can specify different values for these headers, or add other headers.
 
diff --git a/content/en/docs/refguide9/modeling/pages/chart-widgets/charts-configuration.md b/content/en/docs/refguide9/modeling/pages/chart-widgets/charts-configuration.md
@@ -50,7 +50,7 @@ Add series and configure their properties, each series represents a dataset. For
 
 1. Data source<a id="data-source"></a>
 
-    The data for each each series can originate from a different data source. You can add additional data series in the **Chart properties** tab.
+    The data for each series can originate from a different data source. You can add additional data series in the **Chart properties** tab.
 
     {{< figure src="/attachments/refguide9/modeling/pages/chart-widgets/charts-configuration/series-item-data-source.png" alt="Edit series Data source tab" class="no-border" >}}
 
diff --git a/content/en/docs/releasenotes/sdk/model-sdk/model-sdk-1.md b/content/en/docs/releasenotes/sdk/model-sdk/model-sdk-1.md
@@ -60,7 +60,7 @@ Please run `npm update mendixmodelsdk --save`.
 | 561960 | Low | It is no longer possible to instantiate objects that are derived, such as `LayoutParameter`. |
 | 561960 | Low | All model elements expose a `.model` property that returns the model they belong to. |
 | 561960 | Low | Convenience methods to create elements and add them to a parent directly are introduced for all elements that are stored at a unique place (this holds for most elements except for utilities like `texts.Text`). See the next paragraph for more details. |
-| 553639 | Low | The Model API and SDK observe the same rules for setting properties to `null` as the Modeler does: (1) list properties cannot receive `null` at all, (2) non-list properties can only be set to `null` if they are are object-typed (as in, not primitive or enum) and not required (see documentation). |
+| 553639 | Low | The Model API and SDK observe the same rules for setting properties to `null` as the Modeler does: (1) list properties cannot receive `null` at all, (2) non-list properties can only be set to `null` if they are object-typed (as in, not primitive or enum) and not required (see documentation). |
 | 561972 | Low | It is no longer possible to move a model element from one model to another. In other words: model elements can only exist within the model they were created in. |
 | 562069, 561977, 568908 | None | The SDK is now versioned in the sense that structures and properties can have lifecycles, moving from `not yet introduced` to `introduced` to `deprecated` to `deleted` depending on which version of the Mendix Modeler was used to create (the *.mpk* for) the working copy. The SDK provides suitable warnings or errors (once per structure/property per connection) on the console whenever a structure or property is used that is either not yet introduced, deprecated or deleted. |
 | 463511* | Low | Finding images by qualified name now works, so for example, `pages.StaticImageViewer.image` isn't always `null`. |
diff --git a/content/en/docs/releasenotes/studio-pro/9/9.24.md b/content/en/docs/releasenotes/studio-pro/9/9.24.md
@@ -910,7 +910,7 @@ We made a major update to your business events modeling experience:
 * We now provide more accurate drag-and-drop feedback on domain model and navigation editors, and we fixed the incorrect feedback for a few controls.
 * We updated the data grid and tree controls to allow for scrolling the containing dialog box using the mouse wheel when the cursor is over the controls and the controls do not have a vertical scroll-bar.
 * We improved the resizing behavior of the **Entity Access Rules** dialog box so that the **Documentation** field no longer takes a lot of space. Instead, the grid with **Member Rights** settings adjusts itself to the available space.
-* The Mendix Client now now retrieves non-persistable objects over a direct association without sending a request as long as they have no virtual attributes.
+* The Mendix Client now retrieves non-persistable objects over a direct association without sending a request as long as they have no virtual attributes.
 * We revised MxAssist Performance Bot best practice [MXP015](/refguide9/performance-best-practices/#mxp015) for XPath ordering to avoid false positives.
 * We extended MxAssist Performance Bot best practice [MXP003](/refguide9/performance-best-practices/#mxp003) for a non-indexed attribute used in sorting to include the Integer type.
 * We added a general note to the MxAssist Performance Bot recommendation pop-up messages.
