Remove {{ code }} since all examples are in one..

... language.

Author: ankur22

docs/sources/k6/next/javascript-api/k6-browser/page/waitforurl.md

@@ -40,8 +40,6 @@ Events can be either:
 
 ### Examples
 
-{{< code >}}
-
 <!-- md-k6:skip -->
 
 ```javascript
@@ -82,14 +80,10 @@ export default async function () {
 }
 ```
 
-{{< /code >}}
-
 ### Valid usage patterns for waitForURL
 
 Use one of the following patterns to coordinate the action that triggers navigation with waiting for the final URL.
 
-{{< code >}}
-
 <!-- eslint-skip -->
 
 ```js
@@ -99,12 +93,8 @@ await Promise.all([
 ]);
 ```
 
-{{< /code >}}
-
 or
 
-{{< code >}}
-
 <!-- eslint-skip -->
 
 ```js
@@ -113,21 +103,15 @@ await page.locator('a[href="/my_messages.php"]').click();
 await navPromise;
 ```
 
-{{< /code >}}
-
 Unlike [waitForNavigation](https://grafana.com/docs/k6/<K6_VERSION>/javascript-api/k6-browser/page/waitfornavigation), `waitForURL` will first check whether it is already on the page with the given URL before proceeding to wait. If it is already there and the `waitUntil` condition has also been met, it will return straight away. This means that it is safe to do this:
 
-{{< code >}}
-
 <!-- eslint-skip -->
 
 ```js
 await page.locator('a[href="/my_messages.php"]').click();
 await page.waitForURL('https://quickpizza.grafana.com/my_messages.php');
 ```
 
-{{< /code >}}
-
 ### Best practices
 
 1. **Use appropriate matching**: Choose the right matching method based on your needs: