Revised for style and naming

Author: Mattp123

powerapps-docs/maker/data-platform/dataverse-accelerator/api-playground.md

@@ -1,6 +1,6 @@
 ---
 title: Test and explore the Dataverse Web API
-description:  Quickly and conveniently interact with Power Platform web APIs, including the Dataverse Web API in a pre-authenticated software testing tool.
+description:  Quickly and conveniently interact with Power Platform web APIs, including the Dataverse Web API in a preauthenticated software testing tool.
 author: denise-msft
 ms.author: demora
 ms.reviewer: matp
@@ -16,7 +16,7 @@ contributors:
 
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../../includes/cc-beta-prerelease-disclaimer.md)]
 
-The API playground is a pre-authenticated software testing tool that helps makers quickly and conveniently interact with the [Microsoft Dataverse Web API](/power-apps/developer/data-platform/webapi/overview).
+The API playground is a preauthenticated software testing tool that helps makers quickly and conveniently interact with the [Microsoft Dataverse Web API](/power-apps/developer/data-platform/webapi/overview).
 
 ![API playground home screen](./media/api-play-landing.svg)
 
@@ -31,17 +31,17 @@ Use this tool to explore what's possible in the RESTful API, test user-defined w
 
 ## Key features
 
-- Pre-authenticated: The API playground comes pre-authenticated, so developers can start testing and experimenting with API endpoints right away.
+- Preauthenticated: The API playground comes preauthenticated, so developers can start testing and experimenting with API endpoints right away.
 - Web-based: With the API playground, developers can quickly interact with the Dataverse Web API without the need for extensive setup like software downloads or non-Microsoft account setup. You can access the tool from the Dataverse accelerator, a Microsoft app available in all new Dataverse environments and can be installed in any environment.
 - Convenient: Presents the various actions and capabilities available in the Dataverse Web API, making it easy to quickly learn what's possible and how to implement it.
 
 ## Prerequisites
 
-You must have [access to Dataverse](/power-apps/maker/data-platform/data-platform-entity-licenses), and [access to run the Dataverse accelerator app](./dataverse-accelerator.md#prerequisites-to-run-the-dataverse-accelerator).
+You must have [access to Dataverse](/power-apps/maker/data-platform/data-platform-entity-licenses), and [access to play the Dataverse accelerator app](./dataverse-accelerator.md#prerequisites-to-run-the-dataverse-accelerator). Members of the system customizer security role have access to play the app.
 
 ## Get started
 
-To get started with the API playground, [run](dataverse-accelerator.md#play-the-dataverse-accelerator) the Dataverse accelerator and navigate to the API playground page.
+To get started with the API playground, [play](dataverse-accelerator.md#play-the-dataverse-accelerator) the Dataverse accelerator and go to the API playground page.
 
 ![Run the API playground by selecting the feature card](media/api-play-run.svg)
 
@@ -61,10 +61,10 @@ Three request types are presented:
 
 These request types are designed to simplify calling plug-ins available in the working environment.
 
-1. Select an option from the main dropdown, which presents the available plugins in the current environment.
-   ![Custom APIs are listed in the dropdown](./media/api-play-list-customapi.svg)
+1. Select an option from the main dropdown list, which presents the available plug-ins in the current environment.
+   ![Custom APIs are listed in the dropdown list](./media/api-play-list-customapi.svg)
 
-1. If parameters are available, they are displayed in the **Query params** table that appears. Provide values for required parameters.
+1. If parameters are available, they're displayed in the **Query params** table that appears. Provide values for required parameters.
 
     ![Custom API parameters display automatically](./media/api-play-customapi-params.svg)
 
@@ -73,9 +73,9 @@ These request types are designed to simplify calling plug-ins available in the w
 
 1. Select **Send**.
 
-Observe the [response](#view-the-response) in the lower section of the screen.
+1. Observe the [response](#view-the-response) in the lower section of the screen.
 
-![Parameters are listed if registered](./media/api-play-response.svg)
+   ![Parameters are listed if registered](./media/api-play-response.svg)
 
 > [!NOTE]
 > The interface provides a convenient listing of all available plug-ins in the environment. When selected, the associated parameters with data types are presented. Behind the scenes an OData call is still being made, but the interface simplifies the construction of the call.
@@ -84,25 +84,25 @@ Observe the [response](#view-the-response) in the lower section of the screen.
 
 OData requests allow more options for request parameters.
 
-1. Select the **HTTP request method** in the first dropdown list. <!-- start here-->
+1. Select the **HTTP request method** in the first dropdown list.
 
-1. Type in the *endpoint Url*. Only include the request Url after `[OrgUrl]/api/data/v9.2/`
+1. Type in the *endpoint Url*. Only include the request URL after `[OrgUrl]/api/data/v9.2/`
 
 1. Add *query parameters* using one of the two methods:
 
-    1. In the Url
-        1. After the question mark (`?`) character in the Url, type in the query parameter key.
+    1. In the URL.
+        1. After the question mark (`?`) character in the URL, type in the query parameter key.
         ![Key typed into Url after question mark](./media/api-play-key.svg)
-        1. Type an equals (`=`) character after the key
-        1. Type in the value
+        1. Type an equals (`=`) character after the key.
+        1. Type in the value.
         ![Value typed into Url after the equals sign](./media/api-play-value.svg)
 
         The keys and values will automatically populate the parameter table in the interface.
 
-    1. Manually add query parameters by clicking the **+ Add param** button. This will add an empty parameter row to the table that you can type values into. The Url will be updated dynamically as values are entered.
+    1. Manually add query parameters by selecting **+ Add param**. This adds an empty parameter row to the table that you can type values into. The URL is updated dynamically as values are entered.
 
-1. Optionally provide a Body (if using all request methods except GET) by selecting the Body tab, then entering the body value in the editor control.
-1. Click **Send**
+1. Optionally provide a body (if using all request methods except GET) by selecting the **Body** tab, and then enter the body value in the editor control.
+1. Select **Send**.
 1. Observe the [response](#view-the-response) in the lower section.
 
 ### View the response
@@ -117,26 +117,27 @@ The response status provides quick metrics on the request:
 - Duration (in milliseconds)
 - Size (in kilobytes)
 
-The response body is displayed below the response status. You can click the copy icon to copy the response body to your clipboard.
+The response body is displayed below the response status. Select the copy icon to copy the response body to your clipboard.
 
 ### Save an API request
 
-You can save requests for quick access later on. Saved requests will store the request details (such as the request method and endpoint for OData request, or the selected plugin for Custom API and instant low code plugin), and the input parameters with associated values.
+You can save requests for quick access later. Saved requests store the request details, such as the request method and endpoint for OData request, or the selected plug-in for custom API and instant plug-in, and the input parameters with associated values.
+
+1. In the request screen, select **Save** in the top right corner of the page.
 
-1. In the request screen, click the save button in the top right corner of the page.
-1. A dialog appears with form fields.
+   A dialog appears with form fields.
 1. Provide a name for the request. A default value is provided based on the request details, but you can update the value.
     ![Save request dialog](./media/api-play-save.svg)
-1. Click **Save**
-1. The saved request appears in the left rail of the screen.
-    ![Saved requests appear in the left rail of the screen](media/api-play-saved-requests.svg)
+1. Select **Save**.
+1. The saved request appears in the left pane of the screen.
+    ![Saved requests appear in the left pane of the screen](media/api-play-saved-requests.svg)
 
 ### Load a saved request
 
-To load a saved request, select a request name. This will load the request screen with the request details filled in, including input parameters and values.
+To load a saved request, select a request name. This loads the request screen with the request details filled in, including input parameters and values.
 
 > [!NOTE]
-> You can only view saved requests that you have created.
+> You can only view saved requests that you've created.
 
 ## FAQs
 
@@ -150,9 +151,9 @@ Yes, the API playground tool only connects to the Dataverse Web API. No other se
 
 ### How does the API playground tool authenticate to the Dataverse Web API?
 
-The tool uses the authentication token of the logged in user that was required to play the Dataverse accelerator application.
+The tool uses the authentication token of the logged in user that is required to play the Dataverse accelerator application.
 
-### Is the API playround feature available in all environments?
+### Is the API playground feature available in all environments?
 
 The feature is delivered through the Dataverse accelerator and is available in all environments that have the app installed. The app is automatically installed in all new environments, but can also be installed in older environments by following the [install instructions](dataverse-accelerator.md#install-the-dataverse-accelerator).