Merge pull request mendix#8190 from mendix/db-duplicates

Remove duplicate words

Author: dbreseman

content/en/docs/apidocs-mxsdk/apidocs/design-properties.md

@@ -37,7 +37,7 @@ The Design Properties API is designed to allow you to choose between CSS classes
 
 There are several types of design properties: **Toggle**, **Dropdown**, **Colorpicker**, **ToggleButtonGroup**, and **Spacing**. They are intended to cover various use cases, allowing you to choose the design property type that best fits your need. Not all versions of Studio Pro support the same design property types.
 
-* The **Toggle** type can be be turned on or off by the user. It can only be used with CSS classes, which will be applied if the toggle is turned on.
+* The **Toggle** type can be turned on or off by the user. It can only be used with CSS classes, which will be applied if the toggle is turned on.
 * A **Dropdown** allows you to define a set of related options. Only a single option can be selected at a single time.
 
 The following types have been introduced with Studio Pro 10.0.0:

content/en/docs/appstore/creating-content/connector-guide-build/connector-guide-best-practices.md

@@ -108,7 +108,7 @@ All modules have their *.jar* files in the **userlib** folder. In order to speci
 
 4. After implementation libraries are placed into the **userlib** folder, they are available in the Mendix application classpath so they can be used in a Java action in your connector module.
 
-You can also also extend your app with Gradle and add the **Implementation** project as a sub-module. In this case, your implementation project becomes part of your Mendix app. You can use it in Java actions without having to copy the *.jar* files to the **userlib** folder. 
+You can also extend your app with Gradle and add the **Implementation** project as a sub-module. In this case, your implementation project becomes part of your Mendix app. You can use it in Java actions without having to copy the *.jar* files to the **userlib** folder. 
 
 {{% alert color="warning" %}}
 You must have the *.jar* file placed in the  **userlib** folder before exporting the connector module. Otherwise, **Implementation** *.jar* files will not be packaged with the module.

content/en/docs/appstore/sharing-content/_index.md

@@ -182,7 +182,7 @@ The [GNU General Public License (GPL), version 3](https://www.gnu.org/licenses/g
 
 You can configure your own proprietary license for your company’s content. The license can be used for multiple components, and it can be used by everyone within your organization. 
 
-This license can be created for a new **Public Marketplace (all Mendix users)** component by requesting a new license and submitting it alongside the component. The license needs to be [approved by Mendix](/appstore/sharing-content/#guidelines) after you have created and submitted it the first time. Once it has been submitted for approval, you and the people within your organization can also use it it for other components.
+This license can be created for a new **Public Marketplace (all Mendix users)** component by requesting a new license and submitting it alongside the component. The license needs to be [approved by Mendix](/appstore/sharing-content/#guidelines) after you have created and submitted it the first time. Once it has been submitted for approval, you and the people within your organization can also use it for other components.
 
 Follow these steps to configure a proprietary license for a new public component:
 

content/en/docs/appstore/use-content/modules/aws/amazon-bedrock.md

@@ -336,7 +336,7 @@ This entity extends the GenAICommons.EmbeddingsOptions entity with attributes sp
 
 ##### 4.1.1.12 CohereEmbedResponse {#cohere-embed-response}
 
-This entity inherits from and extends the `GenAICommons.EmbeddingsResponse` entity with attributes specific to to the `Embeddings_SingleString` and `Embeddings_ChunkCollection` operations for the Cohere Embed model family.
+This entity inherits from and extends the `GenAICommons.EmbeddingsResponse` entity with attributes specific to the `Embeddings_SingleString` and `Embeddings_ChunkCollection` operations for the Cohere Embed model family.
 
 | Attribute | Description |
 | --- | --- |

content/en/docs/appstore/use-content/modules/aws/aws-create-new.md

@@ -199,7 +199,7 @@ In the Mendix project, document the exposed microflow actions, as well as the en
 * What are the required and optional input parameters for the microflow action?
 * Example:
 
-    *The DeleteItem Amazon DynamoDB action allows you to delete an item from a given table from your DynamoDB environment. It requires a valid AWS region, DeleteItemRequest object with an Item object associated to it. If the given table has only a partition key, the Item object should have a KeyValue object that that refers to the row that to be deleted. If the given table has both a partition and sort key, the Item object must have two KeyValue objects.*
+    *The DeleteItem Amazon DynamoDB action allows you to delete an item from a given table from your DynamoDB environment. It requires a valid AWS region, DeleteItemRequest object with an Item object associated to it. If the given table has only a partition key, the Item object should have a KeyValue object that refers to the row that to be deleted. If the given table has both a partition and sort key, the Item object must have two KeyValue objects.*
 
     *Optionally, a condition expression can be included. The delete action is then only performed when the condition returns true. Additionally, an expression attribute list can be included to escape reserved words.*
 

content/en/docs/appstore/use-content/modules/aws/aws-dynamodb.md

@@ -577,7 +577,7 @@ The input and output for this service are shown in the table below:
 
 #### 4.3.5 DeleteItem
 
-The `DeleteItem` Amazon DynamoDB activity allows you to delete an item from a given table from your DynamoDB environment. It requires a valid AWS region, a `Credentials` object and a `DeleteItemRequest` object with a `DeleteItem` object associated to it. If the given table has only a partition key, the `DeleteItem` object should have a `KeyValue` object that that refers to the row that to be deleted. If the given table has both a partition and sort key, the `DeleteItem` object must have two `KeyValue` objects.
+The `DeleteItem` Amazon DynamoDB activity allows you to delete an item from a given table from your DynamoDB environment. It requires a valid AWS region, a `Credentials` object and a `DeleteItemRequest` object with a `DeleteItem` object associated to it. If the given table has only a partition key, the `DeleteItem` object should have a `KeyValue` object that refers to the row that to be deleted. If the given table has both a partition and sort key, the `DeleteItem` object must have two `KeyValue` objects.
 
 Optionally, you can include a condition expression. The delete activity is then only performed when the condition returns true. Additionally, you can include an expression attribute list to escape reserved words.
 

content/en/docs/appstore/use-content/modules/data-widgets/data-grid-2.md

@@ -89,7 +89,7 @@ In the new data grid we offer two types of pagination: **Paging Buttons** and **
 
 ### 3.1 Paging Buttons
 
-The **Paging Buttons** option will render the default buttons as the previous data grid. When the data source is uncountable (for example, external entities), neither the last page button nor the counting will be be available.
+The **Paging Buttons** option will render the default buttons as the previous data grid. When the data source is uncountable (for example, external entities), neither the last page button nor the counting will be available.
 
 {{< figure src="/attachments/appstore/use-content/modules/data-widgets/data-grid-2/paging-buttons.png" alt="Example of paging buttons" >}}
 

content/en/docs/appstore/use-content/modules/genai/conversational-ui.md

@@ -72,7 +72,7 @@ To help you work with the Conversational UI module, the following sections of th
 
 ### 4.1 Module Roles {#module-roles}
 
-Make sure that the module role `User` is part of the the user roles that are intended to chat with the model. Optionally, you can grant the `_addOn_ReadAll` role to admin roles, so that users with that role can read all messages.
+Make sure that the module role `User` is part of the user roles that are intended to chat with the model. Optionally, you can grant the `_addOn_ReadAll` role to admin roles, so that users with that role can read all messages.
 
 | Module role | Description |
 | --- | --- |
@@ -133,7 +133,7 @@ Add the action microflow to an existing `ProviderConfig` by using the **Set Acti
 
 ##### 4.3.1.2 Creating a Custom Action Microflow
 
-If you want to create your own custom action microflow, keep the following considerations in in mind:
+If you want to create your own custom action microflow, keep the following considerations in mind:
 
 * Only one input parameter of [ChatContext](#chat-context) is accepted.
 * The return type needs to be a `Success` Boolean.

content/en/docs/appstore/use-content/modules/saml.md

@@ -171,7 +171,7 @@ You can now finish configuring your SAML module in your app by reviewing/updatin
 
 ### 3.1 Configuring Service Provider{#configure-sp}
 
-Before any IdP can be configured, you need to configure the SP, which is your current application. The SP configuration allows you to configure some basic information for the SP metadata file. This information will be be available in the IdP for the reference of the IdP administrator.
+Before any IdP can be configured, you need to configure the SP, which is your current application. The SP configuration allows you to configure some basic information for the SP metadata file. This information will be available in the IdP for the reference of the IdP administrator.
 
 {{% alert color="info" %}}
 The base URL used for the links in your SP metadata is determined by the **Application Root URL** [custom runtime setting](/refguide/custom-settings/#general) of your app. Change the value for this runtime setting to change the base URL of the links in your SP metadata. After changing the **Application Root URL** setting, you have to import the SP metadata into your IdP again.

content/en/docs/appstore/use-content/modules/snowflake/snowflake-edc.md

@@ -298,7 +298,7 @@ To execute and test the query in Studio Pro, follow these steps:
 
 ## 7 Using Cortex AI functions
 
-Snowflake comes with built in AI functionality that you can leverage in your Mendix applications. This section provides an example of a query that calls the *sentiment* function to to analyze the sentiment of a piece of text.
+Snowflake comes with built in AI functionality that you can leverage in your Mendix applications. This section provides an example of a query that calls the *sentiment* function to analyze the sentiment of a piece of text.
 
 To execute and test the query in Studio Pro, follow these steps: