Spelling Fixes

ArieHein · ArieHein · commit a6866b0c577e · 2024-12-08T20:40:45.000+01:00
diff --git a/articles/logic-apps/authenticate-with-managed-identity.md b/articles/logic-apps/authenticate-with-managed-identity.md
@@ -742,7 +742,7 @@ The following steps show how to use the managed identity with a trigger or actio
         > user-assigned managed identity defined and enabled. However, your logic app should 
         > use only one managed identity at a time. 
         >
-        > For example, a workflow that acceses different Azure Service Bus messaging entities 
+        > For example, a workflow that accesses different Azure Service Bus messaging entities 
         > should use only one managed identity. See [Connect to Azure Service Bus from workflows](../connectors/connectors-create-api-servicebus.md#prerequisites).
 
      For more information, see [Example: Authenticate built-in trigger or action with a managed identity](#authenticate-built-in-managed-identity).
@@ -1303,7 +1303,7 @@ For more information, see [Microsoft.Web/connections/accesspolicies (ARM templat
 
 ---
 
-<a name="setup-identity-apihub-authentiation"></a>
+<a name="setup-identity-apihub-authentication"></a>
 
 ## Set up advanced control over API connection authentication
 
diff --git a/articles/logic-apps/biztalk-server-to-azure-integration-services-overview.md b/articles/logic-apps/biztalk-server-to-azure-integration-services-overview.md
@@ -280,7 +280,7 @@ Web services support is a popular capability in BizTalk Server and is available
 
 WCF adapters support [Single Sign On (SSO)](/biztalk/core/single-sign-on-support-for-the-wcf-adapters) through impersonation and acquire the Enterprise SSO ticket for using SSO with WCF adapters. This capability enables the user context to flow across systems. From an authentication perspective, [Service Authentication](/biztalk/core/what-are-the-wcf-adapters#service-authentication-types) supports the following types: None, Windows, and Certificate. [Client Authentication](/biztalk/core/what-are-the-wcf-adapters#client-authentication-types) supports the following types: Anonymous, UserName, Windows, and Certificate. Supported [security modes](/biztalk/core/what-are-the-wcf-adapters#security-modes) include the following types: Transport, Message, and Mixed.
 
-WCF supports transactions using the [WS-AutomicTransaction protocol](/biztalk/core/what-are-the-wcf-adapters#ws-atomictransaction), which you can find in WCF adapters such as WCF-WsHttp, WCF-NetTcp, and WCF-NetMsmq. This capability is supported in the following scenarios:
+WCF supports transactions using the [WS-AtomicTransaction protocol](/biztalk/core/what-are-the-wcf-adapters#ws-atomictransaction), which you can find in WCF adapters such as WCF-WsHttp, WCF-NetTcp, and WCF-NetMsmq. This capability is supported in the following scenarios:
 
 - Transactional submission of messages to the MessageBox database
 - Transactional transmission of messages from the MessageBox to a transactional destination
@@ -419,7 +419,7 @@ Beyond the core XML transformations, BizTalk Server also provides encoding and d
 
 - Azure Functions
 
-  You can execute XSLT or Liquid template transformations by using C# or any other programing language to create an Azure function that you can call with Azure API Management or Azure Logic Apps.
+  You can execute XSLT or Liquid template transformations by using C# or any other programming language to create an Azure function that you can call with Azure API Management or Azure Logic Apps.
 
 ### Network connectivity
 
diff --git a/articles/logic-apps/connectors/sap-generate-schemas-for-artifacts.md b/articles/logic-apps/connectors/sap-generate-schemas-for-artifacts.md
@@ -350,7 +350,7 @@ You can begin your XML schema with an optional XML prolog. The SAP connector wor
 
 ### XML samples for RFC requests
 
-The following example shows a basic RFC call where the RFC name is `STFC_CONNECTION`. This request uses the default namespace named `xmlns=`. However, you can assign and use namespace aliases such as `xmmlns:exampleAlias=`. The namespace value is the namespace for all the RFCs in SAP for Microsoft services. The request has a simple input parameter named `<REQUTEXT>`.
+The following example shows a basic RFC call where the RFC name is `STFC_CONNECTION`. This request uses the default namespace named `xmlns=`. However, you can assign and use namespace aliases such as `xmlns:exampleAlias=`. The namespace value is the namespace for all the RFCs in SAP for Microsoft services. The request has a simple input parameter named `<REQUTEXT>`.
 
 ```xml
 <STFC_CONNECTION xmlns="http://Microsoft.LobServices.Sap/2007/03/Rfc/">
diff --git a/articles/logic-apps/create-replication-tasks-azure-resources.md b/articles/logic-apps/create-replication-tasks-azure-resources.md
@@ -113,7 +113,7 @@ For Service Bus, you must enable sessions so that message sequences with the sam
 > a disruptive event. To prevent reprocessing already processed messages, you have to set up a way to 
 > track the already processed messages so that processing resumes only with the unprocessed messages.
 >
-> For example, you can set up a database that stores the proccessing state for each message. 
+> For example, you can set up a database that stores the processing state for each message. 
 > When a message arrives, check the message's state and process only when the message is unprocessed. 
 > That way, no processing happens for an already processed message. 
 >
diff --git a/articles/logic-apps/create-single-tenant-workflows-azure-portal.md b/articles/logic-apps/create-single-tenant-workflows-azure-portal.md
@@ -32,7 +32,7 @@ You can have multiple workflows in a Standard logic app. Workflows in the same l
 >
 > - *What's Azure Logic Apps?*
 > - *What's a Standard logic app workflow?*
-> - *What's the Request triger?*
+> - *What's the Request trigger?*
 > - *What's the Office 365 Outlook connector?*
 >
 > To find Azure Copilot, on the [Azure portal](https://portal.azure.com) toolbar, select **Copilot**.
diff --git a/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md b/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md
@@ -339,7 +339,7 @@ Before you can create your logic app, create a local project so that you can man
    > [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
    > 
    > The **APP_KIND** app setting is required for your Standard logic app, and the value
-   > must be **workflowApp**. Howeever, in some scenarios, this app setting might be missing,
+   > must be **workflowApp**. However, in some scenarios, this app setting might be missing,
    > for example, due to automation using Azure Resource Manager templates or other scenarios
    > where the setting isn't included. If certain actions don't work, such as the **Execute JavaScript Code**
    > action, or if the workflow stops working, check that the **APP_KIND** app setting exists and is set to to **workflowApp**.
diff --git a/articles/logic-apps/devops-deployment-single-tenant-azure-logic-apps.md b/articles/logic-apps/devops-deployment-single-tenant-azure-logic-apps.md
@@ -6,7 +6,7 @@ ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: conceptual
 ms.date: 10/23/2024
-# Customer intent: As a developer, I want to learn about DevOps deployment support for Standard logi apps in single-tenant Azure Logic Apps.
+# Customer intent: As a developer, I want to learn about DevOps deployment support for Standard logic apps in single-tenant Azure Logic Apps.
 ---
 
 # DevOps deployment for Standard logic apps in single-tenant Azure Logic Apps
diff --git a/articles/logic-apps/enterprise-integration/create-integration-account.md b/articles/logic-apps/enterprise-integration/create-integration-account.md
@@ -437,7 +437,7 @@ To make this change, you can use either the Azure portal or the Azure CLI.
 
 1. In the Azure portal, open the [Azure Cloud Shell](../../cloud-shell/overview.md) environment.
 
-   ![Screenshot shows Azure portal toolbar with selected Cloud Shell optiond.](./media/create-integration-account/open-azure-cloud-shell-window.png)
+   ![Screenshot shows Azure portal toolbar with selected Cloud Shell options.](./media/create-integration-account/open-azure-cloud-shell-window.png)
 
 1. At the command prompt, enter the [**az resource** command](/cli/azure/resource#az-resource-update), and set `skuName` to the higher tier that you want.
 
diff --git a/articles/logic-apps/estimate-storage-costs.md b/articles/logic-apps/estimate-storage-costs.md
@@ -15,7 +15,7 @@ ms.date: 01/10/2024
 Azure Logic Apps uses [Azure Storage](../storage/index.yml) for any storage operations. In traditional *multitenant* Azure Logic Apps, any storage usage and costs are attached to the logic app. Now, in *single-tenant* Azure Logic Apps, you can use your own storage account. These storage costs are listed separately in your Azure billing invoice. This capability gives you more flexibility and control over your logic app data.
 
 > [!NOTE]
-> This article applies to workflows in the single-tenant Azure Logic Apps environment. These workflows exist in the same logic app and in a single tenant that share the same storage. For more information, see [Single-tenant versus multitenant in Azure Logic Appst](single-tenant-overview-compare.md).
+> This article applies to workflows in the single-tenant Azure Logic Apps environment. These workflows exist in the same logic app and in a single tenant that share the same storage. For more information, see [Single-tenant versus multitenant in Azure Logic Apps](single-tenant-overview-compare.md).
 
 Storage costs change based on your workflows' content. Different triggers, actions, and payloads result in different storage operations and needs. This article describes how to estimate your storage costs when you're using your own Azure Storage account with single-tenant based logic apps. First, you can [estimate the number of storage operations you'll perform](#estimate-storage-needs) using the Logic Apps storage calculator. Then, you can [estimate your possible storage costs](#estimate-storage-costs) using these numbers in the Azure pricing calculator.
 
diff --git a/articles/logic-apps/logic-apps-control-flow-run-steps-group-scopes.md b/articles/logic-apps/logic-apps-control-flow-run-steps-group-scopes.md
@@ -334,7 +334,7 @@ here is the JSON definition for trigger and actions in the previous logic app:
     },
     "else": {
       "actions": {
-        "Scope_succeded": {
+        "Scope_succeeded": {
           "type": "ApiConnection",
           "inputs": {
             "body": {
diff --git a/articles/logic-apps/logic-apps-diagnosing-failures.md b/articles/logic-apps/logic-apps-diagnosing-failures.md
@@ -155,7 +155,7 @@ Standard logic apps store all artifacts in an Azure storage account. You might g
 
 | Azure portal location | Error |
 |-----------------------|-------|
-| Overview pane | - **System.private.corelib:Access to the path 'C:\\home\\site\\wwwroot\\hostj.son is denied** <br><br>- **Azure.Storage.Blobs: This request is not authorized to perform this operation** |
+| Overview pane | - **System.private.corelib:Access to the path 'C:\\home\\site\\wwwroot\\host.json is denied** <br><br>- **Azure.Storage.Blobs: This request is not authorized to perform this operation** |
 | Workflows pane | - **Cannot reach host runtime. Error details, Code: 'BadRequest', Message: 'Encountered an error (InternalServerError) from host runtime.'** <br><br>- **Cannot reach host runtime. Error details, Code: 'BadRequest', Message: 'Encountered an error (ServiceUnavailable) from host runtime.'** <br><br>- **Cannot reach host runtime. Error details, Code: 'BadRequest', Message: 'Encountered an error (BadGateway) from host runtime.'** |
 | During workflow creation and execution | - **Failed to save workflow** <br><br>- **Error in the designer: GetCallFailed. Failed fetching operations** <br><br>- **ajaxExtended call failed** |
 
diff --git a/articles/logic-apps/logic-apps-perform-data-operations.md b/articles/logic-apps/logic-apps-perform-data-operations.md
@@ -969,7 +969,7 @@ To try the **Select** action, follow these steps by using the workflow designer.
 > [!TIP]
 >
 > For an example that creates create an array with strings or integers built from the values in a JSON object array, 
-> see the **Select** and **Initliaze variable** action definitions in 
+> see the **Select** and **Initialize variable** action definitions in 
 > [Data operation code examples - Select](logic-apps-data-operations-code-samples.md#select-action-example).
 
 ### [Consumption](#tab/consumption)
diff --git a/articles/logic-apps/rules-engine/add-rules-operators.md b/articles/logic-apps/rules-engine/add-rules-operators.md
@@ -142,6 +142,6 @@ In the preceding example, the `<CheckQuantityAndDoSomething>` function checks th
 ## Related content
 
 - [Create rules with the Microsoft Rules Composer](create-rules.md)
-- [Add control functions to actions for optimizing rules exection](add-rules-control-functions.md)
+- [Add control functions to actions for optimizing rules execution](add-rules-control-functions.md)
 - [Test your rulesets](test-rulesets.md)
 - [Create an Azure Logic Apps Rules Engine project](create-rules-engine-project.md)
diff --git a/articles/logic-apps/rules-engine/create-manage-vocabularies.md b/articles/logic-apps/rules-engine/create-manage-vocabularies.md
@@ -34,7 +34,7 @@ This guide shows how to create and define vocabularies that are placed in the sh
 
 The terms that you use to define rule conditions and actions are often expressed using domain or industry-specific nomenclature. For example, an e-mail user writes rules using terms such as "messages received from" and "messages received after". An insurance business analyst writes rules using terms such as "risk factors" and "coverage amount".
 
-As another exmaple, a variable for an approval status might point at a certain value in an XML schema. Rather than insert this complex representation in a rule, you might instead create a vocabulary definition that is associated with that variable value, and use "Status" as the friendly name. You can then use "Status" in any number of rules. Technology artifacts, such as XML objects and XML documents, that implement the rule conditions and rule actions lie under this domain-specific terminology. However, the rules engine can retrieve the corresponding data from the table that stores that data.
+As another example, a variable for an approval status might point at a certain value in an XML schema. Rather than insert this complex representation in a rule, you might instead create a vocabulary definition that is associated with that variable value, and use "Status" as the friendly name. You can then use "Status" in any number of rules. Technology artifacts, such as XML objects and XML documents, that implement the rule conditions and rule actions lie under this domain-specific terminology. However, the rules engine can retrieve the corresponding data from the table that stores that data.
 
 Rule conditions and actions are based on data sources that might have detailed, difficult-to-read binding information, which tells the user little or nothing about what the bindings reference. The rules engine empowers you to create vocabularies that simplify the rules development by offering intuitive, domain-specific terminology that you can associate with rule conditions and actions.
 
@@ -96,7 +96,7 @@ When you want to make changes in a vocabulary, create a new vocabulary version t
 > [!IMPORTANT]
 >
 > When you create a new vocabulary version, the rules built using a previous vocabulary version still reference 
-> the previous version. Make sure that you update the references between thoes rules and the new vocabulary version. 
+> the previous version. Make sure that you update the references between those rules and the new vocabulary version. 
 
 ## Create an empty vocabulary version
 
diff --git a/articles/logic-apps/rules-engine/create-rules-engine-project.md b/articles/logic-apps/rules-engine/create-rules-engine-project.md
@@ -206,7 +206,7 @@ To reuse existing rules from Microsoft BizTalk Server, you can export them. Howe
                    // Create rules engine instance.
                    var ruleEngine = new RuleEngine(ruleSet: ruleSet);
 
-                   // Create one or more typedXmlDcoument facts from one or more input XML documents.
+                   // Create one or more typedXmlDocument facts from one or more input XML documents.
                    XmlDocument doc = new XmlDocument();
                    doc.LoadXml(inputXml);
                    var typedXmlDocument = new TypedXmlDocument(documentType, doc);
@@ -219,13 +219,13 @@ To reuse existing rules from Microsoft BizTalk Server, you can export them. Howe
 
                    // Send back the relevant results (facts).
                    var updatedDoc = typedXmlDocument.Document as XmlDocument;
-                   var ruleExectionOutput = new RuleExecutionResult()
+                   var ruleExecutionOutput = new RuleExecutionResult()
                    {
                        XmlDoc = updatedDoc.OuterXml,
                        PurchaseAmountPostTax = currentPurchase.PurchaseAmount + currentPurchase.GetSalesTax()
                    };
 
-                   return Task.FromResult(ruleExectionOutput);
+                   return Task.FromResult(ruleExecutionOutput);
                }
                catch(RuleEngineException ruleEngineException)
                {
@@ -324,13 +324,13 @@ To reuse existing rules from Microsoft BizTalk Server, you can export them. Howe
    1. The engine uses the **`RuleExecutionResult`** custom class to return the values to the **`RunRules`** method:
 
       ```csharp
-      var ruleExectionOutput = new RuleExecutionResult()
+      var ruleExecutionOutput = new RuleExecutionResult()
       {
           XmlDoc = updatedDoc.OuterXml,
           PurchaseAmountPostTax = currentPurchase.PurchaseAmount + currentPurchase.GetSalesTax()
       };
 
-      return Task.FromResult(ruleExectionOutput);
+      return Task.FromResult(ruleExecutionOutput);
       ```
 
    1. Replace the sample function code with your own, and edit the default **`RunRules`** method for your own scenarios.
diff --git a/articles/logic-apps/rules-engine/create-rules.md b/articles/logic-apps/rules-engine/create-rules.md
@@ -403,7 +403,7 @@ For example, suppose you have the following XML schema:
 ## Related content
 
 - [Add arithmetic and logical operators to rules](add-rules-operators.md)
-- [Add control functions to actions for optimizing rules exection](add-rules-control-functions.md)
+- [Add control functions to actions for optimizing rules execution](add-rules-control-functions.md)
 - [Perform advanced tasks on rulesets](perform-advanced-ruleset-tasks.md)
 - [Test your rulesets](test-rulesets.md)
 - [Create an Azure Logic Apps Rules Engine project](create-rules-engine-project.md)
diff --git a/articles/logic-apps/rules-engine/perform-advanced-ruleset-tasks.md b/articles/logic-apps/rules-engine/perform-advanced-ruleset-tasks.md
@@ -9,7 +9,7 @@ ms.reviewer: estfan, azla
 ms.topic: how-to
 ms.date: 06/10/2024
 
-#CustomerIntent: As a developer, I want to perform more advanced tasks and operations on rulesets using the Microft Rules Composer.
+#CustomerIntent: As a developer, I want to perform more advanced tasks and operations on rulesets using the Microsoft Rules Composer.
 ---
 
 # Perform advanced tasks on rulesets with the Microsoft Rules Composer (Preview)
@@ -227,7 +227,7 @@ Now, assume that a **Father** instance and a **Son** instance are asserted into
 >
 > The **Instance ID** field is only used within the context of a specific rule evaluation. This field 
 > isn't affixed to an object instance across the ruleset execution and isn't related to the order used 
-> for assesrting objects. Each object instance is evaluated in all rule arguments for that type.
+> for asserting objects. Each object instance is evaluated in all rule arguments for that type.
 
 ## Related content
 
diff --git a/articles/logic-apps/rules-engine/rules-engine-overview.md b/articles/logic-apps/rules-engine/rules-engine-overview.md
@@ -21,7 +21,7 @@ ms.date: 06/10/2024
 
 Organizations deal with decisions every day, but when you have clear business rules that govern your organization's business logic, these decisions are easier to make. Business rules are the guidelines that shape how a business operates. You can find these rules in manuals, contracts, or agreements, or they can be the unwritten knowledge or expertise of employees. Business rules change over time and affect different types of applications. Many business domains, such as finance, healthcare, insurance, transportation, and telecommunications need to communicate their business rules to their staff so they can implement them in software applications.
 
-Traditional programming languages, such as C++, Java, COBOL, Python, JavaScript, or C#, are designed for programmers. So, nonprogrammers have difficulties changing the business rules that guide how software applications work. These languages also require much time and work to create and update applications. However, business rules engines solve this problem by offering a low-code environment that lets you build applications faster and easier. You can use a rules engine to create and change business rules without having to write code or restart the applications that use them.
+Traditional programming languages, such as C++, Java, COBOL, Python, JavaScript, or C#, are designed for programmers. So, non-programmers have difficulties changing the business rules that guide how software applications work. These languages also require much time and work to create and update applications. However, business rules engines solve this problem by offering a low-code environment that lets you build applications faster and easier. You can use a rules engine to create and change business rules without having to write code or restart the applications that use them.
 
 ## Rules engines in a world of microservices
 
diff --git a/articles/logic-apps/rules-engine/test-rulesets.md b/articles/logic-apps/rules-engine/test-rulesets.md
@@ -46,7 +46,7 @@ If you wait to test your rules all at the same time or when you're all done, and
    > [!NOTE]
    >
    > If you assert a derived class into a rule, but the rules are directly written 
-   > against the base class members, a base class instance is assserted instead, 
+   > against the base class members, a base class instance is asserted instead, 
    > and the conditions are evaluated against the base class instance.
 
 1. To remove a fact instance, select the corresponding fact type, and then select **Remove Instance**.

Original file line number	Diff line number	Diff line change
`@@ -113,7 +113,7 @@ For Service Bus, you must enable sessions so that message sequences with the sam`
`113`	`113`	`> a disruptive event. To prevent reprocessing already processed messages, you have to set up a way to`
`114`	`114`	`> track the already processed messages so that processing resumes only with the unprocessed messages.`
`115`	`115`	`>`
`116`		`-> For example, you can set up a database that stores the proccessing state for each message.`
	`116`	`+> For example, you can set up a database that stores the processing state for each message.`
`117`	`117`	`> When a message arrives, check the message's state and process only when the message is unprocessed.`
`118`	`118`	`> That way, no processing happens for an already processed message.`
`119`	`119`	`>`
Original file line number	Diff line number	Diff line change
`@@ -32,7 +32,7 @@ You can have multiple workflows in a Standard logic app. Workflows in the same l`
`32`	`32`	`>`
`33`	`33`	`> - What's Azure Logic Apps?`
`34`	`34`	`> - What's a Standard logic app workflow?`
`35`		`-> - What's the Request triger?`
	`35`	`+> - What's the Request trigger?`
`36`	`36`	`> - What's the Office 365 Outlook connector?`
`37`	`37`	`>`
`38`	`38`	`> To find Azure Copilot, on the [Azure portal](https://portal.azure.com) toolbar, select Copilot.`
Original file line number	Diff line number	Diff line change
`@@ -339,7 +339,7 @@ Before you can create your logic app, create a local project so that you can man`
`339`	`339`	`> [FUNCTIONS_WORKER_RUNTIME app setting](edit-app-settings-host-settings.md#reference-local-settings-json).`
`340`	`340`	`>`
`341`	`341`	`> The APP_KIND app setting is required for your Standard logic app, and the value`
`342`		`- > must be workflowApp. Howeever, in some scenarios, this app setting might be missing,`
	`342`	`+ > must be workflowApp. However, in some scenarios, this app setting might be missing,`
`343`	`343`	`> for example, due to automation using Azure Resource Manager templates or other scenarios`
`344`	`344`	`> where the setting isn't included. If certain actions don't work, such as the Execute JavaScript Code`
`345`	`345`	`> action, or if the workflow stops working, check that the APP_KIND app setting exists and is set to to workflowApp.`