Review Notify Workflow

Author: Yiyun333

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/workflow-activities/notify-workflow.md

@@ -13,27 +13,27 @@ This activity can only be used in microflows.
 
 The **Notify workflow** activity is used to resume or trigger logic within a [workflow](/refguide/workflows/). It specifically targets two types of elements:
 
-* A [Wait for Notification](/refguide/wait-for-notification/) workflow activity currently suspended in a flow.
-* A [Notification Event Sub-process](/refguide/workflow-event-sub-processes/) defined within the workflow.
+* A [Wait for notification](/refguide/wait-for-notification/) workflow activity currently suspended in a flow.
+* A [Notification event sub-process](/refguide/workflow-event-sub-processes/) defined within the workflow.
 
-When the **Notify workflow** action is executed, the engine checks for an active receiver. If a valid **Wait for Notification** activity or a **Notification Event Sub-process** is found and successfully triggered, the action returns `true`. If no active receiver is found, it returns `false`.
+When the **Notify workflow** activity is executed, the Workflow Engine checks for an active receiver. If a valid **Wait for notification** activity or a **Notification event sub-process** is found and successfully triggered, the activity returns `true`. If no active receiver is found, it returns `false`.
 
 {{% alert color="warning" %}}
-Attempting to notify a workflow that is already `Completed` or `Aborted` will result in a runtime error. For information on how to handle these cases, see [Error Handling in Microflows](/refguide/error-handling-in-microflows/).
+Attempting to notify a workflow that is already `Completed` or `Aborted` results in a runtime error. For information on how to handle these cases, see [Error Handling in Microflows](/refguide/error-handling-in-microflows/).
 {{% /alert %}}
 
 ### Execution Behavior
 
-The table below describes how the workflow engine responds when a **Notify workflow** action is called, depending on the state of the workflow and the type of receiver configured.
+The table below describes how the Workflow Engine responds when a **Notify workflow** activity is called, depending on the state of the workflow and the type of receiver configured.
 
-| Workflow/Element State              | Action Result | System Behavior                                                                                                                                                |
-|-------------------------------------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Aborted or Completed                | Error         | The action fails. An error is logged indicating the workflow is no longer in an active state and cannot be notified.                                           |
-| Paused, Failed, or Incompatible     | True          | The notification is accepted and "queued." The targeted activity or **Event Sub-process** will trigger automatically once the workflow is resumed or resolved. |
-| **Wait for Notification** (Active)  | True          | The workflow resumes execution from the point of the **Wait for Notification** activity.                                                                       |
-| **Event Sub-process** (Inactive)    | True          | The **Event Sub-process** is triggered immediately and its execution path begins.                                                                              |
-| **Event Sub-process** (In Progress) | False         | The notification is ignored because an instance of this specific sub-process is already running. No new instance is created.                                   |
-| No matching receiver                | False         | If the workflow is active but does not contain the specified **Wait for Notification** activity or **Event Sub-process**, the action returns `false`.          |
+| Workflow/Element State | Action Result | System Behavior |
+| --- | --- | --- |
+| Aborted or Completed | Error | The activity fails. An error is logged indicating the workflow is no longer in an active state and cannot be notified. |
+| Paused, Failed, or Incompatible | True | The notification is accepted and "queued." The targeted activity or event sub-process is triggered automatically once the workflow is resumed or resolved. |
+| Wait for notification (Active) | True | The workflow resumes execution from the point of the **Wait for notification** activity. |
+| Event sub-process (Inactive) | True | The event sub-process is triggered immediately and its execution path begins. |
+| Event sub-process (In Progress) | False | The notification is ignored because an instance of this specific sub-process is already running. No new instance is created. |
+| No matching receiver | False | If the workflow is active but does not contain the specified **Wait for notification** activity or **Event sub-process**, the activity returns `false`. |
 
 ## Properties