Merge pull request #230142 from ecfan/patch-2

Azure Logic Apps: Fix text about gateway triggers unavailable in Standard

Author: prmerger-automator[bot]

articles/logic-apps/single-tenant-overview-compare.md

@@ -278,8 +278,6 @@ For the **Logic App (Standard)** resource, these capabilities have changed, or t
 
   * These triggers and actions have either changed or are currently limited, unsupported, or unavailable:
 
-    * [On-premises data gateway *triggers*](../connectors/managed.md#on-premises-connectors) are unavailable, but gateway actions *are* available.
-
     * The built-in action, [Azure Functions - Choose an Azure function](logic-apps-azure-functions.md) is now **Azure Function Operations - Call an Azure function**. This action currently works only for functions that are created from the **HTTP Trigger** template.
 
       In the Azure portal, you can select an HTTP trigger function that you can access by creating a connection through the user experience. If you inspect the function action's JSON definition in code view or the **workflow.json** file using Visual Studio Code, the action refers to the function by using a `connectionName` reference. This version abstracts the function's information as a connection, which you can find in your logic app project's **connections.json** file, which is available after you create a connection in Visual Studio Code.