Piecing together the expected outcome

Author: Mattp123

powerapps-docs/maker/data-platform/low-code-plugins-copilot-studio.md

@@ -86,7 +86,7 @@ If everything is configured correctly, you see the expected result of 15.5 outpu
 
 ## Send notification low-code plugin example
 
-In this example you create a low-code instant plug-in that wraps an existing API for use with a copilot. The action sends a notification to a user when the user prompts it to do so. The copilot determines the required parameters from the plain language query from the user and sends a notification using a Dataverse low-code plugin-in to a model-driven app in Power Apps.
+In this example you create a low-code instant plug-in that wraps an existing API for use with a copilot. The action sends a notification to the user specified in the copilot action when the user creating the action tests it in Copilot Studio. The copilot determines the required parameters from the plain language query from the user and sends a notification using a Dataverse low-code plugin-in to a model-driven app in Power Apps.
 
 To create your low-code instant plug-in, follow these steps:
 
@@ -144,10 +144,12 @@ Follow these steps in the **Test copilot** pane in Copilot Studio.
 1. Select the sparkle icon at the top of the chat window to start tracing mode. This allows you to confirm that your action is being called and verifies the inputs and outputs of your action. More information: [Testing you copilot using generative actions](/microsoft-copilot-studio/advanced-generative-actions#testing-your-copilot-using-generative-actions)
 1. Enter the text in the chat window *Send a notification to my user to check out this url https://copilotstudio.microsoft.com*, and then select **Send**.
 
-If everything is configured correctly, you see that a notification has been sent in the **Test copilot** pane. You can try some other prompts to test the action further and you could change the plugin to be smarter about how it searches for users given a name to see how the action responds. For example, you could add a step to search for the user by email address if the name doesn't return a result.
+If everything is configured correctly, you see that a notification has been sent in the **Test copilot** pane. The notification is sent as a model-driven in-app notification when the specified user plays the app. 
 
 :::image type="content" source="media/low-code-plugin-copilot-action4.png" alt-text="Results of notifcation sent from copilot" lightbox="media/low-code-plugin-copilot-action4.png":::
 
+You can try some other prompts to test the action further and you could change the plugin to be smarter about how it searches for users given a name to see how the action responds. For example, you could add a step to search for the user by email address if the name doesn't return a result.
+
 ## See also
 
 [Use low-code plug-ins in Dataverse](low-code-plug-ins.md)