addressed comments

Author: vvs11

articles/playwright-testing/how-to-use-service-features.md

@@ -23,7 +23,7 @@ In this article, you learn how to use the features provided by Microsoft Playwri
 
 Microsoft Playwright Testing preview allows you to:
 - Accelerate build pipelines by running tests in parallel using cloud-hosted browsers.
-- Simplify troubleshooting by publishing test results and artifacts to the service, making them easily accessible through the service portal..
+- Simplify troubleshooting by publishing test results and artifacts to the service, making them easily accessible through the service portal.
 
 These features have their own pricing plans and are billed separately. You can choose to use either feature or both. These features can be enabled or disabled for the workspace or for any specific run. To know more about pricing, see [Microsoft Playwright Testing preview pricing](https://aka.ms/mpt/pricing)
 

articles/playwright-testing/includes/include-playwright-portal-view-test-results.md

@@ -19,11 +19,11 @@ ms.date: 09/23/2024
     - View detailed error logs, test steps, and attached artifacts such as screenshots or videos.
     - Navigate directly to the **Trace Viewer** for deeper analysis. 
 
-    :::image type="content" source="../media/include-playwright-portal-view-test-results/playwright-testing-open-test.png" alt-text="Screenshot that shows the preview of a test" lightbox="../media/include-playwright-portal-view-test-results/playwright-testing-open-test.png":::
+    :::image type="content" source="../media/include-playwright-portal-view-test-results/playwright-testing-open-test.png" alt-text="Screenshot that shows the preview of a test." lightbox="../media/include-playwright-portal-view-test-results/playwright-testing-open-test.png":::
 
 4. The Trace Viewer allows you to step through your test execution visually. You can:
     - Use the timeline to hover over individual steps, revealing the page state before and after each action.
     - Inspect detailed logs, DOM snapshots, network activity, errors, and console output for each step.
 
-    :::image type="content" source="../media/include-playwright-portal-view-test-results/playwright-testing-trace-viewer.png" alt-text="Screenshot that shows the trace viewer" lightbox="../media/include-playwright-portal-view-test-results/playwright-testing-trace-viewer.png":::
+    :::image type="content" source="../media/include-playwright-portal-view-test-results/playwright-testing-trace-viewer.png" alt-text="Screenshot that shows the trace viewer." lightbox="../media/include-playwright-portal-view-test-results/playwright-testing-trace-viewer.png":::
 

articles/playwright-testing/media/include-playwright-portal-view-test-results/playwright-testing-trace-viewer.png

@@ -65,17 +65,17 @@ If you haven't configured your Playwright tests yet for running them on cloud-ho
 
     Optionally, use the `playwright.service.config.ts` file in the [sample repository](https://github.com/microsoft/playwright-testing-service/blob/main/samples/get-started/playwright.service.config.ts).
 
-1. Add the following content to it:
+2. Add the following content to it:
 
     :::code language="typescript" source="~/playwright-testing-service/samples/get-started/playwright.service.config.ts":::
 
   By default, the service configuration enables you to:
   - Accelerate build pipelines by running tests in parallel using cloud-hosted browsers.
   - Simplify troubleshooting with easy access to test results and artifacts published to the service.
 
-  However, you can choose to use either of these feature or both. See [How to use service features](./how-to-use-service-features.md#manage-features-while-running-tests) and update the service configuration file as per your requirement. 
+  However, you can choose to use either of these features or both. See [How to use service features](./how-to-use-service-features.md#manage-features-while-running-tests) and update the service configuration file as per your requirement. 
 
-1. Save and commit the file to your source code repository.
+3. Save and commit the file to your source code repository.
 
 ## Update package.json file 
 

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

@@ -111,7 +111,7 @@ We recommend that you use the `dotenv` module to manage your environment. With `
     Make sure to replace the `{MY-REGION-ENDPOINT}` text placeholder with the value you copied earlier.
 
 
-## Set up Authentication
+## Set up authentication
 
 To publish test results and artifacts to your Microsoft Playwright Testing workspace, you need to authenticate the Playwright client where you're running the tests with the service. The client could be your local dev machine or CI machine.