Line edits3

Author: lootle1

learn-pr/azure/logic-apps-and-custom-connectors/6-make-your-custom-connector-available-to-the-entire-organization.yml

@@ -3,7 +3,7 @@ uid: learn.azure.logic-apps-and-custom-connectors.6-make-your-custom-connector-a
 title: Share a custom connector
 metadata:
   title: Share a custom connector
-  description: In this unit, you will learn how to publish your custom connector, both inside your organization and to the wider community.
+  description: In this unit, you'll learn how to publish your custom connector, both inside your organization and to the wider community.
   ms.date: 06/03/2025
   author: ecfan
   ms.author: estfan
@@ -19,22 +19,22 @@ quiz:
     choices:
     - content: "Yes, you can apply for certification immediately."
       isCorrect: false
-      explanation: "This connector is not eligible for certification because you do not own the underlying service."
+      explanation: "This connector isn't eligible for certification because you don't own the underlying service."
     - content: "Yes, you can apply for certification after a single modification."
       isCorrect: false
-      explanation: "This connector is not eligible for certification because you do not own the underlying service."
-    - content: "No, you cannot apply for certification."
+      explanation: "This connector isn't eligible for certification because you don't own the underlying service."
+    - content: "No, you can't apply for certification."
       isCorrect: true
-      explanation: "This connector is not eligible for certification because you do not own the underlying service."
+      explanation: "This connector isn't eligible for certification because you don't own the underlying service."
   - content: "Your company has a connector that uses client certificates for authentication and provides access to your own REST API, which has typical availability of 95%. Is your connector eligible for certification?"
     choices:
     - content: "Yes, you can apply for certification immediately."
       isCorrect: false
-      explanation: "Modify the API to use OAuth2, an API key, or basic authentication. Client certificate authentication is not supported."
+      explanation: "Modify the API to use OAuth2, an API key, or basic authentication. Client certificate authentication isn't supported."
     - content: "Yes, you can apply for certification after a single modification."
       isCorrect: true
-      explanation: "Modify the API to use OAuth2, an API key, or basic authentication. Client certificate authentication is not supported."
-    - content: "No, you cannot apply for certification."
+      explanation: "Modify the API to use OAuth2, an API key, or basic authentication. Client certificate authentication isn't supported."
+    - content: "No, you can't apply for certification."
       isCorrect: false
-      explanation: "Modify the API to use OAuth2, an API key, or basic authentication. Client certificate authentication is not supported."
+      explanation: "Modify the API to use OAuth2, an API key, or basic authentication. Client certificate authentication isn't supported."
 

learn-pr/azure/logic-apps-and-custom-connectors/includes/2-connectors-for-azure-logic-apps.md

@@ -29,7 +29,7 @@ Azure Logic Apps offers hundreds of connectors, which fall into the following ma
 | Connector group | Description |
 |-----------------|-------------|
 | **Built-in** | Triggers and actions that natively run on the Azure Logic Apps runtime. Some integrate directly with specific Azure services without having to create a connection; for example, Azure Functions. |
-| **Managed** | Triggers and actions that call other services and systems. These operations usually require that you create a connection first. These connectors are hosted and run in Azure and are managed by Microsoft. Managed connectors can fall across the following subgroups: <br><br>- **Standard connectors**: Triggers and actions that integrate with Azure Storage, Microsoft 365, Microsoft Dynamics, Microsoft Power BI, and more. <br><br>- **Enterprise connectors**: Triggers and actions that can access enterprise systems such as SAP, IBM Message Queue, and others for an extra cost. <br><br>- **On-premises connectors**: Triggers and actions that integration with on-premises SQL Server, SharePoint Server, Oracle, file shares, and more. <br><br>- **Integration account connectors**: Triggers and actions that transform and validate XML, encode and decode flat files, and process business-to-business (B2B) messages with AS2, EDIFACT, and X12 protocols. |
+| **Managed** | Triggers and actions that call other services and systems. These operations usually require that you create a connection first. Microsoft hosts and runs these connectors in Azure. Managed connectors can fall across the following subgroups: <br><br>- **Standard connectors**: Triggers and actions that integrate with Azure Storage, Microsoft 365, Microsoft Dynamics, Microsoft Power BI, and more. <br><br>- **Enterprise connectors**: Triggers and actions that can access enterprise systems such as SAP, IBM Message Queue, and others for an extra cost. <br><br>- **On-premises connectors**: Triggers and actions that integration with on-premises SQL Server, SharePoint Server, Oracle, file shares, and more. <br><br>- **Integration account connectors**: Triggers and actions that transform and validate XML, encode and decode flat files, and process business-to-business (B2B) messages with AS2, EDIFACT, and X12 protocols. |
 |||
 
 ### Triggers in Azure Logic Apps

learn-pr/azure/logic-apps-and-custom-connectors/includes/4-access-an-api-with-a-logic-apps-custom-connector.md

@@ -16,7 +16,7 @@ The Postman app requires you to provide the request URL and any necessary authen
 
 ### OpenAPI definition
 
-An OpenAPI definition file is a JSON file that lists the API's methods, parameters, and outputs. In .NET, you can create an OpenAPI file by adding the **Swashbuckle** NuGet package to your API's project. Then, add the following code below to the Web API's source code:
+An OpenAPI definition file is a JSON file that lists the API's methods, parameters, and outputs. In .NET, you can create an OpenAPI file by adding the **Swashbuckle** NuGet package to your API's project. Then, add the following code to the Web API's source code:
 
 1. In the **Startup.cs** file, add a `using` statement for Swashbuckle: