Update how-to-compare-multiple-test-runs.md

Update documented test runs comparison limits to show that up to ten test runs are allowed

Author: JhanviChauhan

articles/load-testing/how-to-compare-multiple-test-runs.md

@@ -12,13 +12,13 @@ ms.topic: how-to
 
 # Compare load test runs in Azure Load Testing
 
-In this article, you learn how you can compare test runs in Azure Load Testing. You can view trends across the last 10 test runs, or you can select and compare up to five individual test runs. Optionally, you can mark a test run as a baseline to compare against.
+In this article, you learn how you can compare test runs in Azure Load Testing. You can view trends across the last 10 test runs, or you can select and compare up to ten individual test runs. Optionally, you can mark a test run as a baseline to compare against.
 
 To identify regressions over time, you can use the client-side metrics trends of the last 10 test runs, such as the response time, error rate, and more. In combination with [CI/CD integration](./quickstart-add-load-test-cicd.md), the trends data might help you identify which application build introduced a performance issue.
 
 When you want to compare the client-side metrics trends against a specific reference test run, you can mark that test run as your baseline. For example, before you implement performance optimizations in your application, you might first create a baseline load test run, and then validate the effects of your optimizations against your baseline.
 
-To compare both client-side and server-side metrics, you can select up to five test runs, and compare them in the Azure Load Testing dashboard. The dashboard overlays the client-side and server-side metric graphs for each test run. By also comparing server-side application metrics in the dashboard, you can identify which application component was the root cause for a sudden performance degradation.
+To compare both client-side and server-side metrics, you can select up to ten test runs, and compare them in the Azure Load Testing dashboard. The dashboard overlays the client-side and server-side metric graphs for each test run. By also comparing server-side application metrics in the dashboard, you can identify which application component was the root cause for a sudden performance degradation.
 
 ## Prerequisites
 
@@ -28,7 +28,7 @@ To compare both client-side and server-side metrics, you can select up to five t
 
 ## Compare multiple load test runs
 
-To compare test runs in Azure Load Testing, you first have to select up to five runs within a load test. You can only compare runs that belong to the same load test. After you select the test runs you want to compare, you can visually compare the client-side and server-side metrics for each test run in the load test dashboard.
+To compare test runs in Azure Load Testing, you first have to select up to ten runs within a load test. You can only compare runs that belong to the same load test. After you select the test runs you want to compare, you can visually compare the client-side and server-side metrics for each test run in the load test dashboard.
 
 A test run needs to be in the *Done*, *Stopped*, or *Failed* state to compare it.
 
@@ -45,7 +45,7 @@ Use the following steps to select the test runs:
 
 1. Select two or more test runs, and then select **Compare** to compare test runs.
 
-    You can choose a maximum of five test runs to compare.
+    You can choose a maximum of ten test runs to compare.
 
     :::image type="content" source="media/how-to-compare-multiple-test-runs/compare-test-results-from-list.png" alt-text="Screenshot that shows a list of test runs and the 'Compare' button in the Azure portal." lightbox="media/how-to-compare-multiple-test-runs/compare-test-results-from-list.png":::