Updates per feedback

Author: ecfan

articles/logic-apps/logic-apps-enterprise-integration-maps.md

@@ -64,10 +64,18 @@ This article shows how to add a map to your integration account. If you're worki
 
     * Supports references to external assemblies from maps, which enable direct calls from XSLT maps to custom .NET code. To configure support for external assemblies, see [.NET Framework assembly support for XSLT transformations added to Azure Logic Apps (Standard)](https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/net-framework-assembly-support-added-to-azure-logic-apps/ba-p/3669120).
 
+    * Supports XSLT 1.0, 2.0, and 3.0.
+
     * No limits apply to map file sizes.
 
   * Consumption workflows
 
+    * Azure Logic Apps allocates finite memory for processing XML transformations. If you create Consumption workflows, and your map or payload transformations have high memory consumption, such transformations might fail, resulting in out of memory errors. To avoid this scenario, consider these options:
+
+      * Edit your maps or payloads to reduce memory consumption.
+
+      * Create [Standard logic app workflows](logic-apps-overview.md#resource-environment-differences), which run in single-tenant Azure Logic Apps and offer dedicated and flexible options for compute and memory resources.
+
     * Supports references to external assemblies from maps, which enable direct calls from XSLT maps to custom .NET code with the following requirements:
 
       * You need a 64-bit assembly. The transform service runs a 64-bit process, so 32-bit assemblies aren't supported. If you have the source code for a 32-bit assembly, recompile the code into a 64-bit assembly. If you don't have the source code, but you obtained the binary from a third-party provider, get the 64-bit version from that provider. For example, some vendors provide assemblies in packages that have both 32-bit and 64-bit versions. If you have the option, use the 64-bit version instead.
@@ -86,14 +94,6 @@ This article shows how to add a map to your integration account. If you're worki
 
         To add larger maps, you can use the [Azure Logic Apps REST API - Maps](/rest/api/logic/maps/createorupdate). For Standard workflows, the Azure Logic Apps REST API is currently unavailable.
 
-    * Azure Logic Apps allocates finite memory for processing XML transformations. If you create Consumption workflows, and your map or payload transformations have high memory consumption, such transformations might fail, resulting in out of memory errors. To avoid this scenario, consider these options:
-
-      * Edit your maps or payloads to reduce memory consumption.
-
-      * Create [Standard logic app workflows](logic-apps-overview.md#resource-environment-differences) instead.
-
-        These workflows run in single-tenant Azure Logic Apps, which offers dedicated and flexible options for compute and memory resources. However, Standard workflows support only XSLT 1.0 and don't support referencing external assemblies from maps.
-
 <a name="create-maps"></a>
 
 ## Create maps