Merge pull request #314922 from Abhinav-Premsekhar/main

Fix typo in load test configuration documentation

Author: prmerger-automator[bot]

articles/app-testing/load-testing/how-to-configure-load-test-cicd.md

@@ -296,7 +296,7 @@ Update your Azure Pipelines workflow to run a load test for your Azure load test
     ```
 
     Optionally, you can pass parameters or secrets to the load test by using the `env` or `secrets` property.
-    Set *`waitForCompletion: false`* to if you want to proceed without waiting for the load test run to complete.
+    Set *`waitForCompletion: false`* if you want to proceed without waiting for the load test run to complete.
 
 1. Use the `publish` task to publish the test results as artifacts in your Azure Pipelines workflow run.
 
@@ -350,7 +350,7 @@ Update your GitHub Actions workflow to run a load test for your Azure load testi
     ```
 
     Optionally, you can pass parameters or secrets to the load test by using the `env` or `secrets` property.
-    Set *`waitForCompletion: false`* to if you want to proceed without waiting for the load test run to complete.
+    Set *`waitForCompletion: false`* if you want to proceed without waiting for the load test run to complete.
 
 1. Use the `actions/upload-artifact` action to publish the test results as artifacts in your GitHub Actions workflow run.
 

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

@@ -246,11 +246,8 @@ When you run your load test, Azure Load Testing retrieves the client certificate
 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
-endpoint = os.getenv("endpoint") or "localhost"
 cert_dir = os.getenv("ALT_CERTIFICATES_DIR")
 
-base_url = "https://" + endpoint
-
 key_path = "client.key.pem"
 crt_path = "client.crt.pem"