updated sharding article (#4)

Author: vvs11

articles/playwright-testing/playwright-testing-reporting-with-sharding.md

@@ -19,7 +19,13 @@ Playwright's sharding enables you to split your test suite to run across multipl
 You can use Playwright Testing's reporting feature to get a consolidated report of a test run with sharding. You need to make sure you set the variable `PLAYWRIGHT_SERVICE_RUN_ID` so that it remains same across all shards. 
 
 > [!IMPORTANT]
-> Microsoft Playwright Testing's reporting feature is currently in invite-only preview. If you want to try it out, [submit a request for access to the preview](https://aka.ms/mpt/reporting-signup).
+> Microsoft Playwright Testing is currently in preview. For legal terms that apply to Azure features that are in beta, in preview, or otherwise not yet released into general availability, see the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
+## Prerequisites
+
+* An Azure account with an active subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+
+* Set up continuous end-to-end testing. Complete the [Quickstart: Set up continuous end-to-end testing with Microsoft Playwright Testing Preview](./quickstart-automate-end-to-end-testing.md) to set up continuous integration (CI) pipeline.
 
 
 ## Set up variables
@@ -63,7 +69,7 @@ jobs:
         node-version: 18
       # This step is to sign-in to Azure to run tests from GitHub Action workflow.
       # You can choose how set up Authentication to Azure from GitHub Actions, this is one example. 
-     - name: OIDC Login to Azure Public Cloud with AzPowershell (enableAzPSSession true) 
+     - name: Login to Azure with AzPowershell (enableAzPSSession true) 
       uses: azure/login@v2 
       with: 
         client-id: ${{ secrets.AZURE_CLIENT_ID }} 

articles/playwright-testing/quickstart-automate-end-to-end-testing.md

@@ -77,7 +77,7 @@ Update the `package.json` file in your repository to add details about Microsoft
 
 ```json
 "devDependencies": {
-    "@azure/microsoft-playwright-testing": "^1.0.0-beta.2"
+    "@azure/microsoft-playwright-testing": "^1.0.0-beta.3"
 }
 ```
 ## Update the workflow definition
@@ -96,7 +96,7 @@ Update the CI workflow definition to run your Playwright tests with the Playwrig
 
       # This step is to sign-in to Azure to run tests from GitHub Action workflow. 
       # You can choose how set up Authentication to Azure from GitHub Actions, this is one example. 
-    - name: OIDC Login to Azure Public Cloud with AzPowershell (enableAzPSSession true) 
+    - name: Login to Azure with AzPowershell (enableAzPSSession true) 
       uses: azure/login@v2 
       with: 
         client-id: ${{ secrets.AZURE_CLIENT_ID }} 
@@ -165,7 +165,7 @@ Update the CI workflow definition to run your Playwright tests with the Playwrig
     When the CI workflow is triggered, your Playwright tests run in your Microsoft Playwright Testing workspace on cloud-hosted browsers, across 20 parallel workers.
 
 > [!NOTE]
-> Reporting feature will be enabled by default for existing workspaces. This is being rolled out in stages and will take a few days. To avoid failures, confirm that `Rich diagnostics using reporting` setting is ON for your workspace before proceeding. See, [Enable reporting for workspace](./how-to-use-service-features.md#manage-feature-for-the-workspace).
+> Reporting feature is enabled by default for existing workspaces. This is being rolled out in stages and will take a few days. To avoid failures, confirm that `Rich diagnostics using reporting` setting is ON for your workspace before proceeding. See, [Enable reporting for workspace](./how-to-use-service-features.md#manage-feature-for-the-workspace).
 
 > [!CAUTION]
 > With Microsoft Playwright Testing, you get charged based on the number of total test minutes and test result published. If you're a first-time user or [getting started with a free trial](./how-to-try-playwright-testing-free.md), you might start with running a single test at scale instead of your full test suite to avoid exhausting your free test minutes and test results.

articles/playwright-testing/quickstart-run-end-to-end-tests.md

@@ -116,7 +116,7 @@ You've now prepared the configuration for running your Playwright tests in the c
 With Microsoft Playwright Testing, you get charged based on the number of total test minutes and number of test results published. If you're a first-time user or [getting started with a free trial](./how-to-try-playwright-testing-free.md), you might start with running a single test at scale instead of your full test suite to avoid exhausting your free trial limits.
 
 > [!NOTE]
-> Reporting feature will be enabled by default for existing workspaces. This is being rolled out in stages and will take a few days. To avoid failures, confirm that `Rich diagnostics using reporting` setting is ON for your workspace before proceeding. See, [Enable reporting for workspace](./how-to-use-service-features.md#manage-feature-for-the-workspace).
+> Reporting feature is enabled by default for existing workspaces. This is being rolled out in stages and will take a few days. To avoid failures, confirm that `Rich diagnostics using reporting` setting is ON for your workspace before proceeding. See, [Enable reporting for workspace](./how-to-use-service-features.md#manage-feature-for-the-workspace).
 
 After you validate that the test runs successfully, you can gradually increase the test load by running more tests with the service.