diff --git a/src/content/docs/synthetics/synthetic-monitoring/troubleshooting/simple-scripted-or-scripted-api-non-ping-errors.mdx b/src/content/docs/synthetics/synthetic-monitoring/troubleshooting/simple-scripted-or-scripted-api-non-ping-errors.mdx
index 141c7837de6..a473aec3841 100644
--- a/src/content/docs/synthetics/synthetic-monitoring/troubleshooting/simple-scripted-or-scripted-api-non-ping-errors.mdx
+++ b/src/content/docs/synthetics/synthetic-monitoring/troubleshooting/simple-scripted-or-scripted-api-non-ping-errors.mdx
@@ -123,7 +123,7 @@ Below are some of the most common non-ping monitor error messages.
 
     If it appears that a specific task is causing the job to wait an unacceptable amount of time, consider changing the method by which you’re accomplishing that task. For example, changing `$browser.findElement(locator: $driver.Locator)` to `$browser.waitForAndFindElement(locator: $driver.Locator [, timeout: number)` would assign the task its own configurable timeout.
 
-    If you have multiple steps where the `$browser.waitForAndFindElement(locator, timeout)` function is called, ensure that the the sum of the provided timeouts to these steps does not exceed 180 seconds. If you’re finding it difficult to accomplish this, then that is a sign that the monitor should probably be broken up into separate monitor scripts.
+    If you have multiple steps where the `$browser.waitForAndFindElement(locator, timeout)` function is called, ensure that the sum of the provided timeouts to these steps does not exceed 180 seconds. If you’re finding it difficult to accomplish this, then that is a sign that the monitor should probably be broken up into separate monitor scripts.
 
     ### Cause