Merge pull request #9162 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/powerapps-docs (branch main)

Author: Mattp123

powerapps-docs/maker/data-platform/actions.md

@@ -1,36 +1,35 @@
 ---
 title: "Use custom process actions | MicrosoftDocs"
-description: "With custom process actions, you can perform operations, such as Create, Update, Delete, Assign, or Perform Action. Internally, an custom process action creates a custom message."
+description: "With custom process actions, you can perform operations, such as Create, Update, Delete, Assign, or Perform Action. Internally, a custom process action creates a custom message."
 ms.collection: get-started
 ms.date: 04/28/2021
 ms.reviewer: ""
-
-author: MSFTMAN
+author: Mattp123
 ms.suite: ""
 ms.tgt_pltfrm: ""
 ms.topic: "overview"
 ms.assetid: 1475985f-d3c4-429d-beac-cb455965e792
 caps.latest.revision: 20
 ms.subservice: dataverse-maker
-ms.author: "DEONHE"
+ms.author: "matp"
 search.audienceType: 
   - flowmaker
   - enduser
 ---
 
 # Use custom process actions
 
-Custom process actions, also known as *Custom actions*, or just *actions*. open a range of possibilities for composing business logic. With custom process actions, you can perform operations, such as Create, Update, Delete, Assign, or Perform Action. Internally, a custom process action creates a custom message. Developers refer to these actions as *messages*. If the goal of a process is to create a row, then update it, and then assign it, there are three separate steps. Each step is defined by the capabilities of the table—not necessarily your business process.  
+Custom process actions, also known as *Custom actions*, or just *actions* open a range of possibilities for composing business logic. With custom process actions, you can perform operations, such as Create, Update, Delete, Assign, or Perform Action. Internally, a custom process action creates a custom message. Developers refer to these actions as *messages*. If the goal of a process is to create a row, then update it, and then assign it, there are three separate steps. Each step is defined by the capabilities of the table—not necessarily your business process.  
 
-Custom process actions provide the ability to define a single verb (or message) that matches an operation you need to perform for your business. These new messages are driven by a process or behavior rather than what can be done with a table. These messages can correspond to verbs like Escalate, Convert, Schedule, Route, or Approve—whatever you need. The addition of these verbs helps provide a richer vocabulary for you to fluently define your business processes. You can apply this richer vocabulary from clients or integrations rather than having to write the action within clients. This also makes it easier because you can manage and log the success or failure of the entire action as a single unit.  
+Custom process actions let you define a single verb (or message) that matches an operation you need to perform for your business. These new messages are driven by a process or behavior rather than what can be done with a table. These messages can correspond to verbs like Escalate, Convert, Schedule, Route, or Approve—whatever you need. The addition of these verbs helps provide a richer vocabulary for you to fluently define your business processes. You can apply this richer vocabulary from clients or integrations rather than having to write the action within clients. This also makes it easier because you can manage and log the success or failure of the entire action as a single unit.  
 
 <a name="BKMK_ConfigurableMessages"></a>
 
 ## Configurable messages
 
-Once an action is defined and activated, a developer can use that message like any of the other messages provided by the platform. However, a significant difference is that now someone who is not a developer can apply changes to what should be done when that message is used. You can configure the action to modify steps as your business processes change. Any custom code that uses that message does not need to be changed as long as the process arguments do not change.  
+Once an action is defined and activated, a developer can use that message like any of the other messages provided by the platform. However, a significant difference is that now someone who isn't a developer can apply changes to what should be done when that message is used. You can configure the action to modify steps as your business processes change. Any custom code that uses that message doesn't need to be changed as long as the process arguments don't change.  
 
-Workflow processes and plug-ins continue to provide similar capabilities for defining automation. Workflow processes still provide the capability for a non-developer to apply changes. But the difference is in how the business processes are composed and how a developer can write their code. A custom process action is a message that operates on the same level as any of the messages provided by the platform. Developers can register plug-ins for actions.  
+Workflow processes and plug-ins continue to provide similar capabilities for defining automation. Workflow processes still provide the capability for a nondeveloper to apply changes. But the difference is in how the business processes are composed and how a developer can write their code. A custom process action is a message that operates on the same level as any of the messages provided by the platform. Developers can register plug-ins for actions.  
 
 > [!NOTE]
 > Custom API is a newer way to define custom messages with many advantages for developers. If you do not intend to use the no-code capabilities that custom process actions provide to configure business logic, custom API provides better capabilities for developers to create their own messages. More information: 
@@ -42,7 +41,7 @@ Workflow processes and plug-ins continue to provide similar capabilities for def
 
 ## Global messages 
 
-Unlike Microsoft Dataverse workflows or [plug-ins](../../developer/data-platform/apply-business-logic-with-code.md?branch=master#create-a-plug-in), an custom process action doesn’t have to be associated with a specific table. You can define global custom process actions that can be called on their own.
+Unlike Microsoft Dataverse workflows or [plug-ins](../../developer/data-platform/apply-business-logic-with-code.md?branch=master#create-a-plug-in), a custom process action doesn’t have to be associated with a specific table. You can define global custom process actions that can be called on their own.
 
 ## Next steps
 

powerapps-docs/maker/data-platform/create-and-use-dataflows.md

@@ -217,6 +217,8 @@ The following articles are useful for further information and scenarios when usi
 
 -   [Connect Azure Data Lake Storage Gen2 for dataflow storage](/power-query/dataflows/connect-azure-data-lake-storage-for-dataflow)
 
+-   [Use dataflows in solutions](/power-query/dataflows/dataflow-solution-awareness)
+
 For more information about the Common Data Model:
 
 -   [Common Data Model - overview](/common-data-model/)

powerapps-docs/maker/data-platform/data-platform-import-export.md

@@ -120,7 +120,7 @@ Export data from one or more tables. Exported data is in comma-separated value (
    > ![Sample export that shows successful export with link downloadable file.](./media/data-platform-import-export/export-success.png)
 
 > [!NOTE]
-> Exports have a 12 minute time limit. If the volumne of data exported exceeds 12 minutes the export will fail. If this occurs, export data in smaller segments.
+> Exports have a 12 minute time limit. If the volume of data exported exceeds 12 minutes the export will fail. If this occurs, export data in smaller segments.
 
 ## Unsupported data types and fields
 

powerapps-docs/maker/data-platform/processes.md

@@ -38,7 +38,7 @@ You can also use the following Dataverse processes:
 
 - [Real-time workflows](overview-realtime-workflows.md)
 
-- [Actions](actions.md).
+- [Actions](actions.md)
 
 ## Power Automate
 Power Automate has several different flows you can use to create automated workflows within Dataverse or between Dataverse and another app or service that can be used to synchronize files, get notifications, collect data, and more.