Addressed review comments

Author: ninallam

articles/app-testing/playwright-workspaces/how-to-manage-authentication.md

@@ -55,13 +55,13 @@ To enable authentication using access tokens:
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 
-1. While running the tests, enable access token auth in the `playwright.service.config.ts` file in your setup. 
+While running the tests, enable access token auth in the `playwright.service.config.ts` file in your setup. 
 
     ```typescript
     import { getServiceConfig, ServiceAuth } from '@azure/playwright';
-
+    
     /* Learn more about service configuration at https://aka.ms/mpt/config */
     export default defineConfig(config, getServiceConfig( config {
         serviceAuthType: ServiceAuth.ACCESS_TOKEN
@@ -71,7 +71,7 @@ To enable authentication using access tokens:
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 
 1. While running the tests, enable access token auth in the setup file. 
 
@@ -107,37 +107,35 @@ To enable authentication using access tokens:
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+## Set up your environment.
 
-3. Set up your environment.
+### If you're using the **Playwright Test Runner**
 
-    To set up your environment, configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Ensure this environment variable is available in your setup where you are running tests.
+To set up your environment, configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Ensure this environment variable is available in your setup where you are running tests.
 
-    We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
+We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
 
-    1. Add the `dotenv` module to your project:
+1. Add the `dotenv` module to your project:
 
-        ```shell
-        npm i --save-dev dotenv
-        ```
+    ```shell
+    npm i --save-dev dotenv
+    ```
 
-    2. Create a `.env` file alongside the `playwright.config.ts` file in your Playwright project:
-        
-        ```
-        PLAYWRIGHT_SERVICE_ACCESS_TOKEN={MY-ACCESS-TOKEN}
-        ```
+2. Create a `.env` file alongside the `playwright.config.ts` file in your Playwright project:
+    
+    ```
+    PLAYWRIGHT_SERVICE_ACCESS_TOKEN={MY-ACCESS-TOKEN}
+    ```
 
-        Make sure to replace the `{MY-ACCESS-TOKEN}` text placeholder with the value you copied earlier.
+    Make sure to replace the `{MY-ACCESS-TOKEN}` text placeholder with the value you copied earlier.
 
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
-
-3. Set up your environment.
+### If you're using the **NUnit Test Runner**
 
-    To set up your environment, configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Ensure this environment variable is available in your setup where you are running tests.
+To set up your environment, configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Ensure this environment variable is available in your setup where you are running tests.
 
 ::: zone-end
 
@@ -147,15 +145,15 @@ Run Playwright tests against cloud-hosted browsers and publish the results to th
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 ```typescript
 npx playwright test --config=playwright.service.config.ts --workers=20
 ```
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 ```bash
 dotnet test -- NUnit.NumberOfTestWorkers=20
 ```

articles/app-testing/playwright-workspaces/how-to-test-local-applications.md

@@ -30,7 +30,7 @@ You can specify one or multiple networks by using a list of rules. For example,
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 
 You can configure the `exposeNetwork` option in `playwright.service.config.ts`. The following example shows how to expose the `localhost` network by using the [`<loopback>`](https://en.wikipedia.org/wiki/Loopback) rule. You can also replace `localhost` with a domain that you want to enable for the service.
 
@@ -60,7 +60,7 @@ npx playwright test --config=playwright.service.config.ts --workers=20
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 
 You can configure the `ExposeNetwork` option in the setup file. The following example shows how to expose the `localhost` network by using the [`<loopback>`](https://en.wikipedia.org/wiki/Loopback) rule. You can also replace `localhost` with a domain that you want to enable for the service. 
 

articles/app-testing/playwright-workspaces/how-to-use-service-config-file.md

@@ -17,7 +17,7 @@ zone_pivot_groups: playwright-workspaces
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 
 This article shows you how to use the options available in the `playwright.service.config.ts` file that was generated for you. 
 If you don't have this file in your code, follow [Quickstart: Run end-to-end tests at scale with Playwright Workspaces](./quickstart-run-end-to-end-tests.md) 
@@ -26,7 +26,7 @@ If you don't have this file in your code, follow [Quickstart: Run end-to-end tes
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 
 This article shows you how to use the options available in the `PlaywrightServiceSetup.cs` file. 
 If you don't have this file in your code, follow [Quickstart: Run end-to-end tests at scale with Playwright Workspaces](./quickstart-run-end-to-end-tests.md) 
@@ -42,7 +42,7 @@ If you don't have this file in your code, follow [Quickstart: Run end-to-end tes
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 
 Below is a complete example of a `playwright.service.config.ts` file showing all supported configuration options:
 
@@ -131,7 +131,7 @@ export default defineConfig(
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 
 
 Here's version of the setup file with all the available options:

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

@@ -67,7 +67,7 @@ To get the service endpoint URL and store it as a CI workflow secret, perform th
 
 ## Add service configuration file
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 
 If you don't have Playwright tests configured to run with the service, add a service configuration file to your repository. In the next step, you then specify this service configuration file on the Playwright CLI.
 
@@ -99,7 +99,7 @@ Update the `package.json` file in your repository to add details about Playwrigh
 
 ## Install service package
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 
 In your project, install Playwright Workspaces package. 
 
@@ -223,7 +223,7 @@ You can generate an access token from your Playwright workspace and use it in yo
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 Update the CI workflow definition to run your Playwright tests with the Playwright CLI. Pass the [service configuration file](#add-service-configuration-file) as an input parameter for the Playwright CLI. You configure your environment by specifying environment variables.
 
 1. Open the CI workflow definition.
@@ -324,7 +324,7 @@ Update the CI workflow definition to run your Playwright tests with the Playwrig
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 
 Update the CI workflow definition to run your Playwright tests with the Playwright NUnit CLI. You configure your environment by specifying environment variables.
 

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

@@ -70,7 +70,7 @@ To get started with running your Playwright tests on cloud browsers, you first n
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 
 To use the service, install the Playwright Workspaces package. 
 
@@ -86,7 +86,7 @@ If you already have this file, the package asks you to overwrite it.
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 
 To use the service, install the Playwright Workspaces package. 
 
@@ -118,7 +118,7 @@ To get the service endpoint URL, perform the following steps:
 
 ## Set up your environment
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 
 To set up your environment, you have to configure the `PLAYWRIGHT_SERVICE_URL` environment variable with the value you obtained in the previous steps.
 
@@ -144,7 +144,7 @@ We recommend that you use the `dotenv` module to manage your environment. With `
 
 ## Set up service configuration 
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 
 Create a file `PlaywrightServiceSetup.cs` in your project with the following content. 
 
@@ -202,7 +202,7 @@ You can generate an access token from your Playwright workspace and use it in yo
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 
 You've now prepared the configuration for running your Playwright tests in the cloud with Playwright Workspaces. You can either use the Playwright CLI to run your tests, or use the [Playwright Test Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright).
 
@@ -334,7 +334,7 @@ To run your Playwright test suite in Visual Studio Code with Playwright Workspac
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 
 Run Playwright tests against browsers managed by the service using the configuration you created above. 
 
@@ -364,13 +364,13 @@ With Playwright Workspaces, you can run with up to 50 parallel workers. Several
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**:
+### If you're using the **Playwright Test Runner**
 You can specify the number of parallel workers on the Playwright CLI command-line, or configure the `workers` property in the Playwright service configuration file.
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**:
+### If you're using the **NUnit Test Runner**
 You can specify the number of parallel workers on the Playwright CLI command-line, or configure the `NumberOfTestWorkers` property in the `.runsettings` file.
 ::: zone-end