Addressing manual PR review comments

Author: Nagarjuna-Vipparthi

articles/load-testing/concept-load-testing-concepts.md

@@ -24,21 +24,21 @@ A virtual user runs a particular test case against your server application and r
 
 Apache JMeter also refers to virtual users as *threads*. In the JMeter test script, a *thread group* element lets you specify the pool of virtual users. Learn about [thread groups](https://jmeter.apache.org/usermanual/test_plan.html#thread_group) in the Apache JMeter documentation.
 
-Locust refers to virtual users as *users*. You can specify the users needed for your test in the web interface, as a command line argument, through an environment variable or through a configuration file. Learn about [configuration options](https://docs.locust.io/en/stable/configuration.html) in the Locust documentation. 
+Locust refers to virtual users as *users*. You can specify the users needed for your test in the web interface, as a command line argument, through an environment variable, or through a configuration file. For more information, see [configuration options](https://docs.locust.io/en/stable/configuration.html) in the Locust documentation. 
 
 The total number of virtual users for your load test depends on the number of virtual users in the test script and the number of [test engine instances](#test-engine).
 
 For JMeter based load tests, the formula is: Total virtual users = (virtual users in the JMX file) * (number of test engine instances).
 
-You can achieve the target number of virtual users by [configuring the number of test engine instances](./how-to-high-scale-load.md#test-engine-instances-and-virtual-users-for-JMeter-based-tests), the number of virtual users in the test script, or a combination of both.
+You can achieve the target number of virtual users by [configuring the number of test engine instances](./how-to-high-scale-load.md#test-engine-instances-and-virtual-users-for-jMeter-based-tests), the number of virtual users in the test script, or a combination of both.
 
-For Locust based load tests, the total number of virtual users is the number of users specified through any of the configuration options. You can then [configure the number of test engine instances](./how-to-high-scale-load.md#test-engine-instances-and-virtual-users-for-Locust-based-tests) required to generate the total number of users. 
+For Locust based load tests, the total number of virtual users is the number of users specified through any of the configuration options. You can then [configure the number of test engine instances](./how-to-high-scale-load.md#test-engine-instances-and-virtual-users-for-locust-based-tests) required to generate the total number of users. 
 
 ### Ramp-up time
 
 The ramp-up time is the amount of time to get to the full number of [virtual users](#virtual-users) for the load test. If the number of virtual users is 20, and the ramp-up time is 120 seconds, then it takes 120 seconds to get to all 20 virtual users. Each virtual user will start 6 (120/20) seconds after the previous user was started.
 
-For Locust, you can specify this using *spawn rate*. Spawn rate is the number of users added per second. If the number of users is 20 and the spawn rate is 2, 2 users will get added every second and it takes 10 seconds to get to all the 20 users. 
+For Locust, you can configure ramp-up using *spawn rate*. Spawn rate is the number of users added per second. For example, if the number of users is 20 and the spawn rate is 2, 2 users will get added every second and it takes 10 seconds to get to all the 20 users. 
 
 ### Response time
 
@@ -78,7 +78,7 @@ To run a load test for your application, you add a [test](#test) to your load te
 
 You can use [Azure role-based access control](./how-to-assign-roles.md) to grant access to your load testing resource and related artifacts.
 
-Azure Load Testing lets you [use managed identities](./how-to-use-a-managed-identity.md) to access Azure Key Vault for storing [load test secret parameters or certificates](./how-to-parameterize-load-tests.md), to access Azure monitor metrics for configuring failure criteria or to simulate managed identity based authentication flows. You can use either a user-assigned or system-assigned managed identity.
+Azure Load Testing allows you to [use managed identities](./how-to-use-a-managed-identity.md) for various purposes, such as accessing Azure Key Vault to store [load test secret parameters or certificates](./how-to-parameterize-load-tests.md), accessing Azure Monitor metrics to [configure failure criteria](./how-to-define-test-criteria.md#access-app-component-for-test-criteria-on-server-metrics), or simulating [managed identity-based authentication flows](./how-to-test-secured-endpoints.md#authenticate-with-a-managed-identity).
 
 ### Test
 

articles/load-testing/how-to-export-test-results.md

@@ -156,7 +156,7 @@ The following code snippet shows an example of how to use the backend listener f
 
 You can download the full [example of using the Azure Application Insights backend listener](https://github.com/Azure-Samples/azure-load-testing-samples/tree/main/jmeter-backend-listeners).
 
-For Locust-based tests, you can use [event hooks](https://docs.locust.io/en/stable/extending-locust.html) or [listener plugins](https://github.com/SvenskaSpel/locust-plugins?tab=readme-ov-file#listeners)
+For Locust-based tests, you can use [event hooks](https://docs.locust.io/en/stable/extending-locust.html) or [listener plugins](https://github.com/SvenskaSpel/locust-plugins?tab=readme-ov-file#listeners).
 
 ## Copy test artifacts from a storage account container
 

articles/load-testing/how-to-high-scale-load.md

@@ -31,7 +31,7 @@ Depending on the type of load test, URL-based, JMeter-based or Locust-based, you
 | URL-based (basic)    | Specify the target number of virtual users in the load test configuration. | Linear load pattern, based on the ramp-up time and number of virtual users. |
 | URL-based (advanced) | Specify the number of test engines and the number of virtual users per instance in the load test configuration. | Configure the load pattern (linear, step, spike). |
 | JMeter-based         | Specify the number of virtual users per instance in the test script. Specify the number of test engines in the load test configuration. | Configure the load pattern in the test script. |
-| Locust-based         | Specify the total number of users in the load test configuration, the locust configuration file or the test script. Specify the number of test engines in the load test configuration.  | Configure the load pattern in the test script. |
+| Locust-based         | Specify the total number of users in the load test configuration, the locust configuration file, or the test script. Specify the number of test engines in the load test configuration.  | Configure the load pattern in the test script. |
 
 ### Configure load parameters for URL-based tests
 
@@ -184,7 +184,7 @@ To specify the load parameters for a Locust-based load test:
 
 1. In the [Azure portal](https://portal.azure.com/), go to your Azure Load Testing resource.
 
-1. In the left navigation, select **Tests**  to view all tests.
+1. In the left navigation, select **Tests** to view all tests.
 
 1. In the list, select your load test, and then select **Edit**.
 
@@ -193,7 +193,7 @@ To specify the load parameters for a Locust-based load test:
     Alternately, you can also edit the test configuration from the test details page. To do so, select **Configure**, and then select **Test**.
 
 1. On the **Edit test** page, select the **Load** tab. Enter the values for the overall users required and overall spwan rate in the respective input boxes. 
-The engine instance count required to generate this load is automatically populated. If your test script is complex and resource intensive, use the **Engine instances** slider control to update the number of test engine instances, or enter the value directly in the input box.
+The engine instance count required to generate this load automatically populates. If your test script is complex and resource intensive, use the **Engine instances** slider control to update the number of test engine instances, or enter the value directly in the input box.
 
     :::image type="content" source="media/how-to-high-scale-load/edit-test-load-locust.png" alt-text="Screenshot of the 'Load' tab on the 'Edit test' pane for Locust-based tests." lightbox="media/how-to-high-scale-load/edit-test-load-locust.png":::
 
@@ -293,7 +293,7 @@ The location of the Azure Load Testing resource determines the location of the t
 
 ## Test engine instances and virtual users for Locust-based tests
 
-Configure the total number of users required for your load test. This represents the peak number of concurrent Locust users. You can configure this in the load configuration while creating a test in Azure Load Testing. You can also configure this in your test script or the Locust configuration file. We recommend running upto 500 users from a test engine instance.
+Configure the total number of users required for your load test. This represents the peak number of concurrent Locust users. You can configure this in the load configuration while creating a test in Azure Load Testing. You can also configure this in your test script or the Locust configuration file. We recommend running up to 500 users from a test engine instance.
 
 In Azure Load Testing, *test engine* instances are responsible for running the Locust script. All test engine instances run in parallel. You can configure the number of instances for a load test.
 

articles/load-testing/how-to-move-between-regions.md

@@ -51,7 +51,7 @@ To get started, export the ARM template for the Azure load testing resource and
 
     1. Select the ellipsis (**...**) for a test run, and then select **Download input file**.
 
-        The browser should now start downloading a zipped folder that contains all input files for the test, such as the [test configuration YAML file](./reference-test-config-yaml.md), the test script, and any configuration or data files.
+        The browser begins downloading a zipped folder that contains all input files for the test, such as the [test configuration YAML file](./reference-test-config-yaml.md), the test script, and any configuration or data files.
 
         :::image type="content" source="media/how-to-move-an-azure-load-testing-resource/download-input-artifacts.png" alt-text="Screenshot that shows how to download input files for a test.":::
 

articles/load-testing/how-to-read-csv-data.md

@@ -15,7 +15,7 @@ ms.custom: template-how-to
 
 In this article, you learn how to read data from a comma-separated value (CSV) file in test script with Azure Load Testing. Use data from an external CSV file to make your JMeter or Locust test script configurable. For example, you might iterate over all customers in a CSV file to pass the customer details into API request.
 
-In JMeter, you can use the [CSV Data Set Config element](https://jmeter.apache.org/usermanual/component_reference.html#CSV_Data_Set_Config) in your test script to read data from a CSV file. In Locust, you can open the CSV file in your test script, read the required data and pass it to the requests.  
+In JMeter, you can use the [CSV Data Set Config element](https://jmeter.apache.org/usermanual/component_reference.html#CSV_Data_Set_Config) in your test script to read data from a CSV file. In Locust, you can open the CSV file in your test script, read the required data, and pass it to the requests.  
 
 To read data from an external file in Azure Load Testing, you have to upload the external file alongside the test script in your load test. If you scale out your test across multiple parallel test engine instances, you can choose to split the input data evenly across these instances.
 

articles/load-testing/how-to-test-secured-endpoints.md

@@ -243,7 +243,7 @@ certificates:
 
 When you run your load test, Azure Load Testing retrieves the client certificate from Azure Key Vault, and automatically injects it in each JMeter web request. 
 
-For Locust-based tests, you can retrieve the certificate and use it in your tests script. The certificate configured in the load test configuration will be available in the `ALT_CERTIFICATES_DIR`. 
+For Locust-based tests, you can retrieve the certificate and use it in your tests script. The certificate configured in the load test configuration are available in the `ALT_CERTIFICATES_DIR`. 
 
 ```Python
 cert_dir = os.getenv("ALT_CERTIFICATES_DIR")

articles/load-testing/overview-what-is-azure-load-testing.md

@@ -44,7 +44,7 @@ Azure Load Testing can use the Apache JMeter or Locust testing frameworks and su
 - Databases via JDBC
 - TCP-based endpoints
 
-For JMeter, you can [use JMeter plugins](./how-to-use-jmeter-plugins.md) in your test script, you can load test more application types. For Locust, you can [use third party extensions](https://docs.locust.io/en/stable/extensions.html), Locust plugins or any other Python libraries to extend the cpabilities of Locust. 
+For JMeter, you can [use JMeter plugins](./how-to-use-jmeter-plugins.md) in your test script, you can load test more application types. For Locust, you can [use third party extensions](https://docs.locust.io/en/stable/extensions.html), Locust plugins, or any other Python libraries to extend the cpabilities of Locust. 
 
 With the quick test experience you can [test a single URL-based HTTP endpoint](./quickstart-create-and-run-load-test.md). By [uploading a JMeter script](how-to-create-and-run-load-test-with-jmeter-script.md), you can use all JMeter-supported communication protocols.
 

articles/load-testing/quickstart-add-load-test-cicd.md

@@ -29,7 +29,7 @@ If you want to automate your load test with GitHub Actions, learn how to [manual
 
 - Your Azure DevOps organization needs to have the [Azure Load Testing](https://marketplace.visualstudio.com/items?itemName=AzloadTest.AzloadTesting) extension installed.
 
-- A load testing resource, which contains a test. Create a [URL-based load test](./quickstart-create-and-run-load-test.md), [use an existing JMeter script](./how-to-create-and-run-load-test-with-jmeter-script.md) or [use an existing Locust script](./quickstart-create-run-load-test-with-locust.md) to create a load test.
+- A load testing resource, which contains a test. Create a [URL-based load test](./quickstart-create-and-run-load-test.md), [use an existing JMeter script](./how-to-create-and-run-load-test-with-jmeter-script.md), or [use an existing Locust script](./quickstart-create-run-load-test-with-locust.md) to create a load test.
 
 ## Configure a CI/CD pipeline