From 6816b7063de0d1d1720d0726505218d2b87d94e8 Mon Sep 17 00:00:00 2001
From: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 26 Sep 2024 13:23:10 +0000
Subject: [PATCH] feat(roll): roll to ToT Playwright (26-09-24)

---
 dotnet/docs/api/class-accessibility.mdx       |   1 +
 dotnet/docs/api/class-apirequest.mdx          |   1 +
 dotnet/docs/api/class-browser.mdx             |   7 ++
 dotnet/docs/api/class-browsercontext.mdx      |  10 ++
 dotnet/docs/api/class-browsertype.mdx         |   5 +
 dotnet/docs/api/class-elementhandle.mdx       |   3 +
 dotnet/docs/api/class-frame.mdx               |   9 ++
 dotnet/docs/api/class-framelocator.mdx        |   1 +
 dotnet/docs/api/class-jshandle.mdx            |   1 +
 dotnet/docs/api/class-keyboard.mdx            |   3 +
 dotnet/docs/api/class-locator.mdx             |  24 ++++-
 dotnet/docs/api/class-mouse.mdx               |   1 +
 dotnet/docs/api/class-page.mdx                |  72 +++++++++----
 dotnet/docs/api/class-request.mdx             |   1 +
 dotnet/docs/api/class-touchscreen.mdx         |   1 +
 dotnet/docs/browsers.mdx                      |   2 +
 dotnet/docs/clock.mdx                         |  14 ++-
 dotnet/docs/debug.mdx                         |   1 +
 dotnet/docs/dialogs.mdx                       |   1 +
 dotnet/docs/docker.mdx                        |   2 +
 dotnet/docs/downloads.mdx                     |   2 +
 dotnet/docs/handles.mdx                       |   2 +
 dotnet/docs/input.mdx                         |   1 +
 dotnet/docs/locators.mdx                      |   3 +
 dotnet/docs/navigations.mdx                   |   1 +
 dotnet/docs/other-locators.mdx                |  16 +++
 dotnet/docs/selenium-grid.mdx                 |  15 ++-
 dotnet/docs/trace-viewer.mdx                  |   2 -
 java/docs/api/class-apirequest.mdx            |   1 +
 java/docs/api/class-browser.mdx               |   9 ++
 java/docs/api/class-browsercontext.mdx        |  10 ++
 java/docs/api/class-browsertype.mdx           |   5 +
 java/docs/api/class-elementhandle.mdx         |   3 +
 java/docs/api/class-frame.mdx                 |   9 ++
 java/docs/api/class-framelocator.mdx          |   1 +
 java/docs/api/class-jshandle.mdx              |   1 +
 java/docs/api/class-keyboard.mdx              |   3 +
 java/docs/api/class-locator.mdx               |  24 ++++-
 java/docs/api/class-mouse.mdx                 |   1 +
 java/docs/api/class-page.mdx                  |  71 +++++++++----
 java/docs/api/class-request.mdx               |   1 +
 java/docs/api/class-touchscreen.mdx           |   1 +
 java/docs/browsers.mdx                        |   2 +
 java/docs/ci.mdx                              |  12 +--
 java/docs/clock.mdx                           |  14 ++-
 java/docs/debug.mdx                           |   1 +
 java/docs/dialogs.mdx                         |   1 +
 java/docs/docker.mdx                          |  16 +--
 java/docs/downloads.mdx                       |   2 +
 java/docs/handles.mdx                         |   2 +
 java/docs/input.mdx                           |   1 +
 java/docs/intro.mdx                           |   2 +-
 java/docs/locators.mdx                        |   3 +
 java/docs/navigations.mdx                     |   1 +
 java/docs/other-locators.mdx                  |  16 +++
 java/docs/selenium-grid.mdx                   |  15 ++-
 java/docs/test-runners.mdx                    |   4 +-
 java/docs/trace-viewer.mdx                    |   2 -
 nodejs/docs/accessibility-testing.mdx         |   5 +-
 nodejs/docs/api/class-accessibility.mdx       |   1 +
 nodejs/docs/api/class-android.mdx             |   1 +
 nodejs/docs/api/class-androiddevice.mdx       |   2 +
 nodejs/docs/api/class-apirequest.mdx          |   1 +
 nodejs/docs/api/class-browser.mdx             |   9 ++
 nodejs/docs/api/class-browsercontext.mdx      |  12 +++
 nodejs/docs/api/class-browsertype.mdx         |   7 ++
 nodejs/docs/api/class-coverage.mdx            |   4 +
 nodejs/docs/api/class-elementhandle.mdx       |   3 +
 nodejs/docs/api/class-frame.mdx               |   9 ++
 nodejs/docs/api/class-framelocator.mdx        |   1 +
 nodejs/docs/api/class-jshandle.mdx            |   1 +
 nodejs/docs/api/class-keyboard.mdx            |   3 +
 nodejs/docs/api/class-locator.mdx             |  24 ++++-
 nodejs/docs/api/class-mouse.mdx               |   1 +
 nodejs/docs/api/class-page.mdx                |  72 +++++++++----
 nodejs/docs/api/class-request.mdx             |   1 +
 nodejs/docs/api/class-snapshotassertions.mdx  |   2 +
 nodejs/docs/api/class-test.mdx                |   3 +
 nodejs/docs/api/class-testconfig.mdx          |   1 +
 nodejs/docs/api/class-testinfo.mdx            |   1 +
 nodejs/docs/api/class-testoptions.mdx         |   3 +
 nodejs/docs/api/class-touchscreen.mdx         |   1 +
 nodejs/docs/browsers.mdx                      |   3 +
 nodejs/docs/canary-releases.mdx               |   5 +-
 nodejs/docs/chrome-extensions.mdx             |   2 +
 nodejs/docs/ci-intro.mdx                      |   1 +
 nodejs/docs/clock.mdx                         |  14 ++-
 nodejs/docs/debug.mdx                         |   1 +
 nodejs/docs/dialogs.mdx                       |   1 +
 nodejs/docs/docker.mdx                        |   2 +
 nodejs/docs/downloads.mdx                     |   2 +
 nodejs/docs/handles.mdx                       |   2 +
 nodejs/docs/input.mdx                         |   1 +
 nodejs/docs/locators.mdx                      |   3 +
 nodejs/docs/navigations.mdx                   |   1 +
 nodejs/docs/other-locators.mdx                |  16 +++
 nodejs/docs/selenium-grid.mdx                 |  15 ++-
 ...ce-workers-experimental-network-events.mdx |   2 +
 nodejs/docs/test-assertions.mdx               |   1 +
 nodejs/docs/test-global-setup-teardown.mdx    |   1 +
 nodejs/docs/test-parallel.mdx                 |   2 +
 nodejs/docs/test-parameterize.mdx             |   1 +
 nodejs/docs/test-retries.mdx                  |   1 +
 nodejs/docs/test-use-options.mdx              |   1 +
 nodejs/docs/testing-library.mdx               |   1 +
 nodejs/docs/trace-viewer.mdx                  |   2 -
 python/docs/api/class-accessibility.mdx       |   1 +
 python/docs/api/class-apirequest.mdx          |   1 +
 python/docs/api/class-browser.mdx             |   7 ++
 python/docs/api/class-browsercontext.mdx      |  16 +++
 python/docs/api/class-browsertype.mdx         |   4 +
 python/docs/api/class-dialog.mdx              |   1 +
 python/docs/api/class-elementhandle.mdx       |   4 +
 python/docs/api/class-frame.mdx               |  10 ++
 python/docs/api/class-framelocator.mdx        |   1 +
 python/docs/api/class-jshandle.mdx            |   1 +
 python/docs/api/class-keyboard.mdx            |   5 +
 python/docs/api/class-locator.mdx             |  24 ++++-
 python/docs/api/class-mouse.mdx               |   1 +
 python/docs/api/class-page.mdx                | 100 ++++++++++++++----
 python/docs/api/class-request.mdx             |   1 +
 python/docs/api/class-touchscreen.mdx         |   1 +
 python/docs/api/class-websocket.mdx           |   1 +
 python/docs/browsers.mdx                      |   2 +
 python/docs/chrome-extensions.mdx             |   2 +
 python/docs/clock.mdx                         |  14 ++-
 python/docs/debug.mdx                         |   1 +
 python/docs/dialogs.mdx                       |   3 +
 python/docs/docker.mdx                        |   2 +
 python/docs/downloads.mdx                     |   2 +
 python/docs/handles.mdx                       |   2 +
 python/docs/input.mdx                         |   2 +
 python/docs/library.mdx                       |   1 +
 python/docs/locators.mdx                      |  11 ++
 python/docs/navigations.mdx                   |   1 +
 python/docs/other-locators.mdx                |  19 ++++
 python/docs/selenium-grid.mdx                 |  15 ++-
 python/docs/trace-viewer.mdx                  |   2 -
 python/docs/videos.mdx                        |   1 +
 src/documentation.js                          |   7 +-
 src/markdown.js                               |  26 +++--
 141 files changed, 854 insertions(+), 123 deletions(-)

diff --git a/dotnet/docs/api/class-accessibility.mdx b/dotnet/docs/api/class-accessibility.mdx
index 3567eebc71..fd17197b10 100644
--- a/dotnet/docs/api/class-accessibility.mdx
+++ b/dotnet/docs/api/class-accessibility.mdx
@@ -34,6 +34,7 @@ This method is deprecated. Please use other libraries such as [Axe](https://www.
 Captures the current state of the accessibility tree. The returned object represents the root accessible node of the page.
 
 :::note
+
 The Chromium accessibility tree contains nodes that go unused on most platforms and by most screen readers. Playwright will discard them as well for an easier to process tree, unless [InterestingOnly](/api/class-accessibility.mdx#accessibility-snapshot-option-interesting-only) is set to `false`.
 :::
 
diff --git a/dotnet/docs/api/class-apirequest.mdx b/dotnet/docs/api/class-apirequest.mdx
index b03c2e3a9e..786cc84283 100644
--- a/dotnet/docs/api/class-apirequest.mdx
+++ b/dotnet/docs/api/class-apirequest.mdx
@@ -67,6 +67,7 @@ await ApiRequest.NewContextAsync(options);
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
diff --git a/dotnet/docs/api/class-browser.mdx b/dotnet/docs/api/class-browser.mdx
index 9bf5205d13..39641cbc10 100644
--- a/dotnet/docs/api/class-browser.mdx
+++ b/dotnet/docs/api/class-browser.mdx
@@ -51,6 +51,7 @@ In case this browser is obtained using [BrowserType.LaunchAsync()](/api/class-br
 In case this browser is connected to, clears all created contexts belonging to this browser and disconnects from the browser server.
 
 :::note
+
 This is similar to force quitting the browser. Therefore, you should call [BrowserContext.CloseAsync()](/api/class-browsercontext.mdx#browser-context-close) on any [BrowserContext]'s you explicitly created earlier with [Browser.NewContextAsync()](/api/class-browser.mdx#browser-new-context) **before** calling [Browser.CloseAsync()](/api/class-browser.mdx#browser-close).
 :::
 
@@ -116,6 +117,7 @@ Browser.IsConnected
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.NewBrowserCDPSessionAsync</x-search>
 
 :::note
+
 CDP Sessions are only supported on Chromium-based browsers.
 :::
 
@@ -139,6 +141,7 @@ await Browser.NewBrowserCDPSessionAsync();
 Creates a new browser context. It won't share cookies/cache with other browser contexts.
 
 :::note
+
 If directly using this method to create [BrowserContext]s, it is best practice to explicitly close the returned context via [BrowserContext.CloseAsync()](/api/class-browsercontext.mdx#browser-context-close) when your code is done with the [BrowserContext], and before calling [Browser.CloseAsync()](/api/class-browser.mdx#browser-close). This will ensure the `context` is closed gracefully and any artifacts—like HARs and videos—are fully flushed and saved.
 :::
 
@@ -205,6 +208,7 @@ await browser.CloseAsync();
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
@@ -349,6 +353,7 @@ await browser.CloseAsync();
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `ViewportSize.NoViewport` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation.mdx#viewport).
     
     :::note
+    
     The `ViewportSize.NoViewport` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
@@ -418,6 +423,7 @@ await Browser.NewPageAsync(options);
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
@@ -562,6 +568,7 @@ await Browser.NewPageAsync(options);
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `ViewportSize.NoViewport` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation.mdx#viewport).
     
     :::note
+    
     The `ViewportSize.NoViewport` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
diff --git a/dotnet/docs/api/class-browsercontext.mdx b/dotnet/docs/api/class-browsercontext.mdx
index fa87d6e9f0..52c3809a3c 100644
--- a/dotnet/docs/api/class-browsercontext.mdx
+++ b/dotnet/docs/api/class-browsercontext.mdx
@@ -119,6 +119,7 @@ The order of evaluation of multiple scripts installed via [BrowserContext.AddIni
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.BackgroundPages</x-search>
 
 :::note
+
 Background pages are only supported on Chromium-based browsers.
 :::
 
@@ -214,6 +215,7 @@ await context.ClearPermissionsAsync();
 Closes the browser context. All the pages that belong to the browser context will be closed.
 
 :::note
+
 The default browser context cannot be closed.
 :::
 
@@ -443,6 +445,7 @@ await BrowserContext.GrantPermissionsAsync(permissions, options);
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.NewCDPSessionAsync</x-search>
 
 :::note
+
 CDP sessions are only supported on Chromium-based browsers.
 :::
 
@@ -505,6 +508,7 @@ BrowserContext.Pages
 Routing provides the capability to modify network requests that are made by any page in the browser context. Once route is enabled, every request matching the url pattern will stall unless it's continued, fulfilled or aborted.
 
 :::note
+
 [BrowserContext.RouteAsync()](/api/class-browsercontext.mdx#browser-context-route) will not intercept requests intercepted by Service Worker. See [this](https://github.com/microsoft/playwright/issues/1090) issue. We recommend disabling Service Workers when using request interception by setting [ServiceWorkers](/api/class-browser.mdx#browser-new-context-option-service-workers) to `'block'`.
 :::
 
@@ -547,6 +551,7 @@ Page routes (set up with [Page.RouteAsync()](/api/class-page.mdx#page-route)) ta
 To remove a route with its handler you can use [BrowserContext.UnrouteAsync()](/api/class-browsercontext.mdx#browser-context-unroute).
 
 :::note
+
 Enabling routing disables http cache.
 :::
 
@@ -768,6 +773,7 @@ This setting will change the default maximum navigation time for the following m
 * [Page.RunAndWaitForNavigationAsync()](/api/class-page.mdx#page-wait-for-navigation)
 
 :::note
+
 [Page.SetDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) and [Page.SetDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout) take priority over [BrowserContext.SetDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout).
 :::
 
@@ -791,6 +797,7 @@ BrowserContext.SetDefaultNavigationTimeout(timeout);
 This setting will change the default maximum time for all the methods accepting [timeout](/api/class-browsercontext.mdx#browser-context-set-default-timeout-option-timeout) option.
 
 :::note
+
 [Page.SetDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout), [Page.SetDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout) and [BrowserContext.SetDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout) take priority over [BrowserContext.SetDefaultTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout).
 :::
 
@@ -814,6 +821,7 @@ BrowserContext.SetDefaultTimeout(timeout);
 The extra HTTP headers will be sent with every request initiated by any page in the context. These headers are merged with page-specific extra HTTP headers set with [Page.SetExtraHTTPHeadersAsync()](/api/class-page.mdx#page-set-extra-http-headers). If page overrides a particular header, page-specific header value will be used instead of the browser context header value.
 
 :::note
+
 [BrowserContext.SetExtraHTTPHeadersAsync()](/api/class-browsercontext.mdx#browser-context-set-extra-http-headers) does not guarantee the order of headers in the outgoing requests.
 :::
 
@@ -1022,6 +1030,7 @@ BrowserContext.Tracing
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.event BackgroundPage</x-search>
 
 :::note
+
 Only works with Chromium browser's persistent context.
 :::
 
@@ -1172,6 +1181,7 @@ BrowserContext.Request += async (_, request) => {};
 Emitted when a request fails, for example by timing out. To only listen for failed requests from a particular page, use [Page.RequestFailed](/api/class-page.mdx#page-event-request-failed).
 
 :::note
+
 HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with [BrowserContext.RequestFinished](/api/class-browsercontext.mdx#browser-context-event-request-finished) event and not with [BrowserContext.RequestFailed](/api/class-browsercontext.mdx#browser-context-event-request-failed).
 :::
 
diff --git a/dotnet/docs/api/class-browsertype.mdx b/dotnet/docs/api/class-browsertype.mdx
index 3eeee6ebcb..a11a73a8a3 100644
--- a/dotnet/docs/api/class-browsertype.mdx
+++ b/dotnet/docs/api/class-browsertype.mdx
@@ -87,6 +87,7 @@ This method attaches Playwright to an existing browser instance using the Chrome
 The default browser context is accessible via [Browser.Contexts](/api/class-browser.mdx#browser-contexts).
 
 :::note
+
 Connecting over the Chrome DevTools Protocol is only supported for Chromium-based browsers.
 :::
 
@@ -162,6 +163,7 @@ var browser = await playwright.Chromium.LaunchAsync(new() {
   - `Args` [IEnumerable]?&lt;[string]&gt; *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-type-launch-option-args"/><a href="#browser-type-launch-option-args" class="list-anchor">#</a>
     
     :::warning
+    
     Use custom browser args at your own risk, as some of them may break Playwright functionality.
     :::
     
@@ -265,6 +267,7 @@ await BrowserType.LaunchPersistentContextAsync(userDataDir, options);
   - `Args` [IEnumerable]?&lt;[string]&gt; *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-type-launch-persistent-context-option-args"/><a href="#browser-type-launch-persistent-context-option-args" class="list-anchor">#</a>
     
     :::warning
+    
     Use custom browser args at your own risk, as some of them may break Playwright functionality.
     :::
     
@@ -317,6 +320,7 @@ await BrowserType.LaunchPersistentContextAsync(userDataDir, options);
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
@@ -502,6 +506,7 @@ await BrowserType.LaunchPersistentContextAsync(userDataDir, options);
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `ViewportSize.NoViewport` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation.mdx#viewport).
     
     :::note
+    
     The `ViewportSize.NoViewport` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
diff --git a/dotnet/docs/api/class-elementhandle.mdx b/dotnet/docs/api/class-elementhandle.mdx
index f13c690611..c4472b5197 100644
--- a/dotnet/docs/api/class-elementhandle.mdx
+++ b/dotnet/docs/api/class-elementhandle.mdx
@@ -11,6 +11,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ElementHandle represents an in-page DOM element. ElementHandles can be created with the [Page.QuerySelectorAsync()](/api/class-page.mdx#page-query-selector) method.
 
 :::warning[Discouraged]
+
 The use of ElementHandle is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -308,6 +309,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [Timeout](/api/class-elementhandle.mdx#element-handle-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `elementHandle.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -1346,6 +1348,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [Timeout](/api/class-elementhandle.mdx#element-handle-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `elementHandle.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
diff --git a/dotnet/docs/api/class-frame.mdx b/dotnet/docs/api/class-frame.mdx
index 5702e3ceda..fa9dd74c8a 100644
--- a/dotnet/docs/api/class-frame.mdx
+++ b/dotnet/docs/api/class-frame.mdx
@@ -496,6 +496,7 @@ await page
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
@@ -684,6 +685,7 @@ The method will throw an error if:
 The method will not throw an error when any valid HTTP status code is returned by the remote server, including 404 "Not Found" and 500 "Internal Server Error".  The status code for such responses can be retrieved by calling [Response.Status](/api/class-response.mdx#response-status).
 
 :::note
+
 The method either throws an error or returns a main resource response. The only exceptions are navigation to `about:blank` or navigation to the same URL with a different hash, which would succeed and return `null`.
 :::
 
@@ -821,6 +823,7 @@ Returns frame's name attribute as specified in the tag.
 If the name is empty, returns the id attribute instead.
 
 :::note
+
 This value is calculated once when the frame is created, and will not update if the attribute is changed later.
 :::
 
@@ -999,6 +1002,7 @@ Waits for the required load state to be reached.
 This returns when the frame reaches a required load state, `load` by default. The navigation must have been committed when this method is called. If current document has already reached the required state, resolves immediately.
 
 :::note
+
 Most of the time, this method is not needed because Playwright [auto-waits before every action](../actionability.mdx).
 :::
 
@@ -1225,6 +1229,7 @@ This method double clicks an element matching [selector](/api/class-frame.mdx#fr
 When all steps combined have not finished during the specified [Timeout](/api/class-frame.mdx#frame-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `frame.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -1996,6 +2001,7 @@ Use locator-based [Frame.Locator()](/api/class-frame.mdx#frame-locator) instead.
 Returns the ElementHandle pointing to the frame element.
 
 :::caution
+
 The use of [ElementHandle] is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -2035,6 +2041,7 @@ Use locator-based [Frame.Locator()](/api/class-frame.mdx#frame-locator) instead.
 Returns the ElementHandles pointing to the frame elements.
 
 :::caution
+
 The use of [ElementHandle] is discouraged, use [Locator] objects instead.
 :::
 
@@ -2379,6 +2386,7 @@ This method taps an element matching [selector](/api/class-frame.mdx#frame-tap-o
 When all steps combined have not finished during the specified [Timeout](/api/class-frame.mdx#frame-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `frame.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
@@ -2594,6 +2602,7 @@ Use web assertions that assert visibility or a locator-based [Locator.WaitForAsy
 Returns when element specified by selector satisfies [State](/api/class-frame.mdx#frame-wait-for-selector-option-state) option. Returns `null` if waiting for `hidden` or `detached`.
 
 :::note
+
 Playwright automatically waits for element to be ready before performing an action. Using [Locator] objects and web-first assertions make the code wait-for-selector-free.
 :::
 
diff --git a/dotnet/docs/api/class-framelocator.mdx b/dotnet/docs/api/class-framelocator.mdx
index b2c4bf8693..af26c54057 100644
--- a/dotnet/docs/api/class-framelocator.mdx
+++ b/dotnet/docs/api/class-framelocator.mdx
@@ -216,6 +216,7 @@ await page
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
diff --git a/dotnet/docs/api/class-jshandle.mdx b/dotnet/docs/api/class-jshandle.mdx
index bc58e678c5..685b735293 100644
--- a/dotnet/docs/api/class-jshandle.mdx
+++ b/dotnet/docs/api/class-jshandle.mdx
@@ -169,6 +169,7 @@ await JsHandle.GetPropertyAsync(propertyName);
 Returns a JSON representation of the object. If the object has a `toJSON` function, it **will not be called**.
 
 :::note
+
 The method will return an empty JSON object if the referenced object is not stringifiable. It will throw an error if the object has circular references.
 :::
 
diff --git a/dotnet/docs/api/class-keyboard.mdx b/dotnet/docs/api/class-keyboard.mdx
index 020e4ddac6..ee60dbbf68 100644
--- a/dotnet/docs/api/class-keyboard.mdx
+++ b/dotnet/docs/api/class-keyboard.mdx
@@ -70,6 +70,7 @@ If [key](/api/class-keyboard.mdx#keyboard-down-option-key) is a modifier key, `S
 After the key is pressed once, subsequent calls to [Keyboard.DownAsync()](/api/class-keyboard.mdx#keyboard-down) will have [repeat](https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/repeat) set to true. To release the key, use [Keyboard.UpAsync()](/api/class-keyboard.mdx#keyboard-up).
 
 :::note
+
 Modifier keys DO influence `keyboard.down`. Holding down `Shift` will type the text in upper case.
 :::
 
@@ -120,6 +121,7 @@ Modifier keys DO NOT effect `keyboard.insertText`. Holding down `Shift` will not
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>keyboard.PressAsync</x-search>
 
 :::tip
+
 In most cases, you should use [Locator.PressAsync()](/api/class-locator.mdx#locator-press) instead.
 :::
 
@@ -169,6 +171,7 @@ Shortcut for [Keyboard.DownAsync()](/api/class-keyboard.mdx#keyboard-down) and [
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>keyboard.TypeAsync</x-search>
 
 :::caution
+
 In most cases, you should use [Locator.FillAsync()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.PressSequentiallyAsync()](/api/class-locator.mdx#locator-press-sequentially).
 :::
 
diff --git a/dotnet/docs/api/class-locator.mdx b/dotnet/docs/api/class-locator.mdx
index 795d1ebcb6..8465be00a6 100644
--- a/dotnet/docs/api/class-locator.mdx
+++ b/dotnet/docs/api/class-locator.mdx
@@ -23,7 +23,12 @@ Locators are the central piece of Playwright's auto-waiting and retry-ability. I
 When the locator points to a list of elements, this returns an array of locators, pointing to their respective elements.
 
 :::note
-[Locator.AllAsync()](/api/class-locator.mdx#locator-all) does not wait for elements to match the locator, and instead immediately returns whatever is present in the page.  When the list of elements changes dynamically, [Locator.AllAsync()](/api/class-locator.mdx#locator-all) will produce unpredictable and flaky results.  When the list of elements is stable, but loaded dynamically, wait for the full list to finish loading before calling [Locator.AllAsync()](/api/class-locator.mdx#locator-all).
+
+[Locator.AllAsync()](/api/class-locator.mdx#locator-all) does not wait for elements to match the locator, and instead immediately returns whatever is present in the page.
+
+When the list of elements changes dynamically, [Locator.AllAsync()](/api/class-locator.mdx#locator-all) will produce unpredictable and flaky results.
+
+When the list of elements is stable, but loaded dynamically, wait for the full list to finish loading before calling [Locator.AllAsync()](/api/class-locator.mdx#locator-all).
 :::
 
 **Usage**
@@ -45,6 +50,7 @@ foreach (var li in await page.GetByRole("listitem").AllAsync())
 Returns an array of `node.innerText` values for all matching nodes.
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [Expect(Locator).ToHaveTextAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) with [UseInnerText](/api/class-locatorassertions.mdx#locator-assertions-to-have-text-option-use-inner-text) option to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -66,6 +72,7 @@ var texts = await page.GetByRole(AriaRole.Link).AllInnerTextsAsync();
 Returns an array of `node.textContent` values for all matching nodes.
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [Expect(Locator).ToHaveTextAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -381,6 +388,7 @@ await frameLocator.GetByRole(AriaRole.Button).ClickAsync();
 Returns the number of elements matching the locator.
 
 :::warning[Asserting count]
+
 If you need to assert the number of elements on the page, prefer [Expect(Locator).ToHaveCountAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-have-count) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -459,6 +467,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [Timeout](/api/class-locator.mdx#locator-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `element.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -863,6 +872,7 @@ await locator.ClickAsync();
 Returns the matching element's attribute value.
 
 :::warning[Asserting attributes]
+
 If you need to assert an element's attribute, prefer [Expect(Locator).ToHaveAttributeAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-have-attribute) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1041,6 +1051,7 @@ await page
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
@@ -1319,6 +1330,7 @@ await Locator.InnerHTMLAsync(options);
 Returns the [`element.innerText`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/innerText).
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [Expect(Locator).ToHaveTextAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) with [UseInnerText](/api/class-locatorassertions.mdx#locator-assertions-to-have-text-option-use-inner-text) option to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1346,6 +1358,7 @@ await Locator.InnerTextAsync(options);
 Returns the value for the matching `<input>` or `<textarea>` or `<select>` element.
 
 :::warning[Asserting value]
+
 If you need to assert input value, prefer [Expect(Locator).ToHaveValueAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-have-value) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1377,6 +1390,7 @@ Throws elements that are not an input, textarea or a select. However, if the ele
 Returns whether the element is checked. Throws if the element is not a checkbox or radio input.
 
 :::warning[Asserting checked state]
+
 If you need to assert that checkbox is checked, prefer [Expect(Locator).ToBeCheckedAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-be-checked) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1404,6 +1418,7 @@ var isChecked = await page.GetByRole(AriaRole.Checkbox).IsCheckedAsync();
 Returns whether the element is disabled, the opposite of [enabled](../actionability.mdx#enabled).
 
 :::warning[Asserting disabled state]
+
 If you need to assert that an element is disabled, prefer [Expect(Locator).ToBeDisabledAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-be-disabled) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1431,6 +1446,7 @@ Boolean disabled = await page.GetByRole(AriaRole.Button).IsDisabledAsync();
 Returns whether the element is [editable](../actionability.mdx#editable).
 
 :::warning[Asserting editable state]
+
 If you need to assert that an element is editable, prefer [Expect(Locator).ToBeEditableAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-be-editable) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1458,6 +1474,7 @@ Boolean editable = await page.GetByRole(AriaRole.Textbox).IsEditableAsync();
 Returns whether the element is [enabled](../actionability.mdx#enabled).
 
 :::warning[Asserting enabled state]
+
 If you need to assert that an element is enabled, prefer [Expect(Locator).ToBeEnabledAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-be-enabled) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1485,6 +1502,7 @@ Boolean enabled = await page.GetByRole(AriaRole.Button).IsEnabledAsync();
 Returns whether the element is hidden, the opposite of [visible](../actionability.mdx#visible).
 
 :::warning[Asserting visibility]
+
 If you need to assert that element is hidden, prefer [Expect(Locator).ToBeHiddenAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-be-hidden) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1515,6 +1533,7 @@ Boolean hidden = await page.GetByRole(AriaRole.Button).IsHiddenAsync();
 Returns whether the element is [visible](../actionability.mdx#visible).
 
 :::warning[Asserting visibility]
+
 If you need to assert that element is visible, prefer [Expect(Locator).ToBeVisibleAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-be-visible) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1724,6 +1743,7 @@ Shortcuts such as `key: "Control+o"`, `key: "Control++` or `key: "Control+Shift+
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.38</font><x-search>locator.PressSequentiallyAsync</x-search>
 
 :::tip
+
 In most cases, you should use [Locator.FillAsync()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page.
 :::
 
@@ -2152,6 +2172,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [Timeout](/api/class-locator.mdx#locator-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `element.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
@@ -2164,6 +2185,7 @@ When all steps combined have not finished during the specified [Timeout](/api/cl
 Returns the [`node.textContent`](https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent).
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [Expect(Locator).ToHaveTextAsync()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
diff --git a/dotnet/docs/api/class-mouse.mdx b/dotnet/docs/api/class-mouse.mdx
index ff849e2d4e..b40daf980d 100644
--- a/dotnet/docs/api/class-mouse.mdx
+++ b/dotnet/docs/api/class-mouse.mdx
@@ -181,6 +181,7 @@ await Mouse.UpAsync(options);
 Dispatches a `wheel` event. This method is usually used to manually scroll the page. See [scrolling](../input.mdx#scrolling) for alternative ways to scroll.
 
 :::note
+
 Wheel events may cause scrolling if they are not handled, and this method does not wait for the scrolling to finish before returning.
 :::
 
diff --git a/dotnet/docs/api/class-page.mdx b/dotnet/docs/api/class-page.mdx
index 46c331277a..0e5debf475 100644
--- a/dotnet/docs/api/class-page.mdx
+++ b/dotnet/docs/api/class-page.mdx
@@ -106,7 +106,12 @@ Things to keep in mind:
 * You can register multiple handlers. However, only a single handler will be running at a time. Make sure the actions within a handler don't depend on another handler.
 
 :::warning
-Running the handler will alter your page state mid-test. For example it will change the currently focused element and move the mouse. Make sure that actions that run after the handler are self-contained and do not rely on the focus and mouse state being unchanged. <br /> <br /> For example, consider a test that calls [Locator.FocusAsync()](/api/class-locator.mdx#locator-focus) followed by [Keyboard.PressAsync()](/api/class-keyboard.mdx#keyboard-press). If your handler clicks a button between these two actions, the focused element most likely will be wrong, and key press will happen on the unexpected element. Use [Locator.PressAsync()](/api/class-locator.mdx#locator-press) instead to avoid this problem. <br /> <br /> Another example is a series of mouse actions, where [Mouse.MoveAsync()](/api/class-mouse.mdx#mouse-move) is followed by [Mouse.DownAsync()](/api/class-mouse.mdx#mouse-down). Again, when the handler runs between these two actions, the mouse position will be wrong during the mouse down. Prefer self-contained actions like [Locator.ClickAsync()](/api/class-locator.mdx#locator-click) that do not rely on the state being unchanged by a handler.
+
+Running the handler will alter your page state mid-test. For example it will change the currently focused element and move the mouse. Make sure that actions that run after the handler are self-contained and do not rely on the focus and mouse state being unchanged.
+
+For example, consider a test that calls [Locator.FocusAsync()](/api/class-locator.mdx#locator-focus) followed by [Keyboard.PressAsync()](/api/class-keyboard.mdx#keyboard-press). If your handler clicks a button between these two actions, the focused element most likely will be wrong, and key press will happen on the unexpected element. Use [Locator.PressAsync()](/api/class-locator.mdx#locator-press) instead to avoid this problem.
+
+Another example is a series of mouse actions, where [Mouse.MoveAsync()](/api/class-mouse.mdx#mouse-move) is followed by [Mouse.DownAsync()](/api/class-mouse.mdx#mouse-down). Again, when the handler runs between these two actions, the mouse position will be wrong during the mouse down. Prefer self-contained actions like [Locator.ClickAsync()](/api/class-locator.mdx#locator-click) that do not rely on the state being unchanged by a handler.
 :::
 
 **Usage**
@@ -265,6 +270,7 @@ If [RunBeforeUnload](/api/class-page.mdx#page-close-option-run-before-unload) is
 By default, `page.close()` **does not** run `beforeunload` handlers.
 
 :::note
+
 if [RunBeforeUnload](/api/class-page.mdx#page-close-option-run-before-unload) is passed as true, a `beforeunload` dialog might be summoned and should be handled manually via [Page.Dialog](/api/class-page.mdx#page-event-dialog) event.
 :::
 
@@ -547,6 +553,7 @@ The first argument of the [callback](/api/class-page.mdx#page-expose-binding-opt
 See [BrowserContext.ExposeBindingAsync()](/api/class-browsercontext.mdx#browser-context-expose-binding) for the context-wide version.
 
 :::note
+
 Functions installed via [Page.ExposeBindingAsync()](/api/class-page.mdx#page-expose-binding) survive navigations.
 :::
 
@@ -616,6 +623,7 @@ If the [callback](/api/class-page.mdx#page-expose-function-option-callback) retu
 See [BrowserContext.ExposeFunctionAsync()](/api/class-browsercontext.mdx#browser-context-expose-function) for context-wide exposed function.
 
 :::note
+
 Functions installed via [Page.ExposeFunctionAsync()](/api/class-page.mdx#page-expose-function) survive navigations.
 :::
 
@@ -673,23 +681,6 @@ class PageExamples
 
 ---
 
-### ForceGarbageCollectionAsync {#page-force-garbage-collection}
-
-<font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.47</font><x-search>page.ForceGarbageCollectionAsync</x-search>
-
-Force the browser to perform garbage collection.
-
-**Usage**
-
-```csharp
-await Page.ForceGarbageCollectionAsync();
-```
-
-**Returns**
-- [void]<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="page-force-garbage-collection-return"/><a href="#page-force-garbage-collection-return" class="list-anchor">#</a>
-
----
-
 ### Frame {#page-frame}
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.Frame</x-search>
@@ -935,6 +926,7 @@ await page
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
@@ -1187,6 +1179,7 @@ The method will throw an error if:
 The method will not throw an error when any valid HTTP status code is returned by the remote server, including 404 "Not Found" and 500 "Internal Server Error".  The status code for such responses can be retrieved by calling [Response.Status](/api/class-response.mdx#response-status).
 
 :::note
+
 The method either throws an error or returns a main resource response. The only exceptions are navigation to `about:blank` or navigation to the same URL with a different hash, which would succeed and return `null`.
 :::
 
@@ -1327,6 +1320,7 @@ Pauses script execution. Playwright will stop executing the script and wait for
 User can inspect selectors or perform manual steps while paused. Resume will continue running the original script from the place it was paused.
 
 :::note
+
 This method requires Playwright to be started in a headed mode, with a falsy [Headless](/api/class-browsertype.mdx#browser-type-launch-option-headless) option.
 :::
 
@@ -1348,12 +1342,14 @@ await Page.PauseAsync();
 Returns the PDF buffer.
 
 :::note
+
 Generating a pdf is currently only supported in Chromium headless.
 :::
 
 `page.pdf()` generates a pdf of the page with `print` css media. To generate a pdf with `screen` media, call [Page.EmulateMediaAsync()](/api/class-page.mdx#page-emulate-media) before calling `page.pdf()`:
 
 :::note
+
 By default, `page.pdf()` generates a pdf with modified colors for printing. Use the [`-webkit-print-color-adjust`](https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-print-color-adjust) property to force rendering of exact colors.
 :::
 
@@ -1392,6 +1388,7 @@ The [Format](/api/class-page.mdx#page-pdf-option-format) options are:
 * `A6`: 4.13in x 5.83in
 
 :::note
+
 [HeaderTemplate](/api/class-page.mdx#page-pdf-option-header-template) and [FooterTemplate](/api/class-page.mdx#page-pdf-option-footer-template) markup have the following limitations: > 1. Script tags inside templates are not evaluated. > 2. Page styles are not visible inside templates.
 :::
 
@@ -1517,6 +1514,34 @@ await Page.RemoveLocatorHandlerAsync(locator);
 
 ---
 
+### RequestGCAsync {#page-request-gc}
+
+<font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.48</font><x-search>page.RequestGCAsync</x-search>
+
+Request the page to perform garbage collection. Note that there is no guarantee that all unreachable objects will be collected.
+
+This is useful to help detect memory leaks. For example, if your page has a large object `'suspect'` that might be leaked, you can check that it does not leak by using a [`WeakRef`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakRef).
+
+```csharp
+// 1. In your page, save a WeakRef for the "suspect".
+await Page.EvaluateAsync("globalThis.suspectWeakRef = new WeakRef(suspect)");
+// 2. Request garbage collection.
+await Page.RequestGCAsync();
+// 3. Check that weak ref does not deref to the original object.
+Assert.True(await Page.EvaluateAsync("!globalThis.suspectWeakRef.deref()"));
+```
+
+**Usage**
+
+```csharp
+await Page.RequestGCAsync();
+```
+
+**Returns**
+- [void]<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="page-request-gc-return"/><a href="#page-request-gc-return" class="list-anchor">#</a>
+
+---
+
 ### RouteAsync {#page-route}
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.RouteAsync</x-search>
@@ -1526,6 +1551,7 @@ Routing provides the capability to modify network requests that are made by a pa
 Once routing is enabled, every request matching the url pattern will stall unless it's continued, fulfilled or aborted.
 
 :::note
+
 The handler will only be called for the first url if the response is a redirect.
 :::
 
@@ -1572,6 +1598,7 @@ Page routes take precedence over browser context routes (set up with [BrowserCon
 To remove a route with its handler you can use [Page.UnrouteAsync()](/api/class-page.mdx#page-unroute).
 
 :::note
+
 Enabling routing disables http cache.
 :::
 
@@ -2329,6 +2356,7 @@ This setting will change the default maximum navigation time for the following m
 * [Page.WaitForURLAsync()](/api/class-page.mdx#page-wait-for-url)
 
 :::note
+
 [Page.SetDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) takes priority over [Page.SetDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout), [BrowserContext.SetDefaultTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout) and [BrowserContext.SetDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout).
 :::
 
@@ -2352,6 +2380,7 @@ Page.SetDefaultNavigationTimeout(timeout);
 This setting will change the default maximum time for all the methods accepting [timeout](/api/class-page.mdx#page-set-default-timeout-option-timeout) option.
 
 :::note
+
 [Page.SetDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) takes priority over [Page.SetDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout).
 :::
 
@@ -2375,6 +2404,7 @@ Page.SetDefaultTimeout(timeout);
 The extra HTTP headers will be sent with every request the page initiates.
 
 :::note
+
 [Page.SetExtraHTTPHeadersAsync()](/api/class-page.mdx#page-set-extra-http-headers) does not guarantee the order of headers in the outgoing requests.
 :::
 
@@ -2603,6 +2633,7 @@ Returns when the required load state has been reached.
 This resolves when the page reaches a required load state, `load` by default. The navigation must have been committed when this method is called. If current document has already reached the required state, resolves immediately.
 
 :::note
+
 Most of the time, this method is not needed because Playwright [auto-waits before every action](../actionability.mdx).
 :::
 
@@ -2681,6 +2712,7 @@ await page.WaitForURLAsync("**/target.html");
 This method returns all of the dedicated [WebWorkers](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API) associated with the page.
 
 :::note
+
 This does not contain ServiceWorkers
 :::
 
@@ -3080,6 +3112,7 @@ Page.Request += async (_, request) => {};
 Emitted when a request fails, for example by timing out.
 
 :::note
+
 HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with [Page.RequestFinished](/api/class-page.mdx#page-event-request-finished) event and not with [Page.RequestFailed](/api/class-page.mdx#page-event-request-failed). A request will only be considered failed when the client cannot get an HTTP response from the server, e.g. due to network error net::ERR_FAILED.
 :::
 
@@ -3349,6 +3382,7 @@ This method double clicks an element matching [selector](/api/class-page.mdx#pag
 When all steps combined have not finished during the specified [Timeout](/api/class-page.mdx#page-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `page.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -4531,6 +4565,7 @@ This method taps an element matching [selector](/api/class-page.mdx#page-tap-opt
 When all steps combined have not finished during the specified [Timeout](/api/class-page.mdx#page-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 [Page.TapAsync()](/api/class-page.mdx#page-tap) the method will throw if [HasTouch](/api/class-browser.mdx#browser-new-context-option-has-touch) option of the browser context is false.
 :::
 
@@ -4746,6 +4781,7 @@ Use web assertions that assert visibility or a locator-based [Locator.WaitForAsy
 Returns when element specified by selector satisfies [State](/api/class-page.mdx#page-wait-for-selector-option-state) option. Returns `null` if waiting for `hidden` or `detached`.
 
 :::note
+
 Playwright automatically waits for element to be ready before performing an action. Using [Locator] objects and web-first assertions makes the code wait-for-selector-free.
 :::
 
diff --git a/dotnet/docs/api/class-request.mdx b/dotnet/docs/api/class-request.mdx
index 73e205a94e..2b4d87cdae 100644
--- a/dotnet/docs/api/class-request.mdx
+++ b/dotnet/docs/api/class-request.mdx
@@ -15,6 +15,7 @@ Whenever the page sends a request for a network resource the following sequence
 If request fails at some point, then instead of `'requestfinished'` event (and possibly instead of 'response' event), the  [Page.RequestFailed](/api/class-page.mdx#page-event-request-failed) event is emitted.
 
 :::note
+
 HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with `'requestfinished'` event.
 :::
 
diff --git a/dotnet/docs/api/class-touchscreen.mdx b/dotnet/docs/api/class-touchscreen.mdx
index 080cc410ef..0c02c5b5b8 100644
--- a/dotnet/docs/api/class-touchscreen.mdx
+++ b/dotnet/docs/api/class-touchscreen.mdx
@@ -21,6 +21,7 @@ The Touchscreen class operates in main-frame CSS pixels relative to the top-left
 Dispatches a `touchstart` and `touchend` event with a single touch at the position ([x](/api/class-touchscreen.mdx#touchscreen-tap-option-x),[y](/api/class-touchscreen.mdx#touchscreen-tap-option-y)).
 
 :::note
+
 [Page.TapAsync()](/api/class-page.mdx#page-tap) the method will throw if [HasTouch](/api/class-browser.mdx#browser-new-context-option-has-touch) option of the browser context is false.
 :::
 
diff --git a/dotnet/docs/browsers.mdx b/dotnet/docs/browsers.mdx
index 76ad6d8238..94a01229a7 100644
--- a/dotnet/docs/browsers.mdx
+++ b/dotnet/docs/browsers.mdx
@@ -106,6 +106,7 @@ While Playwright can download and use the recent Chromium build, it can operate
 Available channels are `chrome`, `msedge`, `chrome-beta`, `msedge-beta` or `msedge-dev`.
 
 :::warning
+
 Certain Enterprise Browser Policies may impact Playwright's ability to launch and control Google Chrome and Microsoft Edge. Running in an environment with browser policies is outside of the Playwright project's scope.
 :::
 
@@ -454,6 +455,7 @@ dotnet test
 Playwright keeps track of packages that need those browsers and will garbage collect them as you update Playwright to the newer versions.
 
 :::note
+
 Developers can opt-in in this mode via exporting `PLAYWRIGHT_BROWSERS_PATH=$HOME/pw-browsers` in their `.bashrc`.
 :::
 
diff --git a/dotnet/docs/clock.mdx b/dotnet/docs/clock.mdx
index d47cba9db3..6d6b9bfe60 100644
--- a/dotnet/docs/clock.mdx
+++ b/dotnet/docs/clock.mdx
@@ -24,7 +24,19 @@ The [Clock] API provides the following methods to control time:
 The recommended approach is to use `setFixedTime` to set the time to a specific value. If that doesn't work for your use case, you can use `install` which allows you to pause time later on, fast forward it, tick it, etc. `setSystemTime` is only recommended for advanced use cases.
 
 :::note
-[Page.Clock](/api/class-page.mdx#page-clock) overrides native global classes and functions related to time allowing them to be manually controlled:   - `Date`   - `setTimeout`   - `clearTimeout`   - `setInterval`   - `clearInterval`   - `requestAnimationFrame`   - `cancelAnimationFrame`   - `requestIdleCallback`   - `cancelIdleCallback`   - `performance`   - `Event.timeStamp`
+
+[Page.Clock](/api/class-page.mdx#page-clock) overrides native global classes and functions related to time allowing them to be manually controlled:
+- `Date`
+- `setTimeout`
+- `clearTimeout`
+- `setInterval`
+- `clearInterval`
+- `requestAnimationFrame`
+- `cancelAnimationFrame`
+- `requestIdleCallback`
+- `cancelIdleCallback`
+- `performance`
+- `Event.timeStamp`
 :::
 
 ## Test with predefined time
diff --git a/dotnet/docs/debug.mdx b/dotnet/docs/debug.mdx
index bec9b7e511..571cc7e3de 100644
--- a/dotnet/docs/debug.mdx
+++ b/dotnet/docs/debug.mdx
@@ -246,6 +246,7 @@ dotnet run
 </Tabs>
 
 :::note
+
 **For WebKit**: launching WebKit Inspector during the execution will prevent the Playwright script from executing any further and will reset pre-configured user agent and device emulation.
 :::
 
diff --git a/dotnet/docs/dialogs.mdx b/dotnet/docs/dialogs.mdx
index e6cb198a6e..12b8181468 100644
--- a/dotnet/docs/dialogs.mdx
+++ b/dotnet/docs/dialogs.mdx
@@ -29,6 +29,7 @@ await Page.GetByRole(AriaRole.Button).ClickAsync();
 As a result, the following snippet will never resolve:
 
 :::warning
+
 WRONG!
 :::
 
diff --git a/dotnet/docs/docker.mdx b/dotnet/docs/docker.mdx
index 0f6030e60b..bcbe46ec28 100644
--- a/dotnet/docs/docker.mdx
+++ b/dotnet/docs/docker.mdx
@@ -15,6 +15,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 This Docker image is published to [Microsoft Artifact Registry].
 
 :::info
+
 This Docker image is intended to be used for testing and development purposes only. It is not recommended to use this Docker image to visit untrusted websites.
 :::
 
@@ -80,6 +81,7 @@ We currently publish images with the following tags:
 - `:v1.47.0-focal` - Playwright v1.47.0 release docker image based on Ubuntu 20.04 LTS (Focal Fossa).
 
 :::note
+
 It is recommended to always pin your Docker image to a specific version if possible. If the Playwright version in your Docker image does not match the version in your project/tests, Playwright will be unable to locate browser executables.
 :::
 
diff --git a/dotnet/docs/downloads.mdx b/dotnet/docs/downloads.mdx
index 5e5219c673..f0c65e6d92 100644
--- a/dotnet/docs/downloads.mdx
+++ b/dotnet/docs/downloads.mdx
@@ -13,6 +13,7 @@ For every attachment downloaded by the page, [Page.Download](/api/class-page.mdx
 You can specify where to persist downloaded files using the [DownloadsPath](/api/class-browsertype.mdx#browser-type-launch-option-downloads-path) option in [BrowserType.LaunchAsync()](/api/class-browsertype.mdx#browser-type-launch).
 
 :::note
+
 Downloaded files are deleted when the browser context that produced them is closed.
 :::
 
@@ -39,6 +40,7 @@ page.Download += (sender, download) => Console.WriteLine(download.Url);
 Note that handling the event forks the control flow and makes the script harder to follow. Your scenario might end while you are downloading a file since your main control flow is not awaiting for this operation to resolve.
 
 :::note
+
 For uploading files, see the [uploading files](./input.mdx#upload-files) section.
 :::
 
diff --git a/dotnet/docs/handles.mdx b/dotnet/docs/handles.mdx
index 10ad2bae22..f63ffbb847 100644
--- a/dotnet/docs/handles.mdx
+++ b/dotnet/docs/handles.mdx
@@ -30,6 +30,7 @@ var jsHandle = await page.EvaluateHandleAsync("window");
 ## Element Handles
 
 :::warning[Discouraged]
+
 The use of [ElementHandle] is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -91,6 +92,7 @@ Handles can be acquired using the page methods such as [Page.EvaluateHandleAsync
 ## Locator vs ElementHandle
 
 :::caution
+
 We only recommend using [ElementHandle] in the rare cases when you need to perform extensive DOM traversal on a static page. For all user actions and assertions use locator instead.
 :::
 
diff --git a/dotnet/docs/input.mdx b/dotnet/docs/input.mdx
index dcaacda32e..bdfe0e366b 100644
--- a/dotnet/docs/input.mdx
+++ b/dotnet/docs/input.mdx
@@ -113,6 +113,7 @@ await page.GetByRole(AriaRole.Button).DispatchEventAsync("click");
 ## Type characters
 
 :::caution
+
 Most of the time, you should input text with [Locator.FillAsync()](/api/class-locator.mdx#locator-fill). See the [Text input](#text-input) section above. You only need to type characters if there is special keyboard handling on the page.
 :::
 
diff --git a/dotnet/docs/locators.mdx b/dotnet/docs/locators.mdx
index 45cfe81279..eb02d07575 100644
--- a/dotnet/docs/locators.mdx
+++ b/dotnet/docs/locators.mdx
@@ -125,6 +125,7 @@ Role locators include [buttons, checkboxes, headings, links, lists, tables, and
 Note that role locators **do not replace** accessibility audits and conformance tests, but rather give early feedback about the ARIA guidelines.
 
 :::note[When to use role locators]
+
 We recommend prioritizing role locators to locate elements, as it is the closest way to how users and assistive technology perceive the page.
 :::
 
@@ -604,6 +605,7 @@ If you'd like to target one of the two or more elements, and you don't know whic
 For example, consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead. In this case, you can wait for either a "New email" button, or a dialog and act accordingly.
 
 :::note
+
 If both "New email" button and security dialog appear on screen, the "or" locator will match both of them, possibly throwing the ["strict mode violation" error](#strictness). In this case, you can use [Locator.First](/api/class-locator.mdx#locator-first) to only match one of them.
 :::
 
@@ -619,6 +621,7 @@ await newEmail.ClickAsync();
 ### Matching only visible elements
 
 :::note
+
 It's usually better to find a [more reliable way](./locators.mdx#quick-guide) to uniquely identify the element instead of checking the visibility.
 :::
 
diff --git a/dotnet/docs/navigations.mdx b/dotnet/docs/navigations.mdx
index a760bdb318..c4b53b276a 100644
--- a/dotnet/docs/navigations.mdx
+++ b/dotnet/docs/navigations.mdx
@@ -22,6 +22,7 @@ await page.GotoAsync("https://example.com");
 The code above loads the page and waits for the web page to fire the [load](https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event) event. The load event is fired when the whole page has loaded, including all dependent resources such as stylesheets, scripts, iframes, and images.
 
 :::note
+
 If the page does a client-side redirect before `load`, [Page.GotoAsync()](/api/class-page.mdx#page-goto) will wait for the redirected page to fire the `load` event.
 :::
 
diff --git a/dotnet/docs/other-locators.mdx b/dotnet/docs/other-locators.mdx
index 3d8dc58edd..72c7b7d5cd 100644
--- a/dotnet/docs/other-locators.mdx
+++ b/dotnet/docs/other-locators.mdx
@@ -9,6 +9,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ## Introduction
 
 :::note
+
 Check out the main [locators guide](./locators) for most common and recommended locators.
 :::
 
@@ -17,6 +18,7 @@ In addition to recommended locators like [Page.GetByRole()](/api/class-page.mdx#
 ## CSS locator
 
 :::note
+
 We recommend prioritizing [user-visible locators](./locators.mdx#quick-guide) like text or accessible role instead of using CSS that is tied to the implementation and could break when the page changes.
 :::
 
@@ -64,6 +66,7 @@ Playwright include a number of CSS pseudo-classes to match elements by their tex
   For example, `:text-matches("Log\s*in", "i")` matches `<button>Login</button>` and `<button>log IN</button>`.
 
 :::note
+
 Text matching always normalizes whitespace. For example, it turns multiple spaces into one, turns line breaks into spaces and ignores leading and trailing whitespace.
 :::
 
@@ -118,6 +121,7 @@ The `:is()` pseudo-class is an [experimental CSS pseudo-class](https://developer
 ### CSS: matching elements based on layout
 
 :::note
+
 Matching based on layout may produce unexpected results. For example, a different element could be matched when layout changes by one pixel.
 :::
 
@@ -152,6 +156,7 @@ All layout pseudo-classes support optional maximum pixel distance as the last ar
 ### CSS: pick n-th match from the query result
 
 :::note
+
 It is usually possible to distinguish elements by some attribute or text content, which is more resilient to page changes.
 :::
 
@@ -218,6 +223,7 @@ var parent = page.GetByText("Hello").Locator("xpath=..");
 ## React locator
 
 :::note
+
 React locator is experimental and prefixed with `_`. The functionality might change in future.
 :::
 
@@ -246,6 +252,7 @@ More examples:
 To find React element names in a tree use [React DevTools](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi).
 
 :::note
+
 React locator supports React 15 and above.
 :::
 
@@ -256,6 +263,7 @@ React locator, as well as [React DevTools](https://chrome.google.com/webstore/de
 ## Vue locator
 
 :::note
+
 Vue locator is experimental and prefixed with `_`. The functionality might change in future.
 :::
 
@@ -283,6 +291,7 @@ More examples:
 To find Vue element names in a tree use [Vue DevTools](https://chrome.google.com/webstore/detail/vuejs-devtools/nhdogjmejiglipccpnnnanhbledajbpd?hl=en).
 
 :::note
+
 Vue locator supports Vue2 and above.
 :::
 
@@ -293,6 +302,7 @@ Vue locator, as well as [Vue DevTools](https://chrome.google.com/webstore/detail
 ## XPath locator
 
 :::warning
+
 We recommend prioritizing [user-visible locators](./locators.mdx#quick-guide) like text or accessible role instead of using XPath that is tied to the implementation and easily break when the page changes.
 :::
 
@@ -322,6 +332,7 @@ await page.Locator("//span[contains(@class, 'spinner__loading')]|//div[@id='conf
 ## Label to form control retargeting
 
 :::warning
+
 We recommend [locating by label text](./locators.mdx#locate-by-label) instead of relying to label-to-control retargeting.
 :::
 
@@ -350,6 +361,7 @@ await Expect(Page.Locator("label")).ToHaveTextAsync("Password");
 ## Legacy text locator
 
 :::warning
+
 We recommend the modern [text locator](./locators.mdx#get-by-text) instead.
 :::
 
@@ -383,6 +395,7 @@ Legacy text locator has a few variations:
   ```
   
 :::note
+
 String selectors starting and ending with a quote (either `"` or `'`) are assumed to be a legacy text locators. For example, `"Log in"` is converted to `text="Log in"` internally.
 :::
 
@@ -397,6 +410,7 @@ Input elements of the type `button` and `submit` are matched by their `value` in
 ## id, data-testid, data-test-id, data-test selectors
 
 :::warning
+
 We recommend [locating by test id](./locators.mdx#locate-by-test-id) instead.
 :::
 
@@ -421,6 +435,7 @@ Attribute selectors are not CSS selectors, so anything CSS-specific like `:enabl
 ## Chaining selectors
 
 :::warning
+
 We recommend [chaining locators](./locators.mdx#matching-inside-a-locator) instead.
 :::
 
@@ -446,6 +461,7 @@ If a selector needs to include `>>` in the body, it should be escaped inside a s
 ### Intermediate matches
 
 :::warning
+
 We recommend [filtering by another locator](./locators.mdx#filter-by-childdescendant) to locate elements that contain other elements.
 :::
 
diff --git a/dotnet/docs/selenium-grid.mdx b/dotnet/docs/selenium-grid.mdx
index f9b9c3a3d3..878a594acc 100644
--- a/dotnet/docs/selenium-grid.mdx
+++ b/dotnet/docs/selenium-grid.mdx
@@ -11,7 +11,20 @@ import HTMLCard from '@site/src/components/HTMLCard';
 Playwright can connect to [Selenium Grid Hub](https://www.selenium.dev/documentation/grid/) that runs Selenium 4 to launch **Google Chrome** or **Microsoft Edge** browser, instead of running browser on the local machine. Note this feature is **experimental** and is prioritized accordingly.
 
 :::warning
-There is a risk of Playwright integration with Selenium Grid Hub breaking in the future. Make sure you weight risks against benefits before using it.  <br /> <br /> <details> <summary> <span style={{textTransform:'uppercase',fontSize:'smaller',fontWeight:'bold',opacity:'0.6'}}>More details</span> </summary>  Internally, Playwright connects to the browser using [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) websocket. Selenium 4 currently exposes this capability. However, this [might not be the case in the future](https://github.com/SeleniumHQ/selenium/issues/11590#issuecomment-1436113950). If Selenium drops this capability, Playwright will stop working with it. </details>
+
+There is a risk of Playwright integration with Selenium Grid Hub breaking in the future. Make sure you weight risks against benefits before using it.
+
+<details>
+
+<summary>
+
+<span style={{textTransform:'uppercase',fontSize:'smaller',fontWeight:'bold',opacity:'0.6'}}>More details</span>
+
+</summary>
+
+Internally, Playwright connects to the browser using [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) websocket. Selenium 4 currently exposes this capability. However, this [might not be the case in the future](https://github.com/SeleniumHQ/selenium/issues/11590#issuecomment-1436113950). If Selenium drops this capability, Playwright will stop working with it.
+
+</details>
 :::
 
 Before connecting Playwright to your Selenium Grid, make sure that grid works with [Selenium WebDriver](https://www.selenium.dev/documentation/webdriver/). For example, run [one of the examples](https://github.com/SeleniumHQ/selenium/tree/trunk/javascript/node/selenium-webdriver/example) and pass `SELENIUM_REMOTE_URL` environment variable. If webdriver example does not work, look for any errors at your Selenium hub/node/standalone output and search [Selenium issues](https://github.com/SeleniumHQ/selenium/issues) for a possible solution.
diff --git a/dotnet/docs/trace-viewer.mdx b/dotnet/docs/trace-viewer.mdx
index 424245796b..8f1ab7d5d0 100644
--- a/dotnet/docs/trace-viewer.mdx
+++ b/dotnet/docs/trace-viewer.mdx
@@ -43,8 +43,6 @@ When tracing with the [Snapshots](/api/class-tracing.mdx#tracing-start-option-sn
 |Action|A snapshot at the moment of the performed input. This type of snapshot is especially useful when exploring where exactly Playwright clicked.|
 |After|A snapshot after the action.|
 
-<br/>
-
 Here is what the typical Action snapshot looks like:
 
 ![action tab in trace viewer](https://github.com/microsoft/playwright/assets/13063165/7168d549-eb0a-4964-9c93-483f03711fa9)
diff --git a/java/docs/api/class-apirequest.mdx b/java/docs/api/class-apirequest.mdx
index cccfcb1f8e..eba5f0e9e4 100644
--- a/java/docs/api/class-apirequest.mdx
+++ b/java/docs/api/class-apirequest.mdx
@@ -68,6 +68,7 @@ APIRequest.newContext(options);
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
diff --git a/java/docs/api/class-browser.mdx b/java/docs/api/class-browser.mdx
index 073a0c2a0a..203dbe43e5 100644
--- a/java/docs/api/class-browser.mdx
+++ b/java/docs/api/class-browser.mdx
@@ -56,6 +56,7 @@ In case this browser is obtained using [BrowserType.launch()](/api/class-browser
 In case this browser is connected to, clears all created contexts belonging to this browser and disconnects from the browser server.
 
 :::note
+
 This is similar to force quitting the browser. Therefore, you should call [BrowserContext.close()](/api/class-browsercontext.mdx#browser-context-close) on any [BrowserContext]'s you explicitly created earlier with [Browser.newContext()](/api/class-browser.mdx#browser-new-context) **before** calling [Browser.close()](/api/class-browser.mdx#browser-close).
 :::
 
@@ -121,6 +122,7 @@ Browser.isConnected();
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.newBrowserCDPSession</x-search>
 
 :::note
+
 CDP Sessions are only supported on Chromium-based browsers.
 :::
 
@@ -144,6 +146,7 @@ Browser.newBrowserCDPSession();
 Creates a new browser context. It won't share cookies/cache with other browser contexts.
 
 :::note
+
 If directly using this method to create [BrowserContext]s, it is best practice to explicitly close the returned context via [BrowserContext.close()](/api/class-browsercontext.mdx#browser-context-close) when your code is done with the [BrowserContext], and before calling [Browser.close()](/api/class-browser.mdx#browser-close). This will ensure the `context` is closed gracefully and any artifacts—like HARs and videos—are fully flushed and saved.
 :::
 
@@ -209,6 +212,7 @@ browser.close();
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
@@ -353,6 +357,7 @@ browser.close();
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `null` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation#viewport).
     
     :::note
+    
     The `null` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
@@ -423,6 +428,7 @@ Browser.newPage(options);
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
@@ -567,6 +573,7 @@ Browser.newPage(options);
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `null` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation#viewport).
     
     :::note
+    
     The `null` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
@@ -580,6 +587,7 @@ Browser.newPage(options);
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.startTracing</x-search>
 
 :::note
+
 This API controls [Chromium Tracing](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool) which is a low-level chromium-specific debugging tool. API to control [Playwright Tracing](../trace-viewer) could be found [here](./class-tracing).
 :::
 
@@ -619,6 +627,7 @@ browser.stopTracing();
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.stopTracing</x-search>
 
 :::note
+
 This API controls [Chromium Tracing](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool) which is a low-level chromium-specific debugging tool. API to control [Playwright Tracing](../trace-viewer) could be found [here](./class-tracing).
 :::
 
diff --git a/java/docs/api/class-browsercontext.mdx b/java/docs/api/class-browsercontext.mdx
index e0a1089928..380ab44ff9 100644
--- a/java/docs/api/class-browsercontext.mdx
+++ b/java/docs/api/class-browsercontext.mdx
@@ -118,6 +118,7 @@ The order of evaluation of multiple scripts installed via [BrowserContext.addIni
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.backgroundPages</x-search>
 
 :::note
+
 Background pages are only supported on Chromium-based browsers.
 :::
 
@@ -213,6 +214,7 @@ context.clearPermissions();
 Closes the browser context. All the pages that belong to the browser context will be closed.
 
 :::note
+
 The default browser context cannot be closed.
 :::
 
@@ -453,6 +455,7 @@ BrowserContext.grantPermissions(permissions, options);
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.newCDPSession</x-search>
 
 :::note
+
 CDP sessions are only supported on Chromium-based browsers.
 :::
 
@@ -515,6 +518,7 @@ BrowserContext.pages();
 Routing provides the capability to modify network requests that are made by any page in the browser context. Once route is enabled, every request matching the url pattern will stall unless it's continued, fulfilled or aborted.
 
 :::note
+
 [BrowserContext.route()](/api/class-browsercontext.mdx#browser-context-route) will not intercept requests intercepted by Service Worker. See [this](https://github.com/microsoft/playwright/issues/1090) issue. We recommend disabling Service Workers when using request interception by setting [setServiceWorkers](/api/class-browser.mdx#browser-new-context-option-service-workers) to `'block'`.
 :::
 
@@ -556,6 +560,7 @@ Page routes (set up with [Page.route()](/api/class-page.mdx#page-route)) take pr
 To remove a route with its handler you can use [BrowserContext.unroute()](/api/class-browsercontext.mdx#browser-context-unroute).
 
 :::note
+
 Enabling routing disables http cache.
 :::
 
@@ -668,6 +673,7 @@ This setting will change the default maximum navigation time for the following m
 * [Page.waitForNavigation()](/api/class-page.mdx#page-wait-for-navigation)
 
 :::note
+
 [Page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) and [Page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout) take priority over [BrowserContext.setDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout).
 :::
 
@@ -691,6 +697,7 @@ BrowserContext.setDefaultNavigationTimeout(timeout);
 This setting will change the default maximum time for all the methods accepting [timeout](/api/class-browsercontext.mdx#browser-context-set-default-timeout-option-timeout) option.
 
 :::note
+
 [Page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout), [Page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout) and [BrowserContext.setDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout) take priority over [BrowserContext.setDefaultTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout).
 :::
 
@@ -714,6 +721,7 @@ BrowserContext.setDefaultTimeout(timeout);
 The extra HTTP headers will be sent with every request initiated by any page in the context. These headers are merged with page-specific extra HTTP headers set with [Page.setExtraHTTPHeaders()](/api/class-page.mdx#page-set-extra-http-headers). If page overrides a particular header, page-specific header value will be used instead of the browser context header value.
 
 :::note
+
 [BrowserContext.setExtraHTTPHeaders()](/api/class-browsercontext.mdx#browser-context-set-extra-http-headers) does not guarantee the order of headers in the outgoing requests.
 :::
 
@@ -1007,6 +1015,7 @@ BrowserContext.tracing()
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.onBackgroundPage(handler)</x-search>
 
 :::note
+
 Only works with Chromium browser's persistent context.
 :::
 
@@ -1151,6 +1160,7 @@ BrowserContext.onRequest(handler)
 Emitted when a request fails, for example by timing out. To only listen for failed requests from a particular page, use [Page.onRequestFailed(handler)](/api/class-page.mdx#page-event-request-failed).
 
 :::note
+
 HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with [BrowserContext.onRequestFinished(handler)](/api/class-browsercontext.mdx#browser-context-event-request-finished) event and not with [BrowserContext.onRequestFailed(handler)](/api/class-browsercontext.mdx#browser-context-event-request-failed).
 :::
 
diff --git a/java/docs/api/class-browsertype.mdx b/java/docs/api/class-browsertype.mdx
index 9d5e9743a3..db64af820b 100644
--- a/java/docs/api/class-browsertype.mdx
+++ b/java/docs/api/class-browsertype.mdx
@@ -86,6 +86,7 @@ This method attaches Playwright to an existing browser instance using the Chrome
 The default browser context is accessible via [Browser.contexts()](/api/class-browser.mdx#browser-contexts).
 
 :::note
+
 Connecting over the Chrome DevTools Protocol is only supported for Chromium-based browsers.
 :::
 
@@ -161,6 +162,7 @@ Browser browser = chromium.launch(new BrowserType.LaunchOptions()
   - `setArgs` [List]&lt;[String]&gt; *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-type-launch-option-args"/><a href="#browser-type-launch-option-args" class="list-anchor">#</a>
     
     :::warning
+    
     Use custom browser args at your own risk, as some of them may break Playwright functionality.
     :::
     
@@ -265,6 +267,7 @@ BrowserType.launchPersistentContext(userDataDir, options);
   - `setArgs` [List]&lt;[String]&gt; *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-type-launch-persistent-context-option-args"/><a href="#browser-type-launch-persistent-context-option-args" class="list-anchor">#</a>
     
     :::warning
+    
     Use custom browser args at your own risk, as some of them may break Playwright functionality.
     :::
     
@@ -317,6 +320,7 @@ BrowserType.launchPersistentContext(userDataDir, options);
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
@@ -502,6 +506,7 @@ BrowserType.launchPersistentContext(userDataDir, options);
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `null` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation#viewport).
     
     :::note
+    
     The `null` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
diff --git a/java/docs/api/class-elementhandle.mdx b/java/docs/api/class-elementhandle.mdx
index 5d44511a89..1fc78f617d 100644
--- a/java/docs/api/class-elementhandle.mdx
+++ b/java/docs/api/class-elementhandle.mdx
@@ -11,6 +11,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ElementHandle represents an in-page DOM element. ElementHandles can be created with the [Page.querySelector()](/api/class-page.mdx#page-query-selector) method.
 
 :::warning[Discouraged]
+
 The use of ElementHandle is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -311,6 +312,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [setTimeout](/api/class-elementhandle.mdx#element-handle-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `elementHandle.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -1354,6 +1356,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [setTimeout](/api/class-elementhandle.mdx#element-handle-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `elementHandle.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
diff --git a/java/docs/api/class-frame.mdx b/java/docs/api/class-frame.mdx
index 6935f94fba..e0bc829ad6 100644
--- a/java/docs/api/class-frame.mdx
+++ b/java/docs/api/class-frame.mdx
@@ -496,6 +496,7 @@ page.getByRole(AriaRole.BUTTON,
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
@@ -770,6 +771,7 @@ Returns frame's name attribute as specified in the tag.
 If the name is empty, returns the id attribute instead.
 
 :::note
+
 This value is calculated once when the frame is created, and will not update if the attribute is changed later.
 :::
 
@@ -800,6 +802,7 @@ The method will throw an error if:
 The method will not throw an error when any valid HTTP status code is returned by the remote server, including 404 "Not Found" and 500 "Internal Server Error".  The status code for such responses can be retrieved by calling [Response.status()](/api/class-response.mdx#response-status).
 
 :::note
+
 The method either throws an error or returns a main resource response. The only exceptions are navigation to `about:blank` or navigation to the same URL with a different hash, which would succeed and return `null`.
 :::
 
@@ -1003,6 +1006,7 @@ Waits for the required load state to be reached.
 This returns when the frame reaches a required load state, `load` by default. The navigation must have been committed when this method is called. If current document has already reached the required state, resolves immediately.
 
 :::note
+
 Most of the time, this method is not needed because Playwright [auto-waits before every action](../actionability.mdx).
 :::
 
@@ -1231,6 +1235,7 @@ This method double clicks an element matching [selector](/api/class-frame.mdx#fr
 When all steps combined have not finished during the specified [setTimeout](/api/class-frame.mdx#frame-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `frame.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -2018,6 +2023,7 @@ Use locator-based [Frame.locator()](/api/class-frame.mdx#frame-locator) instead.
 Returns the ElementHandle pointing to the frame element.
 
 :::caution
+
 The use of [ElementHandle] is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -2058,6 +2064,7 @@ Use locator-based [Frame.locator()](/api/class-frame.mdx#frame-locator) instead.
 Returns the ElementHandles pointing to the frame elements.
 
 :::caution
+
 The use of [ElementHandle] is discouraged, use [Locator] objects instead.
 :::
 
@@ -2297,6 +2304,7 @@ This method taps an element matching [selector](/api/class-frame.mdx#frame-tap-o
 When all steps combined have not finished during the specified [setTimeout](/api/class-frame.mdx#frame-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `frame.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
@@ -2568,6 +2576,7 @@ Use web assertions that assert visibility or a locator-based [Locator.waitFor()]
 Returns when element specified by selector satisfies [setState](/api/class-frame.mdx#frame-wait-for-selector-option-state) option. Returns `null` if waiting for `hidden` or `detached`.
 
 :::note
+
 Playwright automatically waits for element to be ready before performing an action. Using [Locator] objects and web-first assertions make the code wait-for-selector-free.
 :::
 
diff --git a/java/docs/api/class-framelocator.mdx b/java/docs/api/class-framelocator.mdx
index d9a1b2d497..c1b5203f99 100644
--- a/java/docs/api/class-framelocator.mdx
+++ b/java/docs/api/class-framelocator.mdx
@@ -214,6 +214,7 @@ page.getByRole(AriaRole.BUTTON,
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
diff --git a/java/docs/api/class-jshandle.mdx b/java/docs/api/class-jshandle.mdx
index 50a86d5a5b..45e0b772f9 100644
--- a/java/docs/api/class-jshandle.mdx
+++ b/java/docs/api/class-jshandle.mdx
@@ -171,6 +171,7 @@ JSHandle.getProperty(propertyName);
 Returns a JSON representation of the object. If the object has a `toJSON` function, it **will not be called**.
 
 :::note
+
 The method will return an empty JSON object if the referenced object is not stringifiable. It will throw an error if the object has circular references.
 :::
 
diff --git a/java/docs/api/class-keyboard.mdx b/java/docs/api/class-keyboard.mdx
index 33a68fbe1b..b84c92d8da 100644
--- a/java/docs/api/class-keyboard.mdx
+++ b/java/docs/api/class-keyboard.mdx
@@ -67,6 +67,7 @@ If [key](/api/class-keyboard.mdx#keyboard-down-option-key) is a modifier key, `S
 After the key is pressed once, subsequent calls to [Keyboard.down()](/api/class-keyboard.mdx#keyboard-down) will have [repeat](https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/repeat) set to true. To release the key, use [Keyboard.up()](/api/class-keyboard.mdx#keyboard-up).
 
 :::note
+
 Modifier keys DO influence `keyboard.down`. Holding down `Shift` will type the text in upper case.
 :::
 
@@ -117,6 +118,7 @@ Modifier keys DO NOT effect `keyboard.insertText`. Holding down `Shift` will not
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>keyboard.press</x-search>
 
 :::tip
+
 In most cases, you should use [Locator.press()](/api/class-locator.mdx#locator-press) instead.
 :::
 
@@ -167,6 +169,7 @@ Shortcut for [Keyboard.down()](/api/class-keyboard.mdx#keyboard-down) and [Keybo
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>keyboard.type</x-search>
 
 :::caution
+
 In most cases, you should use [Locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.pressSequentially()](/api/class-locator.mdx#locator-press-sequentially).
 :::
 
diff --git a/java/docs/api/class-locator.mdx b/java/docs/api/class-locator.mdx
index e2bb750976..10186d1a02 100644
--- a/java/docs/api/class-locator.mdx
+++ b/java/docs/api/class-locator.mdx
@@ -23,7 +23,12 @@ Locators are the central piece of Playwright's auto-waiting and retry-ability. I
 When the locator points to a list of elements, this returns an array of locators, pointing to their respective elements.
 
 :::note
-[Locator.all()](/api/class-locator.mdx#locator-all) does not wait for elements to match the locator, and instead immediately returns whatever is present in the page.  When the list of elements changes dynamically, [Locator.all()](/api/class-locator.mdx#locator-all) will produce unpredictable and flaky results.  When the list of elements is stable, but loaded dynamically, wait for the full list to finish loading before calling [Locator.all()](/api/class-locator.mdx#locator-all).
+
+[Locator.all()](/api/class-locator.mdx#locator-all) does not wait for elements to match the locator, and instead immediately returns whatever is present in the page.
+
+When the list of elements changes dynamically, [Locator.all()](/api/class-locator.mdx#locator-all) will produce unpredictable and flaky results.
+
+When the list of elements is stable, but loaded dynamically, wait for the full list to finish loading before calling [Locator.all()](/api/class-locator.mdx#locator-all).
 :::
 
 **Usage**
@@ -45,6 +50,7 @@ for (Locator li : page.getByRole('listitem').all())
 Returns an array of `node.innerText` values for all matching nodes.
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [assertThat(locator).hasText()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) with [setUseInnerText](/api/class-locatorassertions.mdx#locator-assertions-to-have-text-option-use-inner-text) option to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -66,6 +72,7 @@ String[] texts = page.getByRole(AriaRole.LINK).allInnerTexts();
 Returns an array of `node.textContent` values for all matching nodes.
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [assertThat(locator).hasText()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -381,6 +388,7 @@ frameLocator.getByRole(AriaRole.BUTTON).click();
 Returns the number of elements matching the locator.
 
 :::warning[Asserting count]
+
 If you need to assert the number of elements on the page, prefer [assertThat(locator).hasCount()](/api/class-locatorassertions.mdx#locator-assertions-to-have-count) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -460,6 +468,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [setTimeout](/api/class-locator.mdx#locator-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `element.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -863,6 +872,7 @@ locator.click();
 Returns the matching element's attribute value.
 
 :::warning[Asserting attributes]
+
 If you need to assert an element's attribute, prefer [assertThat(locator).hasAttribute()](/api/class-locatorassertions.mdx#locator-assertions-to-have-attribute) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1040,6 +1050,7 @@ page.getByRole(AriaRole.BUTTON,
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
@@ -1319,6 +1330,7 @@ Locator.innerHTML(options);
 Returns the [`element.innerText`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/innerText).
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [assertThat(locator).hasText()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) with [setUseInnerText](/api/class-locatorassertions.mdx#locator-assertions-to-have-text-option-use-inner-text) option to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1347,6 +1359,7 @@ Locator.innerText(options);
 Returns the value for the matching `<input>` or `<textarea>` or `<select>` element.
 
 :::warning[Asserting value]
+
 If you need to assert input value, prefer [assertThat(locator).hasValue()](/api/class-locatorassertions.mdx#locator-assertions-to-have-value) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1378,6 +1391,7 @@ Throws elements that are not an input, textarea or a select. However, if the ele
 Returns whether the element is checked. Throws if the element is not a checkbox or radio input.
 
 :::warning[Asserting checked state]
+
 If you need to assert that checkbox is checked, prefer [assertThat(locator).isChecked()](/api/class-locatorassertions.mdx#locator-assertions-to-be-checked) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1405,6 +1419,7 @@ boolean checked = page.getByRole(AriaRole.CHECKBOX).isChecked();
 Returns whether the element is disabled, the opposite of [enabled](../actionability.mdx#enabled).
 
 :::warning[Asserting disabled state]
+
 If you need to assert that an element is disabled, prefer [assertThat(locator).isDisabled()](/api/class-locatorassertions.mdx#locator-assertions-to-be-disabled) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1432,6 +1447,7 @@ boolean disabled = page.getByRole(AriaRole.BUTTON).isDisabled();
 Returns whether the element is [editable](../actionability.mdx#editable).
 
 :::warning[Asserting editable state]
+
 If you need to assert that an element is editable, prefer [assertThat(locator).isEditable()](/api/class-locatorassertions.mdx#locator-assertions-to-be-editable) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1459,6 +1475,7 @@ boolean editable = page.getByRole(AriaRole.TEXTBOX).isEditable();
 Returns whether the element is [enabled](../actionability.mdx#enabled).
 
 :::warning[Asserting enabled state]
+
 If you need to assert that an element is enabled, prefer [assertThat(locator).isEnabled()](/api/class-locatorassertions.mdx#locator-assertions-to-be-enabled) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1486,6 +1503,7 @@ boolean enabled = page.getByRole(AriaRole.BUTTON).isEnabled();
 Returns whether the element is hidden, the opposite of [visible](../actionability.mdx#visible).
 
 :::warning[Asserting visibility]
+
 If you need to assert that element is hidden, prefer [assertThat(locator).isHidden()](/api/class-locatorassertions.mdx#locator-assertions-to-be-hidden) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1516,6 +1534,7 @@ boolean hidden = page.getByRole(AriaRole.BUTTON).isHidden();
 Returns whether the element is [visible](../actionability.mdx#visible).
 
 :::warning[Asserting visibility]
+
 If you need to assert that element is visible, prefer [assertThat(locator).isVisible()](/api/class-locatorassertions.mdx#locator-assertions-to-be-visible) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1726,6 +1745,7 @@ Shortcuts such as `key: "Control+o"`, `key: "Control++` or `key: "Control+Shift+
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.38</font><x-search>locator.pressSequentially</x-search>
 
 :::tip
+
 In most cases, you should use [Locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page.
 :::
 
@@ -2152,6 +2172,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [setTimeout](/api/class-locator.mdx#locator-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `element.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
@@ -2164,6 +2185,7 @@ When all steps combined have not finished during the specified [setTimeout](/api
 Returns the [`node.textContent`](https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent).
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [assertThat(locator).hasText()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
diff --git a/java/docs/api/class-mouse.mdx b/java/docs/api/class-mouse.mdx
index 94eb56e2a3..5600d8d8de 100644
--- a/java/docs/api/class-mouse.mdx
+++ b/java/docs/api/class-mouse.mdx
@@ -187,6 +187,7 @@ Mouse.up(options);
 Dispatches a `wheel` event. This method is usually used to manually scroll the page. See [scrolling](../input.mdx#scrolling) for alternative ways to scroll.
 
 :::note
+
 Wheel events may cause scrolling if they are not handled, and this method does not wait for the scrolling to finish before returning.
 :::
 
diff --git a/java/docs/api/class-page.mdx b/java/docs/api/class-page.mdx
index ea75d4f137..33d1b644ce 100644
--- a/java/docs/api/class-page.mdx
+++ b/java/docs/api/class-page.mdx
@@ -107,7 +107,12 @@ Things to keep in mind:
 * You can register multiple handlers. However, only a single handler will be running at a time. Make sure the actions within a handler don't depend on another handler.
 
 :::warning
-Running the handler will alter your page state mid-test. For example it will change the currently focused element and move the mouse. Make sure that actions that run after the handler are self-contained and do not rely on the focus and mouse state being unchanged. <br /> <br /> For example, consider a test that calls [Locator.focus()](/api/class-locator.mdx#locator-focus) followed by [Keyboard.press()](/api/class-keyboard.mdx#keyboard-press). If your handler clicks a button between these two actions, the focused element most likely will be wrong, and key press will happen on the unexpected element. Use [Locator.press()](/api/class-locator.mdx#locator-press) instead to avoid this problem. <br /> <br /> Another example is a series of mouse actions, where [Mouse.move()](/api/class-mouse.mdx#mouse-move) is followed by [Mouse.down()](/api/class-mouse.mdx#mouse-down). Again, when the handler runs between these two actions, the mouse position will be wrong during the mouse down. Prefer self-contained actions like [Locator.click()](/api/class-locator.mdx#locator-click) that do not rely on the state being unchanged by a handler.
+
+Running the handler will alter your page state mid-test. For example it will change the currently focused element and move the mouse. Make sure that actions that run after the handler are self-contained and do not rely on the focus and mouse state being unchanged.
+
+For example, consider a test that calls [Locator.focus()](/api/class-locator.mdx#locator-focus) followed by [Keyboard.press()](/api/class-keyboard.mdx#keyboard-press). If your handler clicks a button between these two actions, the focused element most likely will be wrong, and key press will happen on the unexpected element. Use [Locator.press()](/api/class-locator.mdx#locator-press) instead to avoid this problem.
+
+Another example is a series of mouse actions, where [Mouse.move()](/api/class-mouse.mdx#mouse-move) is followed by [Mouse.down()](/api/class-mouse.mdx#mouse-down). Again, when the handler runs between these two actions, the mouse position will be wrong during the mouse down. Prefer self-contained actions like [Locator.click()](/api/class-locator.mdx#locator-click) that do not rely on the state being unchanged by a handler.
 :::
 
 **Usage**
@@ -268,6 +273,7 @@ If [setRunBeforeUnload](/api/class-page.mdx#page-close-option-run-before-unload)
 By default, `page.close()` **does not** run `beforeunload` handlers.
 
 :::note
+
 if [setRunBeforeUnload](/api/class-page.mdx#page-close-option-run-before-unload) is passed as true, a `beforeunload` dialog might be summoned and should be handled manually via [Page.onDialog(handler)](/api/class-page.mdx#page-event-dialog) event.
 :::
 
@@ -552,6 +558,7 @@ The first argument of the [callback](/api/class-page.mdx#page-expose-binding-opt
 See [BrowserContext.exposeBinding()](/api/class-browsercontext.mdx#browser-context-expose-binding) for the context-wide version.
 
 :::note
+
 Functions installed via [Page.exposeBinding()](/api/class-page.mdx#page-expose-binding) survive navigations.
 :::
 
@@ -616,6 +623,7 @@ If the [callback](/api/class-page.mdx#page-expose-function-option-callback) retu
 See [BrowserContext.exposeFunction()](/api/class-browsercontext.mdx#browser-context-expose-function) for context-wide exposed function.
 
 :::note
+
 Functions installed via [Page.exposeFunction()](/api/class-page.mdx#page-expose-function) survive navigations.
 :::
 
@@ -674,23 +682,6 @@ public class Example {
 
 ---
 
-### forceGarbageCollection {#page-force-garbage-collection}
-
-<font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.47</font><x-search>page.forceGarbageCollection</x-search>
-
-Force the browser to perform garbage collection.
-
-**Usage**
-
-```java
-Page.forceGarbageCollection();
-```
-
-**Returns**
-- [void]<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="page-force-garbage-collection-return"/><a href="#page-force-garbage-collection-return" class="list-anchor">#</a>
-
----
-
 ### frame {#page-frame}
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.frame</x-search>
@@ -934,6 +925,7 @@ page.getByRole(AriaRole.BUTTON,
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
@@ -1266,6 +1258,7 @@ The method will throw an error if:
 The method will not throw an error when any valid HTTP status code is returned by the remote server, including 404 "Not Found" and 500 "Internal Server Error".  The status code for such responses can be retrieved by calling [Response.status()](/api/class-response.mdx#response-status).
 
 :::note
+
 The method either throws an error or returns a main resource response. The only exceptions are navigation to `about:blank` or navigation to the same URL with a different hash, which would succeed and return `null`.
 :::
 
@@ -1380,6 +1373,7 @@ Pauses script execution. Playwright will stop executing the script and wait for
 User can inspect selectors or perform manual steps while paused. Resume will continue running the original script from the place it was paused.
 
 :::note
+
 This method requires Playwright to be started in a headed mode, with a falsy [setHeadless](/api/class-browsertype.mdx#browser-type-launch-option-headless) option.
 :::
 
@@ -1401,12 +1395,14 @@ Page.pause();
 Returns the PDF buffer.
 
 :::note
+
 Generating a pdf is currently only supported in Chromium headless.
 :::
 
 `page.pdf()` generates a pdf of the page with `print` css media. To generate a pdf with `screen` media, call [Page.emulateMedia()](/api/class-page.mdx#page-emulate-media) before calling `page.pdf()`:
 
 :::note
+
 By default, `page.pdf()` generates a pdf with modified colors for printing. Use the [`-webkit-print-color-adjust`](https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-print-color-adjust) property to force rendering of exact colors.
 :::
 
@@ -1445,6 +1441,7 @@ The [setFormat](/api/class-page.mdx#page-pdf-option-format) options are:
 * `A6`: 4.13in x 5.83in
 
 :::note
+
 [setHeaderTemplate](/api/class-page.mdx#page-pdf-option-header-template) and [setFooterTemplate](/api/class-page.mdx#page-pdf-option-footer-template) markup have the following limitations: > 1. Script tags inside templates are not evaluated. > 2. Page styles are not visible inside templates.
 :::
 
@@ -1571,6 +1568,34 @@ Page.removeLocatorHandler(locator);
 
 ---
 
+### requestGC {#page-request-gc}
+
+<font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.48</font><x-search>page.requestGC</x-search>
+
+Request the page to perform garbage collection. Note that there is no guarantee that all unreachable objects will be collected.
+
+This is useful to help detect memory leaks. For example, if your page has a large object `'suspect'` that might be leaked, you can check that it does not leak by using a [`WeakRef`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakRef).
+
+```java
+// 1. In your page, save a WeakRef for the "suspect".
+page.evaluate("globalThis.suspectWeakRef = new WeakRef(suspect)");
+// 2. Request garbage collection.
+page.requestGC();
+// 3. Check that weak ref does not deref to the original object.
+assertTrue(page.evaluate("!globalThis.suspectWeakRef.deref()"));
+```
+
+**Usage**
+
+```java
+Page.requestGC();
+```
+
+**Returns**
+- [void]<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="page-request-gc-return"/><a href="#page-request-gc-return" class="list-anchor">#</a>
+
+---
+
 ### route {#page-route}
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.route</x-search>
@@ -1580,6 +1605,7 @@ Routing provides the capability to modify network requests that are made by a pa
 Once routing is enabled, every request matching the url pattern will stall unless it's continued, fulfilled or aborted.
 
 :::note
+
 The handler will only be called for the first url if the response is a redirect.
 :::
 
@@ -1627,6 +1653,7 @@ Page routes take precedence over browser context routes (set up with [BrowserCon
 To remove a route with its handler you can use [Page.unroute()](/api/class-page.mdx#page-unroute).
 
 :::note
+
 Enabling routing disables http cache.
 :::
 
@@ -1852,6 +1879,7 @@ This setting will change the default maximum navigation time for the following m
 * [Page.waitForURL()](/api/class-page.mdx#page-wait-for-url)
 
 :::note
+
 [Page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) takes priority over [Page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout), [BrowserContext.setDefaultTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout) and [BrowserContext.setDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout).
 :::
 
@@ -1875,6 +1903,7 @@ Page.setDefaultNavigationTimeout(timeout);
 This setting will change the default maximum time for all the methods accepting [timeout](/api/class-page.mdx#page-set-default-timeout-option-timeout) option.
 
 :::note
+
 [Page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) takes priority over [Page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout).
 :::
 
@@ -1898,6 +1927,7 @@ Page.setDefaultTimeout(timeout);
 The extra HTTP headers will be sent with every request the page initiates.
 
 :::note
+
 [Page.setExtraHTTPHeaders()](/api/class-page.mdx#page-set-extra-http-headers) does not guarantee the order of headers in the outgoing requests.
 :::
 
@@ -2266,6 +2296,7 @@ Returns when the required load state has been reached.
 This resolves when the page reaches a required load state, `load` by default. The navigation must have been committed when this method is called. If current document has already reached the required state, resolves immediately.
 
 :::note
+
 Most of the time, this method is not needed because Playwright [auto-waits before every action](../actionability.mdx).
 :::
 
@@ -2541,6 +2572,7 @@ Page.waitForWorker(callback, options);
 This method returns all of the dedicated [WebWorkers](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API) associated with the page.
 
 :::note
+
 This does not contain ServiceWorkers
 :::
 
@@ -3192,6 +3224,7 @@ This method double clicks an element matching [selector](/api/class-page.mdx#pag
 When all steps combined have not finished during the specified [setTimeout](/api/class-page.mdx#page-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `page.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -4287,6 +4320,7 @@ This method taps an element matching [selector](/api/class-page.mdx#page-tap-opt
 When all steps combined have not finished during the specified [setTimeout](/api/class-page.mdx#page-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 [Page.tap()](/api/class-page.mdx#page-tap) the method will throw if [setHasTouch](/api/class-browser.mdx#browser-new-context-option-has-touch) option of the browser context is false.
 :::
 
@@ -4558,6 +4592,7 @@ Use web assertions that assert visibility or a locator-based [Locator.waitFor()]
 Returns when element specified by selector satisfies [setState](/api/class-page.mdx#page-wait-for-selector-option-state) option. Returns `null` if waiting for `hidden` or `detached`.
 
 :::note
+
 Playwright automatically waits for element to be ready before performing an action. Using [Locator] objects and web-first assertions makes the code wait-for-selector-free.
 :::
 
diff --git a/java/docs/api/class-request.mdx b/java/docs/api/class-request.mdx
index cc2f6a29c5..5bd6285c93 100644
--- a/java/docs/api/class-request.mdx
+++ b/java/docs/api/class-request.mdx
@@ -15,6 +15,7 @@ Whenever the page sends a request for a network resource the following sequence
 If request fails at some point, then instead of `'requestfinished'` event (and possibly instead of 'response' event), the  [Page.onRequestFailed(handler)](/api/class-page.mdx#page-event-request-failed) event is emitted.
 
 :::note
+
 HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with `'requestfinished'` event.
 :::
 
diff --git a/java/docs/api/class-touchscreen.mdx b/java/docs/api/class-touchscreen.mdx
index a25f9aa11a..ed95de5310 100644
--- a/java/docs/api/class-touchscreen.mdx
+++ b/java/docs/api/class-touchscreen.mdx
@@ -21,6 +21,7 @@ The Touchscreen class operates in main-frame CSS pixels relative to the top-left
 Dispatches a `touchstart` and `touchend` event with a single touch at the position ([x](/api/class-touchscreen.mdx#touchscreen-tap-option-x),[y](/api/class-touchscreen.mdx#touchscreen-tap-option-y)).
 
 :::note
+
 [Page.tap()](/api/class-page.mdx#page-tap) the method will throw if [setHasTouch](/api/class-browser.mdx#browser-new-context-option-has-touch) option of the browser context is false.
 :::
 
diff --git a/java/docs/browsers.mdx b/java/docs/browsers.mdx
index c52e1e1a4f..b3278ba970 100644
--- a/java/docs/browsers.mdx
+++ b/java/docs/browsers.mdx
@@ -112,6 +112,7 @@ While Playwright can download and use the recent Chromium build, it can operate
 Available channels are `chrome`, `msedge`, `chrome-beta`, `msedge-beta` or `msedge-dev`.
 
 :::warning
+
 Certain Enterprise Browser Policies may impact Playwright's ability to launch and control Google Chrome and Microsoft Edge. Running in an environment with browser policies is outside of the Playwright project's scope.
 :::
 
@@ -459,6 +460,7 @@ mvn test
 Playwright keeps track of packages that need those browsers and will garbage collect them as you update Playwright to the newer versions.
 
 :::note
+
 Developers can opt-in in this mode via exporting `PLAYWRIGHT_BROWSERS_PATH=$HOME/pw-browsers` in their `.bashrc`.
 :::
 
diff --git a/java/docs/ci.mdx b/java/docs/ci.mdx
index 07835b35f0..fac0e4456b 100644
--- a/java/docs/ci.mdx
+++ b/java/docs/ci.mdx
@@ -75,7 +75,7 @@ jobs:
     name: 'Playwright Tests'
     runs-on: ubuntu-latest
     container:
-      image: mcr.microsoft.com/playwright/java:v1.47.0-jammy
+      image: mcr.microsoft.com/playwright/java:vv1.47.0-jammy
       options: --user 1001
     steps:
       - uses: actions/checkout@v4
@@ -165,7 +165,7 @@ trigger:
 
 pool:
   vmImage: ubuntu-latest
-container: mcr.microsoft.com/playwright/java:v1.47.0-noble
+container: mcr.microsoft.com/playwright/java:vv1.47.0-noble
 
 steps:
 - task: JavaToolInstaller@0
@@ -188,7 +188,7 @@ Running Playwright on CircleCI is very similar to running on GitHub Actions. In
 executors:
   pw-jammy-development:
     docker:
-      - image: mcr.microsoft.com/playwright/java:v1.47.0-noble
+      - image: mcr.microsoft.com/playwright/java:vv1.47.0-noble
 ```
 
 Note: When using the docker agent definition, you are specifying the resource class of where playwright runs to the 'medium' tier [here](https://circleci.com/docs/configuration-reference?#docker-execution-environment). The default behavior of Playwright is to set the number of workers to the detected core count (2 in the case of the medium tier). Overriding the number of workers to greater than this number will cause unnecessary timeouts and failures.
@@ -199,7 +199,7 @@ Jenkins supports Docker agents for pipelines. Use the [Playwright Docker image](
 
 ```groovy
 pipeline {
-   agent { docker { image 'mcr.microsoft.com/playwright/java:v1.47.0-noble' } }
+   agent { docker { image 'mcr.microsoft.com/playwright/java:vv1.47.0-noble' } }
    stages {
       stage('e2e-tests') {
          steps {
@@ -216,7 +216,7 @@ pipeline {
 Bitbucket Pipelines can use public [Docker images as build environments](https://confluence.atlassian.com/bitbucket/use-docker-images-as-build-environments-792298897.html). To run Playwright tests on Bitbucket, use our public Docker image ([see Dockerfile](./docker.mdx)).
 
 ```yml
-image: mcr.microsoft.com/playwright/java:v1.47.0-noble
+image: mcr.microsoft.com/playwright/java:vv1.47.0-noble
 ```
 
 ### GitLab CI
@@ -229,7 +229,7 @@ stages:
 
 tests:
   stage: test
-  image: mcr.microsoft.com/playwright/java:v1.47.0-noble
+  image: mcr.microsoft.com/playwright/java:vv1.47.0-noble
   script:
   ...
 ```
diff --git a/java/docs/clock.mdx b/java/docs/clock.mdx
index 2f59ad17c5..8712aa6142 100644
--- a/java/docs/clock.mdx
+++ b/java/docs/clock.mdx
@@ -24,7 +24,19 @@ The [Clock] API provides the following methods to control time:
 The recommended approach is to use `setFixedTime` to set the time to a specific value. If that doesn't work for your use case, you can use `install` which allows you to pause time later on, fast forward it, tick it, etc. `setSystemTime` is only recommended for advanced use cases.
 
 :::note
-[Page.clock()](/api/class-page.mdx#page-clock) overrides native global classes and functions related to time allowing them to be manually controlled:   - `Date`   - `setTimeout`   - `clearTimeout`   - `setInterval`   - `clearInterval`   - `requestAnimationFrame`   - `cancelAnimationFrame`   - `requestIdleCallback`   - `cancelIdleCallback`   - `performance`   - `Event.timeStamp`
+
+[Page.clock()](/api/class-page.mdx#page-clock) overrides native global classes and functions related to time allowing them to be manually controlled:
+- `Date`
+- `setTimeout`
+- `clearTimeout`
+- `setInterval`
+- `clearInterval`
+- `requestAnimationFrame`
+- `cancelAnimationFrame`
+- `requestIdleCallback`
+- `cancelIdleCallback`
+- `performance`
+- `Event.timeStamp`
 :::
 
 ## Test with predefined time
diff --git a/java/docs/debug.mdx b/java/docs/debug.mdx
index b3450ed9fc..086e5b6740 100644
--- a/java/docs/debug.mdx
+++ b/java/docs/debug.mdx
@@ -260,6 +260,7 @@ mvn test
 </Tabs>
 
 :::note
+
 **For WebKit**: launching WebKit Inspector during the execution will prevent the Playwright script from executing any further and will reset pre-configured user agent and device emulation.
 :::
 
diff --git a/java/docs/dialogs.mdx b/java/docs/dialogs.mdx
index b717247800..4da2ce99a2 100644
--- a/java/docs/dialogs.mdx
+++ b/java/docs/dialogs.mdx
@@ -26,6 +26,7 @@ page.getByRole(AriaRole.BUTTON).click();
 As a result, the following snippet will never resolve:
 
 :::warning
+
 WRONG!
 :::
 
diff --git a/java/docs/docker.mdx b/java/docs/docker.mdx
index bad38da144..b54367770d 100644
--- a/java/docs/docker.mdx
+++ b/java/docs/docker.mdx
@@ -15,13 +15,14 @@ import HTMLCard from '@site/src/components/HTMLCard';
 This Docker image is published to [Microsoft Artifact Registry].
 
 :::info
+
 This Docker image is intended to be used for testing and development purposes only. It is not recommended to use this Docker image to visit untrusted websites.
 :::
 
 ### Pull the image
 
 ```bash
-docker pull mcr.microsoft.com/playwright/java:v1.47.0-noble
+docker pull mcr.microsoft.com/playwright/java:vv1.47.0-noble
 ```
 
 ### Run the image
@@ -33,7 +34,7 @@ By default, the Docker image will use the `root` user to run the browsers. This
 On trusted websites, you can avoid creating a separate user and use root for it since you trust the code which will run on the browsers.
 
 ```bash
-docker run -it --rm --ipc=host mcr.microsoft.com/playwright/java:v1.47.0-noble /bin/bash
+docker run -it --rm --ipc=host mcr.microsoft.com/playwright/java:vv1.47.0-noble /bin/bash
 ```
 
 #### Crawling and scraping
@@ -41,7 +42,7 @@ docker run -it --rm --ipc=host mcr.microsoft.com/playwright/java:v1.47.0-noble /
 On untrusted websites, it's recommended to use a separate user for launching the browsers in combination with the seccomp profile. Inside the container or if you are using the Docker image as a base image you have to use `adduser` for it.
 
 ```bash
-docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright/java:v1.47.0-noble /bin/bash
+docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright/java:vv1.47.0-noble /bin/bash
 ```
 
 [`seccomp_profile.json`](https://github.com/microsoft/playwright/blob/main/utils/docker/seccomp_profile.json) is needed to run Chromium with sandbox. This is a [default Docker seccomp profile](https://github.com/docker/engine/blob/d0d99b04cf6e00ed3fc27e81fc3d94e7eda70af3/profiles/seccomp/default.json) with extra user namespace cloning permissions:
@@ -74,12 +75,13 @@ See our [Continuous Integration guides](./ci.mdx) for sample configs.
 See [all available image tags].
 
 We currently publish images with the following tags:
-- `:v1.47.0` - Playwright v1.47.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
-- `:v1.47.0-noble` - Playwright v1.47.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
-- `:v1.47.0-jammy` - Playwright v1.47.0 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish).
-- `:v1.47.0-focal` - Playwright v1.47.0 release docker image based on Ubuntu 20.04 LTS (Focal Fossa).
+- `:vv1.47.0` - Playwright vv1.47.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
+- `:vv1.47.0-noble` - Playwright vv1.47.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
+- `:vv1.47.0-jammy` - Playwright vv1.47.0 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish).
+- `:vv1.47.0-focal` - Playwright vv1.47.0 release docker image based on Ubuntu 20.04 LTS (Focal Fossa).
 
 :::note
+
 It is recommended to always pin your Docker image to a specific version if possible. If the Playwright version in your Docker image does not match the version in your project/tests, Playwright will be unable to locate browser executables.
 :::
 
diff --git a/java/docs/downloads.mdx b/java/docs/downloads.mdx
index 1ae1cfe962..bb2f2a2390 100644
--- a/java/docs/downloads.mdx
+++ b/java/docs/downloads.mdx
@@ -13,6 +13,7 @@ For every attachment downloaded by the page, [Page.onDownload(handler)](/api/cla
 You can specify where to persist downloaded files using the [setDownloadsPath](/api/class-browsertype.mdx#browser-type-launch-option-downloads-path) option in [BrowserType.launch()](/api/class-browsertype.mdx#browser-type-launch).
 
 :::note
+
 Downloaded files are deleted when the browser context that produced them is closed.
 :::
 
@@ -40,6 +41,7 @@ page.onDownload(download -> System.out.println(download.path()));
 Note that handling the event forks the control flow and makes the script harder to follow. Your scenario might end while you are downloading a file since your main control flow is not awaiting for this operation to resolve.
 
 :::note
+
 For uploading files, see the [uploading files](./input.mdx#upload-files) section.
 :::
 
diff --git a/java/docs/handles.mdx b/java/docs/handles.mdx
index 81db1d2cf5..236b4b4ab5 100644
--- a/java/docs/handles.mdx
+++ b/java/docs/handles.mdx
@@ -30,6 +30,7 @@ JSHandle jsHandle = page.evaluateHandle("window");
 ## Element Handles
 
 :::warning[Discouraged]
+
 The use of [ElementHandle] is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -93,6 +94,7 @@ Handles can be acquired using the page methods such as [Page.evaluateHandle()](/
 ## Locator vs ElementHandle
 
 :::caution
+
 We only recommend using [ElementHandle] in the rare cases when you need to perform extensive DOM traversal on a static page. For all user actions and assertions use locator instead.
 :::
 
diff --git a/java/docs/input.mdx b/java/docs/input.mdx
index 664a9b9780..7cc27d73b3 100644
--- a/java/docs/input.mdx
+++ b/java/docs/input.mdx
@@ -113,6 +113,7 @@ page.getByRole(AriaRole.BUTTON).dispatchEvent("click");
 ## Type characters
 
 :::caution
+
 Most of the time, you should input text with [Locator.fill()](/api/class-locator.mdx#locator-fill). See the [Text input](#text-input) section above. You only need to type characters if there is special keyboard handling on the page.
 :::
 
diff --git a/java/docs/intro.mdx b/java/docs/intro.mdx
index 86daa0899e..8d762f6990 100644
--- a/java/docs/intro.mdx
+++ b/java/docs/intro.mdx
@@ -58,7 +58,7 @@ public class App {
     <dependency>
       <groupId>com.microsoft.playwright</groupId>
       <artifactId>playwright</artifactId>
-      <version>1.47.0</version>
+      <version>v1.47.0</version>
     </dependency>
   </dependencies>
   <build>
diff --git a/java/docs/locators.mdx b/java/docs/locators.mdx
index 5fdd596586..74779969b2 100644
--- a/java/docs/locators.mdx
+++ b/java/docs/locators.mdx
@@ -128,6 +128,7 @@ Role locators include [buttons, checkboxes, headings, links, lists, tables, and
 Note that role locators **do not replace** accessibility audits and conformance tests, but rather give early feedback about the ARIA guidelines.
 
 :::note[When to use role locators]
+
 We recommend prioritizing role locators to locate elements, as it is the closest way to how users and assistive technology perceive the page.
 :::
 
@@ -607,6 +608,7 @@ If you'd like to target one of the two or more elements, and you don't know whic
 For example, consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead. In this case, you can wait for either a "New email" button, or a dialog and act accordingly.
 
 :::note
+
 If both "New email" button and security dialog appear on screen, the "or" locator will match both of them, possibly throwing the ["strict mode violation" error](#strictness). In this case, you can use [Locator.first()](/api/class-locator.mdx#locator-first) to only match one of them.
 :::
 
@@ -622,6 +624,7 @@ newEmail.click();
 ### Matching only visible elements
 
 :::note
+
 It's usually better to find a [more reliable way](./locators.mdx#quick-guide) to uniquely identify the element instead of checking the visibility.
 :::
 
diff --git a/java/docs/navigations.mdx b/java/docs/navigations.mdx
index 5b612648d4..d564603fb3 100644
--- a/java/docs/navigations.mdx
+++ b/java/docs/navigations.mdx
@@ -22,6 +22,7 @@ page.navigate("https://example.com");
 The code above loads the page and waits for the web page to fire the [load](https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event) event. The load event is fired when the whole page has loaded, including all dependent resources such as stylesheets, scripts, iframes, and images.
 
 :::note
+
 If the page does a client-side redirect before `load`, [Page.navigate()](/api/class-page.mdx#page-goto) will wait for the redirected page to fire the `load` event.
 :::
 
diff --git a/java/docs/other-locators.mdx b/java/docs/other-locators.mdx
index 468250ce68..46473bb328 100644
--- a/java/docs/other-locators.mdx
+++ b/java/docs/other-locators.mdx
@@ -9,6 +9,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ## Introduction
 
 :::note
+
 Check out the main [locators guide](./locators) for most common and recommended locators.
 :::
 
@@ -17,6 +18,7 @@ In addition to recommended locators like [Page.getByRole()](/api/class-page.mdx#
 ## CSS locator
 
 :::note
+
 We recommend prioritizing [user-visible locators](./locators.mdx#quick-guide) like text or accessible role instead of using CSS that is tied to the implementation and could break when the page changes.
 :::
 
@@ -64,6 +66,7 @@ Playwright include a number of CSS pseudo-classes to match elements by their tex
   For example, `:text-matches("Log\s*in", "i")` matches `<button>Login</button>` and `<button>log IN</button>`.
 
 :::note
+
 Text matching always normalizes whitespace. For example, it turns multiple spaces into one, turns line breaks into spaces and ignores leading and trailing whitespace.
 :::
 
@@ -118,6 +121,7 @@ The `:is()` pseudo-class is an [experimental CSS pseudo-class](https://developer
 ### CSS: matching elements based on layout
 
 :::note
+
 Matching based on layout may produce unexpected results. For example, a different element could be matched when layout changes by one pixel.
 :::
 
@@ -152,6 +156,7 @@ All layout pseudo-classes support optional maximum pixel distance as the last ar
 ### CSS: pick n-th match from the query result
 
 :::note
+
 It is usually possible to distinguish elements by some attribute or text content, which is more resilient to page changes.
 :::
 
@@ -218,6 +223,7 @@ Locator parent = page.getByText("Hello").locator("xpath=..");
 ## React locator
 
 :::note
+
 React locator is experimental and prefixed with `_`. The functionality might change in future.
 :::
 
@@ -246,6 +252,7 @@ More examples:
 To find React element names in a tree use [React DevTools](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi).
 
 :::note
+
 React locator supports React 15 and above.
 :::
 
@@ -256,6 +263,7 @@ React locator, as well as [React DevTools](https://chrome.google.com/webstore/de
 ## Vue locator
 
 :::note
+
 Vue locator is experimental and prefixed with `_`. The functionality might change in future.
 :::
 
@@ -283,6 +291,7 @@ More examples:
 To find Vue element names in a tree use [Vue DevTools](https://chrome.google.com/webstore/detail/vuejs-devtools/nhdogjmejiglipccpnnnanhbledajbpd?hl=en).
 
 :::note
+
 Vue locator supports Vue2 and above.
 :::
 
@@ -293,6 +302,7 @@ Vue locator, as well as [Vue DevTools](https://chrome.google.com/webstore/detail
 ## XPath locator
 
 :::warning
+
 We recommend prioritizing [user-visible locators](./locators.mdx#quick-guide) like text or accessible role instead of using XPath that is tied to the implementation and easily break when the page changes.
 :::
 
@@ -322,6 +332,7 @@ page.locator("//span[contains(@class, 'spinner__loading')]|//div[@id='confirmati
 ## Label to form control retargeting
 
 :::warning
+
 We recommend [locating by label text](./locators.mdx#locate-by-label) instead of relying to label-to-control retargeting.
 :::
 
@@ -350,6 +361,7 @@ assertThat(page.locator("label")).hasText("Password");
 ## Legacy text locator
 
 :::warning
+
 We recommend the modern [text locator](./locators.mdx#get-by-text) instead.
 :::
 
@@ -383,6 +395,7 @@ Legacy text locator has a few variations:
   ```
   
 :::note
+
 String selectors starting and ending with a quote (either `"` or `'`) are assumed to be a legacy text locators. For example, `"Log in"` is converted to `text="Log in"` internally.
 :::
 
@@ -397,6 +410,7 @@ Input elements of the type `button` and `submit` are matched by their `value` in
 ## id, data-testid, data-test-id, data-test selectors
 
 :::warning
+
 We recommend [locating by test id](./locators.mdx#locate-by-test-id) instead.
 :::
 
@@ -421,6 +435,7 @@ Attribute selectors are not CSS selectors, so anything CSS-specific like `:enabl
 ## Chaining selectors
 
 :::warning
+
 We recommend [chaining locators](./locators.mdx#matching-inside-a-locator) instead.
 :::
 
@@ -446,6 +461,7 @@ If a selector needs to include `>>` in the body, it should be escaped inside a s
 ### Intermediate matches
 
 :::warning
+
 We recommend [filtering by another locator](./locators.mdx#filter-by-childdescendant) to locate elements that contain other elements.
 :::
 
diff --git a/java/docs/selenium-grid.mdx b/java/docs/selenium-grid.mdx
index 4acdf1c8bb..edec8733ae 100644
--- a/java/docs/selenium-grid.mdx
+++ b/java/docs/selenium-grid.mdx
@@ -11,7 +11,20 @@ import HTMLCard from '@site/src/components/HTMLCard';
 Playwright can connect to [Selenium Grid Hub](https://www.selenium.dev/documentation/grid/) that runs Selenium 4 to launch **Google Chrome** or **Microsoft Edge** browser, instead of running browser on the local machine. Note this feature is **experimental** and is prioritized accordingly.
 
 :::warning
-There is a risk of Playwright integration with Selenium Grid Hub breaking in the future. Make sure you weight risks against benefits before using it.  <br /> <br /> <details> <summary> <span style={{textTransform:'uppercase',fontSize:'smaller',fontWeight:'bold',opacity:'0.6'}}>More details</span> </summary>  Internally, Playwright connects to the browser using [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) websocket. Selenium 4 currently exposes this capability. However, this [might not be the case in the future](https://github.com/SeleniumHQ/selenium/issues/11590#issuecomment-1436113950). If Selenium drops this capability, Playwright will stop working with it. </details>
+
+There is a risk of Playwright integration with Selenium Grid Hub breaking in the future. Make sure you weight risks against benefits before using it.
+
+<details>
+
+<summary>
+
+<span style={{textTransform:'uppercase',fontSize:'smaller',fontWeight:'bold',opacity:'0.6'}}>More details</span>
+
+</summary>
+
+Internally, Playwright connects to the browser using [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) websocket. Selenium 4 currently exposes this capability. However, this [might not be the case in the future](https://github.com/SeleniumHQ/selenium/issues/11590#issuecomment-1436113950). If Selenium drops this capability, Playwright will stop working with it.
+
+</details>
 :::
 
 Before connecting Playwright to your Selenium Grid, make sure that grid works with [Selenium WebDriver](https://www.selenium.dev/documentation/webdriver/). For example, run [one of the examples](https://github.com/SeleniumHQ/selenium/tree/trunk/javascript/node/selenium-webdriver/example) and pass `SELENIUM_REMOTE_URL` environment variable. If webdriver example does not work, look for any errors at your Selenium hub/node/standalone output and search [Selenium issues](https://github.com/SeleniumHQ/selenium/issues) for a possible solution.
diff --git a/java/docs/test-runners.mdx b/java/docs/test-runners.mdx
index 4a2399a1f9..3071ea774a 100644
--- a/java/docs/test-runners.mdx
+++ b/java/docs/test-runners.mdx
@@ -198,7 +198,7 @@ repositories {
 }
 
 dependencies {
-  implementation 'com.microsoft.playwright:playwright:1.47.0'
+  implementation 'com.microsoft.playwright:playwright:v1.47.0'
 }
 
 application {
@@ -231,7 +231,7 @@ repositories {
 }
 
 dependencies {
-  implementation("com.microsoft.playwright:playwright:1.47.0")
+  implementation("com.microsoft.playwright:playwright:v1.47.0")
 }
 
 application {
diff --git a/java/docs/trace-viewer.mdx b/java/docs/trace-viewer.mdx
index f5b4956518..3181ad36b2 100644
--- a/java/docs/trace-viewer.mdx
+++ b/java/docs/trace-viewer.mdx
@@ -43,8 +43,6 @@ When tracing with the [setSnapshots](/api/class-tracing.mdx#tracing-start-option
 |Action|A snapshot at the moment of the performed input. This type of snapshot is especially useful when exploring where exactly Playwright clicked.|
 |After|A snapshot after the action.|
 
-<br/>
-
 Here is what the typical Action snapshot looks like:
 
 ![action tab in trace viewer](https://github.com/microsoft/playwright/assets/13063165/7168d549-eb0a-4964-9c93-483f03711fa9)
diff --git a/nodejs/docs/accessibility-testing.mdx b/nodejs/docs/accessibility-testing.mdx
index b80c6c4d7b..2f00fdb83f 100644
--- a/nodejs/docs/accessibility-testing.mdx
+++ b/nodejs/docs/accessibility-testing.mdx
@@ -18,7 +18,10 @@ A few examples of problems this can catch include:
 The following examples rely on the [`@axe-core/playwright`](https://npmjs.org/@axe-core/playwright) package which adds support for running the [axe accessibility testing engine](https://www.deque.com/axe/) as part of your Playwright tests.
 
 :::note[Disclaimer]
-Automated accessibility tests can detect some common accessibility problems such as missing or invalid properties. But many accessibility problems can only be discovered through manual testing. We recommend using a combination of automated testing, manual accessibility assessments, and inclusive user testing.  For manual assessments, we recommend [Accessibility Insights for Web](https://accessibilityinsights.io/docs/web/overview/?referrer=playwright-accessibility-testing-js), a free and open source dev tool that walks you through assessing a website for [WCAG 2.1 AA](https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&levels=aaa) coverage.
+
+Automated accessibility tests can detect some common accessibility problems such as missing or invalid properties. But many accessibility problems can only be discovered through manual testing. We recommend using a combination of automated testing, manual accessibility assessments, and inclusive user testing.
+
+For manual assessments, we recommend [Accessibility Insights for Web](https://accessibilityinsights.io/docs/web/overview/?referrer=playwright-accessibility-testing-js), a free and open source dev tool that walks you through assessing a website for [WCAG 2.1 AA](https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&levels=aaa) coverage.
 :::
 
 ## Example accessibility tests
diff --git a/nodejs/docs/api/class-accessibility.mdx b/nodejs/docs/api/class-accessibility.mdx
index 16fa83e97c..f0fd146a85 100644
--- a/nodejs/docs/api/class-accessibility.mdx
+++ b/nodejs/docs/api/class-accessibility.mdx
@@ -34,6 +34,7 @@ This method is deprecated. Please use other libraries such as [Axe](https://www.
 Captures the current state of the accessibility tree. The returned object represents the root accessible node of the page.
 
 :::note
+
 The Chromium accessibility tree contains nodes that go unused on most platforms and by most screen readers. Playwright will discard them as well for an easier to process tree, unless [interestingOnly](/api/class-accessibility.mdx#accessibility-snapshot-option-interesting-only) is set to `false`.
 :::
 
diff --git a/nodejs/docs/api/class-android.mdx b/nodejs/docs/api/class-android.mdx
index 09895ee00c..bffe33aa35 100644
--- a/nodejs/docs/api/class-android.mdx
+++ b/nodejs/docs/api/class-android.mdx
@@ -217,6 +217,7 @@ const { _android } = require('playwright');
     Path at which to serve the Android Server. For security, this defaults to an unguessable string.
     
     :::warning
+    
     Any process or web page (including those running in Playwright) with knowledge of the `wsPath` can take control of the OS user. For this reason, you should use an unguessable token when using this option.
     :::
     
diff --git a/nodejs/docs/api/class-androiddevice.mdx b/nodejs/docs/api/class-androiddevice.mdx
index 52f698b379..99079e4a5f 100644
--- a/nodejs/docs/api/class-androiddevice.mdx
+++ b/nodejs/docs/api/class-androiddevice.mdx
@@ -202,6 +202,7 @@ await androidDevice.launchBrowser(options);
   - `args` [Array]&lt;[string]&gt; *(optional)* <font size="2">Added in: v1.29</font><a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="android-device-launch-browser-option-args"/><a href="#android-device-launch-browser-option-args" class="list-anchor">#</a>
     
     :::warning
+    
     Use custom browser args at your own risk, as some of them may break Playwright functionality.
     :::
     
@@ -382,6 +383,7 @@ await androidDevice.launchBrowser(options);
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `null` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation#viewport).
     
     :::note
+    
     The `null` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
diff --git a/nodejs/docs/api/class-apirequest.mdx b/nodejs/docs/api/class-apirequest.mdx
index 729ffcea31..c3fd59c386 100644
--- a/nodejs/docs/api/class-apirequest.mdx
+++ b/nodejs/docs/api/class-apirequest.mdx
@@ -68,6 +68,7 @@ await apiRequest.newContext(options);
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
diff --git a/nodejs/docs/api/class-browser.mdx b/nodejs/docs/api/class-browser.mdx
index 7821017fee..c790cf5c7d 100644
--- a/nodejs/docs/api/class-browser.mdx
+++ b/nodejs/docs/api/class-browser.mdx
@@ -51,6 +51,7 @@ In case this browser is obtained using [browserType.launch()](/api/class-browser
 In case this browser is connected to, clears all created contexts belonging to this browser and disconnects from the browser server.
 
 :::note
+
 This is similar to force quitting the browser. Therefore, you should call [browserContext.close()](/api/class-browsercontext.mdx#browser-context-close) on any [BrowserContext]'s you explicitly created earlier with [browser.newContext()](/api/class-browser.mdx#browser-new-context) **before** calling [browser.close()](/api/class-browser.mdx#browser-close).
 :::
 
@@ -117,6 +118,7 @@ browser.isConnected();
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.newBrowserCDPSession</x-search>
 
 :::note
+
 CDP Sessions are only supported on Chromium-based browsers.
 :::
 
@@ -140,6 +142,7 @@ await browser.newBrowserCDPSession();
 Creates a new browser context. It won't share cookies/cache with other browser contexts.
 
 :::note
+
 If directly using this method to create [BrowserContext]s, it is best practice to explicitly close the returned context via [browserContext.close()](/api/class-browsercontext.mdx#browser-context-close) when your code is done with the [BrowserContext], and before calling [browser.close()](/api/class-browser.mdx#browser-close). This will ensure the `context` is closed gracefully and any artifacts—like HARs and videos—are fully flushed and saved.
 :::
 
@@ -207,6 +210,7 @@ If directly using this method to create [BrowserContext]s, it is best practice t
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
@@ -419,6 +423,7 @@ If directly using this method to create [BrowserContext]s, it is best practice t
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `null` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation#viewport).
     
     :::note
+    
     The `null` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
@@ -489,6 +494,7 @@ await browser.newPage(options);
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
@@ -701,6 +707,7 @@ await browser.newPage(options);
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `null` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation#viewport).
     
     :::note
+    
     The `null` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
@@ -742,6 +749,7 @@ await browser.removeAllListeners(type, options);
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.startTracing</x-search>
 
 :::note
+
 This API controls [Chromium Tracing](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool) which is a low-level chromium-specific debugging tool. API to control [Playwright Tracing](../trace-viewer) could be found [here](./class-tracing).
 :::
 
@@ -780,6 +788,7 @@ await browser.stopTracing();
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.stopTracing</x-search>
 
 :::note
+
 This API controls [Chromium Tracing](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool) which is a low-level chromium-specific debugging tool. API to control [Playwright Tracing](../trace-viewer) could be found [here](./class-tracing).
 :::
 
diff --git a/nodejs/docs/api/class-browsercontext.mdx b/nodejs/docs/api/class-browsercontext.mdx
index 38cd28b4b3..61e5afb1d9 100644
--- a/nodejs/docs/api/class-browsercontext.mdx
+++ b/nodejs/docs/api/class-browsercontext.mdx
@@ -129,6 +129,7 @@ The order of evaluation of multiple scripts installed via [browserContext.addIni
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.backgroundPages</x-search>
 
 :::note
+
 Background pages are only supported on Chromium-based browsers.
 :::
 
@@ -223,6 +224,7 @@ context.clearPermissions();
 Closes the browser context. All the pages that belong to the browser context will be closed.
 
 :::note
+
 The default browser context cannot be closed.
 :::
 
@@ -446,6 +448,7 @@ await browserContext.grantPermissions(permissions, options);
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.newCDPSession</x-search>
 
 :::note
+
 CDP sessions are only supported on Chromium-based browsers.
 :::
 
@@ -536,6 +539,7 @@ await browserContext.removeAllListeners(type, options);
 Routing provides the capability to modify network requests that are made by any page in the browser context. Once route is enabled, every request matching the url pattern will stall unless it's continued, fulfilled or aborted.
 
 :::note
+
 [browserContext.route()](/api/class-browsercontext.mdx#browser-context-route) will not intercept requests intercepted by Service Worker. See [this](https://github.com/microsoft/playwright/issues/1090) issue. We recommend disabling Service Workers when using request interception by setting [serviceWorkers](/api/class-browser.mdx#browser-new-context-option-service-workers) to `'block'`.
 :::
 
@@ -577,6 +581,7 @@ Page routes (set up with [page.route()](/api/class-page.mdx#page-route)) take pr
 To remove a route with its handler you can use [browserContext.unroute()](/api/class-browsercontext.mdx#browser-context-unroute).
 
 :::note
+
 Enabling routing disables http cache.
 :::
 
@@ -681,6 +686,7 @@ await context.routeWebSocket('/ws', async ws => {
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.serviceWorkers</x-search>
 
 :::note
+
 Service workers are only supported on Chromium-based browsers.
 :::
 
@@ -710,6 +716,7 @@ This setting will change the default maximum navigation time for the following m
 * [page.waitForNavigation()](/api/class-page.mdx#page-wait-for-navigation)
 
 :::note
+
 [page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) and [page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout) take priority over [browserContext.setDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout).
 :::
 
@@ -733,6 +740,7 @@ browserContext.setDefaultNavigationTimeout(timeout);
 This setting will change the default maximum time for all the methods accepting [timeout](/api/class-browsercontext.mdx#browser-context-set-default-timeout-option-timeout) option.
 
 :::note
+
 [page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout), [page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout) and [browserContext.setDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout) take priority over [browserContext.setDefaultTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout).
 :::
 
@@ -756,6 +764,7 @@ browserContext.setDefaultTimeout(timeout);
 The extra HTTP headers will be sent with every request initiated by any page in the context. These headers are merged with page-specific extra HTTP headers set with [page.setExtraHTTPHeaders()](/api/class-page.mdx#page-set-extra-http-headers). If page overrides a particular header, page-specific header value will be used instead of the browser context header value.
 
 :::note
+
 [browserContext.setExtraHTTPHeaders()](/api/class-browsercontext.mdx#browser-context-set-extra-http-headers) does not guarantee the order of headers in the outgoing requests.
 :::
 
@@ -1038,6 +1047,7 @@ browserContext.tracing
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.on('backgroundpage')</x-search>
 
 :::note
+
 Only works with Chromium browser's persistent context.
 :::
 
@@ -1182,6 +1192,7 @@ browserContext.on('request', data => {});
 Emitted when a request fails, for example by timing out. To only listen for failed requests from a particular page, use [page.on('requestfailed')](/api/class-page.mdx#page-event-request-failed).
 
 :::note
+
 HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with [browserContext.on('requestfinished')](/api/class-browsercontext.mdx#browser-context-event-request-finished) event and not with [browserContext.on('requestfailed')](/api/class-browsercontext.mdx#browser-context-event-request-failed).
 :::
 
@@ -1235,6 +1246,7 @@ browserContext.on('response', data => {});
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.on('serviceworker')</x-search>
 
 :::note
+
 Service workers are only supported on Chromium-based browsers.
 :::
 
diff --git a/nodejs/docs/api/class-browsertype.mdx b/nodejs/docs/api/class-browsertype.mdx
index ab21521fe5..55a11a7fb9 100644
--- a/nodejs/docs/api/class-browsertype.mdx
+++ b/nodejs/docs/api/class-browsertype.mdx
@@ -84,6 +84,7 @@ This method attaches Playwright to an existing browser instance using the Chrome
 The default browser context is accessible via [browser.contexts()](/api/class-browser.mdx#browser-contexts).
 
 :::note
+
 Connecting over the Chrome DevTools Protocol is only supported for Chromium-based browsers.
 :::
 
@@ -165,6 +166,7 @@ const browser = await chromium.launch({  // Or 'firefox' or 'webkit'.
   - `args` [Array]&lt;[string]&gt; *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-type-launch-option-args"/><a href="#browser-type-launch-option-args" class="list-anchor">#</a>
     
     :::warning
+    
     Use custom browser args at your own risk, as some of them may break Playwright functionality.
     :::
     
@@ -269,6 +271,7 @@ await browserType.launchPersistentContext(userDataDir, options);
   - `args` [Array]&lt;[string]&gt; *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-type-launch-persistent-context-option-args"/><a href="#browser-type-launch-persistent-context-option-args" class="list-anchor">#</a>
     
     :::warning
+    
     Use custom browser args at your own risk, as some of them may break Playwright functionality.
     :::
     
@@ -321,6 +324,7 @@ await browserType.launchPersistentContext(userDataDir, options);
     An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
     
     :::note
+    
     When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
     :::
     
@@ -532,6 +536,7 @@ await browserType.launchPersistentContext(userDataDir, options);
     Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `null` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation#viewport).
     
     :::note
+    
     The `null` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
     :::
     
@@ -568,6 +573,7 @@ const { chromium } = require('playwright');  // Or 'webkit' or 'firefox'.
   - `args` [Array]&lt;[string]&gt; *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-type-launch-server-option-args"/><a href="#browser-type-launch-server-option-args" class="list-anchor">#</a>
     
     :::warning
+    
     Use custom browser args at your own risk, as some of them may break Playwright functionality.
     :::
     
@@ -648,6 +654,7 @@ const { chromium } = require('playwright');  // Or 'webkit' or 'firefox'.
     Path at which to serve the Browser Server. For security, this defaults to an unguessable string.
     
     :::warning
+    
     Any process or web page (including those running in Playwright) with knowledge of the `wsPath` can take control of the OS user. For this reason, you should use an unguessable token when using this option.
     :::
     
diff --git a/nodejs/docs/api/class-coverage.mdx b/nodejs/docs/api/class-coverage.mdx
index 22f002eca3..c97f9d2b5b 100644
--- a/nodejs/docs/api/class-coverage.mdx
+++ b/nodejs/docs/api/class-coverage.mdx
@@ -12,6 +12,7 @@ Coverage gathers information about parts of JavaScript and CSS that were used by
 An example of using JavaScript coverage to produce Istanbul report for page load:
 
 :::note
+
 Coverage APIs are only supported on Chromium-based browsers.
 :::
 
@@ -71,6 +72,7 @@ await coverage.startCSSCoverage(options);
 Returns coverage is started
 
 :::note
+
 Anonymous scripts are ones that don't have an associated url. These are scripts that are dynamically created on the page using `eval` or `new Function`. If [reportAnonymousScripts](/api/class-coverage.mdx#coverage-start-js-coverage-option-report-anonymous-scripts) is set to `true`, anonymous scripts will have `__playwright_evaluation_script__` as their URL.
 :::
 
@@ -102,6 +104,7 @@ await coverage.startJSCoverage(options);
 Returns the array of coverage reports for all stylesheets
 
 :::note
+
 CSS Coverage doesn't include dynamically injected style tags without sourceURLs.
 :::
 
@@ -138,6 +141,7 @@ await coverage.stopCSSCoverage();
 Returns the array of coverage reports for all scripts
 
 :::note
+
 JavaScript Coverage doesn't include anonymous scripts by default. However, scripts with sourceURLs are reported.
 :::
 
diff --git a/nodejs/docs/api/class-elementhandle.mdx b/nodejs/docs/api/class-elementhandle.mdx
index 1c78882272..188c4e08c6 100644
--- a/nodejs/docs/api/class-elementhandle.mdx
+++ b/nodejs/docs/api/class-elementhandle.mdx
@@ -11,6 +11,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ElementHandle represents an in-page DOM element. ElementHandles can be created with the [page.$()](/api/class-page.mdx#page-query-selector) method.
 
 :::warning[Discouraged]
+
 The use of ElementHandle is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -461,6 +462,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [timeout](/api/class-elementhandle.mdx#element-handle-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `elementHandle.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -1358,6 +1360,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [timeout](/api/class-elementhandle.mdx#element-handle-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `elementHandle.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
diff --git a/nodejs/docs/api/class-frame.mdx b/nodejs/docs/api/class-frame.mdx
index 580378823c..51e1afc02e 100644
--- a/nodejs/docs/api/class-frame.mdx
+++ b/nodejs/docs/api/class-frame.mdx
@@ -489,6 +489,7 @@ await page.getByRole('button', { name: /submit/i }).click();
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
@@ -688,6 +689,7 @@ The method will throw an error if:
 The method will not throw an error when any valid HTTP status code is returned by the remote server, including 404 "Not Found" and 500 "Internal Server Error".  The status code for such responses can be retrieved by calling [response.status()](/api/class-response.mdx#response-status).
 
 :::note
+
 The method either throws an error or returns a main resource response. The only exceptions are navigation to `about:blank` or navigation to the same URL with a different hash, which would succeed and return `null`.
 :::
 
@@ -828,6 +830,7 @@ Returns frame's name attribute as specified in the tag.
 If the name is empty, returns the id attribute instead.
 
 :::note
+
 This value is calculated once when the frame is created, and will not update if the attribute is changed later.
 :::
 
@@ -1003,6 +1006,7 @@ Waits for the required load state to be reached.
 This returns when the frame reaches a required load state, `load` by default. The navigation must have been committed when this method is called. If current document has already reached the required state, resolves immediately.
 
 :::note
+
 Most of the time, this method is not needed because Playwright [auto-waits before every action](../actionability.mdx).
 :::
 
@@ -1080,6 +1084,7 @@ Use locator-based [frame.locator()](/api/class-frame.mdx#frame-locator) instead.
 Returns the ElementHandle pointing to the frame element.
 
 :::caution
+
 The use of [ElementHandle] is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -1120,6 +1125,7 @@ Use locator-based [frame.locator()](/api/class-frame.mdx#frame-locator) instead.
 Returns the ElementHandles pointing to the frame elements.
 
 :::caution
+
 The use of [ElementHandle] is discouraged, use [Locator] objects instead.
 :::
 
@@ -1390,6 +1396,7 @@ This method double clicks an element matching [selector](/api/class-frame.mdx#fr
 When all steps combined have not finished during the specified [timeout](/api/class-frame.mdx#frame-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `frame.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -2297,6 +2304,7 @@ This method taps an element matching [selector](/api/class-frame.mdx#frame-tap-o
 When all steps combined have not finished during the specified [timeout](/api/class-frame.mdx#frame-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `frame.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
@@ -2564,6 +2572,7 @@ Use web assertions that assert visibility or a locator-based [locator.waitFor()]
 Returns when element specified by selector satisfies [state](/api/class-frame.mdx#frame-wait-for-selector-option-state) option. Returns `null` if waiting for `hidden` or `detached`.
 
 :::note
+
 Playwright automatically waits for element to be ready before performing an action. Using [Locator] objects and web-first assertions make the code wait-for-selector-free.
 :::
 
diff --git a/nodejs/docs/api/class-framelocator.mdx b/nodejs/docs/api/class-framelocator.mdx
index c3e1ee1cb9..64020ce486 100644
--- a/nodejs/docs/api/class-framelocator.mdx
+++ b/nodejs/docs/api/class-framelocator.mdx
@@ -208,6 +208,7 @@ await page.getByRole('button', { name: /submit/i }).click();
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
diff --git a/nodejs/docs/api/class-jshandle.mdx b/nodejs/docs/api/class-jshandle.mdx
index 2839f893b2..018d40569a 100644
--- a/nodejs/docs/api/class-jshandle.mdx
+++ b/nodejs/docs/api/class-jshandle.mdx
@@ -171,6 +171,7 @@ await jsHandle.getProperty(propertyName);
 Returns a JSON representation of the object. If the object has a `toJSON` function, it **will not be called**.
 
 :::note
+
 The method will return an empty JSON object if the referenced object is not stringifiable. It will throw an error if the object has circular references.
 :::
 
diff --git a/nodejs/docs/api/class-keyboard.mdx b/nodejs/docs/api/class-keyboard.mdx
index 7464ceda2f..2e64ccb048 100644
--- a/nodejs/docs/api/class-keyboard.mdx
+++ b/nodejs/docs/api/class-keyboard.mdx
@@ -69,6 +69,7 @@ If [key](/api/class-keyboard.mdx#keyboard-down-option-key) is a modifier key, `S
 After the key is pressed once, subsequent calls to [keyboard.down()](/api/class-keyboard.mdx#keyboard-down) will have [repeat](https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/repeat) set to true. To release the key, use [keyboard.up()](/api/class-keyboard.mdx#keyboard-up).
 
 :::note
+
 Modifier keys DO influence `keyboard.down`. Holding down `Shift` will type the text in upper case.
 :::
 
@@ -119,6 +120,7 @@ Modifier keys DO NOT effect `keyboard.insertText`. Holding down `Shift` will not
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>keyboard.press</x-search>
 
 :::tip
+
 In most cases, you should use [locator.press()](/api/class-locator.mdx#locator-press) instead.
 :::
 
@@ -169,6 +171,7 @@ Shortcut for [keyboard.down()](/api/class-keyboard.mdx#keyboard-down) and [keybo
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>keyboard.type</x-search>
 
 :::caution
+
 In most cases, you should use [locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [locator.pressSequentially()](/api/class-locator.mdx#locator-press-sequentially).
 :::
 
diff --git a/nodejs/docs/api/class-locator.mdx b/nodejs/docs/api/class-locator.mdx
index 5d57b82f30..303104cd1f 100644
--- a/nodejs/docs/api/class-locator.mdx
+++ b/nodejs/docs/api/class-locator.mdx
@@ -23,7 +23,12 @@ Locators are the central piece of Playwright's auto-waiting and retry-ability. I
 When the locator points to a list of elements, this returns an array of locators, pointing to their respective elements.
 
 :::note
-[locator.all()](/api/class-locator.mdx#locator-all) does not wait for elements to match the locator, and instead immediately returns whatever is present in the page.  When the list of elements changes dynamically, [locator.all()](/api/class-locator.mdx#locator-all) will produce unpredictable and flaky results.  When the list of elements is stable, but loaded dynamically, wait for the full list to finish loading before calling [locator.all()](/api/class-locator.mdx#locator-all).
+
+[locator.all()](/api/class-locator.mdx#locator-all) does not wait for elements to match the locator, and instead immediately returns whatever is present in the page.
+
+When the list of elements changes dynamically, [locator.all()](/api/class-locator.mdx#locator-all) will produce unpredictable and flaky results.
+
+When the list of elements is stable, but loaded dynamically, wait for the full list to finish loading before calling [locator.all()](/api/class-locator.mdx#locator-all).
 :::
 
 **Usage**
@@ -45,6 +50,7 @@ for (const li of await page.getByRole('listitem').all())
 Returns an array of `node.innerText` values for all matching nodes.
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [expect(locator).toHaveText()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) with [useInnerText](/api/class-locatorassertions.mdx#locator-assertions-to-have-text-option-use-inner-text) option to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -66,6 +72,7 @@ const texts = await page.getByRole('link').allInnerTexts();
 Returns an array of `node.textContent` values for all matching nodes.
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [expect(locator).toHaveText()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -382,6 +389,7 @@ await frameLocator.getByRole('button').click();
 Returns the number of elements matching the locator.
 
 :::warning[Asserting count]
+
 If you need to assert the number of elements on the page, prefer [expect(locator).toHaveCount()](/api/class-locatorassertions.mdx#locator-assertions-to-have-count) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -461,6 +469,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [timeout](/api/class-locator.mdx#locator-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `element.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -862,6 +871,7 @@ await locator.click();
 Returns the matching element's attribute value.
 
 :::warning[Asserting attributes]
+
 If you need to assert an element's attribute, prefer [expect(locator).toHaveAttribute()](/api/class-locatorassertions.mdx#locator-assertions-to-have-attribute) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1033,6 +1043,7 @@ await page.getByRole('button', { name: /submit/i }).click();
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
@@ -1323,6 +1334,7 @@ await locator.innerHTML(options);
 Returns the [`element.innerText`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/innerText).
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [expect(locator).toHaveText()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) with [useInnerText](/api/class-locatorassertions.mdx#locator-assertions-to-have-text-option-use-inner-text) option to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1351,6 +1363,7 @@ await locator.innerText(options);
 Returns the value for the matching `<input>` or `<textarea>` or `<select>` element.
 
 :::warning[Asserting value]
+
 If you need to assert input value, prefer [expect(locator).toHaveValue()](/api/class-locatorassertions.mdx#locator-assertions-to-have-value) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1382,6 +1395,7 @@ Throws elements that are not an input, textarea or a select. However, if the ele
 Returns whether the element is checked. Throws if the element is not a checkbox or radio input.
 
 :::warning[Asserting checked state]
+
 If you need to assert that checkbox is checked, prefer [expect(locator).toBeChecked()](/api/class-locatorassertions.mdx#locator-assertions-to-be-checked) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1409,6 +1423,7 @@ const checked = await page.getByRole('checkbox').isChecked();
 Returns whether the element is disabled, the opposite of [enabled](../actionability.mdx#enabled).
 
 :::warning[Asserting disabled state]
+
 If you need to assert that an element is disabled, prefer [expect(locator).toBeDisabled()](/api/class-locatorassertions.mdx#locator-assertions-to-be-disabled) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1436,6 +1451,7 @@ const disabled = await page.getByRole('button').isDisabled();
 Returns whether the element is [editable](../actionability.mdx#editable).
 
 :::warning[Asserting editable state]
+
 If you need to assert that an element is editable, prefer [expect(locator).toBeEditable()](/api/class-locatorassertions.mdx#locator-assertions-to-be-editable) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1463,6 +1479,7 @@ const editable = await page.getByRole('textbox').isEditable();
 Returns whether the element is [enabled](../actionability.mdx#enabled).
 
 :::warning[Asserting enabled state]
+
 If you need to assert that an element is enabled, prefer [expect(locator).toBeEnabled()](/api/class-locatorassertions.mdx#locator-assertions-to-be-enabled) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1490,6 +1507,7 @@ const enabled = await page.getByRole('button').isEnabled();
 Returns whether the element is hidden, the opposite of [visible](../actionability.mdx#visible).
 
 :::warning[Asserting visibility]
+
 If you need to assert that element is hidden, prefer [expect(locator).toBeHidden()](/api/class-locatorassertions.mdx#locator-assertions-to-be-hidden) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1520,6 +1538,7 @@ const hidden = await page.getByRole('button').isHidden();
 Returns whether the element is [visible](../actionability.mdx#visible).
 
 :::warning[Asserting visibility]
+
 If you need to assert that element is visible, prefer [expect(locator).toBeVisible()](/api/class-locatorassertions.mdx#locator-assertions-to-be-visible) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1730,6 +1749,7 @@ Shortcuts such as `key: "Control+o"`, `key: "Control++` or `key: "Control+Shift+
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.38</font><x-search>locator.pressSequentially</x-search>
 
 :::tip
+
 In most cases, you should use [locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page.
 :::
 
@@ -2162,6 +2182,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [timeout](/api/class-locator.mdx#locator-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `element.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
@@ -2174,6 +2195,7 @@ When all steps combined have not finished during the specified [timeout](/api/cl
 Returns the [`node.textContent`](https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent).
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [expect(locator).toHaveText()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
diff --git a/nodejs/docs/api/class-mouse.mdx b/nodejs/docs/api/class-mouse.mdx
index 6cb28102fa..cc9ba655e7 100644
--- a/nodejs/docs/api/class-mouse.mdx
+++ b/nodejs/docs/api/class-mouse.mdx
@@ -187,6 +187,7 @@ await mouse.up(options);
 Dispatches a `wheel` event. This method is usually used to manually scroll the page. See [scrolling](../input.mdx#scrolling) for alternative ways to scroll.
 
 :::note
+
 Wheel events may cause scrolling if they are not handled, and this method does not wait for the scrolling to finish before returning.
 :::
 
diff --git a/nodejs/docs/api/class-page.mdx b/nodejs/docs/api/class-page.mdx
index e1dff54284..1a53eb6e73 100644
--- a/nodejs/docs/api/class-page.mdx
+++ b/nodejs/docs/api/class-page.mdx
@@ -117,7 +117,12 @@ Things to keep in mind:
 * You can register multiple handlers. However, only a single handler will be running at a time. Make sure the actions within a handler don't depend on another handler.
 
 :::warning
-Running the handler will alter your page state mid-test. For example it will change the currently focused element and move the mouse. Make sure that actions that run after the handler are self-contained and do not rely on the focus and mouse state being unchanged. <br /> <br /> For example, consider a test that calls [locator.focus()](/api/class-locator.mdx#locator-focus) followed by [keyboard.press()](/api/class-keyboard.mdx#keyboard-press). If your handler clicks a button between these two actions, the focused element most likely will be wrong, and key press will happen on the unexpected element. Use [locator.press()](/api/class-locator.mdx#locator-press) instead to avoid this problem. <br /> <br /> Another example is a series of mouse actions, where [mouse.move()](/api/class-mouse.mdx#mouse-move) is followed by [mouse.down()](/api/class-mouse.mdx#mouse-down). Again, when the handler runs between these two actions, the mouse position will be wrong during the mouse down. Prefer self-contained actions like [locator.click()](/api/class-locator.mdx#locator-click) that do not rely on the state being unchanged by a handler.
+
+Running the handler will alter your page state mid-test. For example it will change the currently focused element and move the mouse. Make sure that actions that run after the handler are self-contained and do not rely on the focus and mouse state being unchanged.
+
+For example, consider a test that calls [locator.focus()](/api/class-locator.mdx#locator-focus) followed by [keyboard.press()](/api/class-keyboard.mdx#keyboard-press). If your handler clicks a button between these two actions, the focused element most likely will be wrong, and key press will happen on the unexpected element. Use [locator.press()](/api/class-locator.mdx#locator-press) instead to avoid this problem.
+
+Another example is a series of mouse actions, where [mouse.move()](/api/class-mouse.mdx#mouse-move) is followed by [mouse.down()](/api/class-mouse.mdx#mouse-down). Again, when the handler runs between these two actions, the mouse position will be wrong during the mouse down. Prefer self-contained actions like [locator.click()](/api/class-locator.mdx#locator-click) that do not rely on the state being unchanged by a handler.
 :::
 
 **Usage**
@@ -278,6 +283,7 @@ If [runBeforeUnload](/api/class-page.mdx#page-close-option-run-before-unload) is
 By default, `page.close()` **does not** run `beforeunload` handlers.
 
 :::note
+
 if [runBeforeUnload](/api/class-page.mdx#page-close-option-run-before-unload) is passed as true, a `beforeunload` dialog might be summoned and should be handled manually via [page.on('dialog')](/api/class-page.mdx#page-event-dialog) event.
 :::
 
@@ -568,6 +574,7 @@ The first argument of the [callback](/api/class-page.mdx#page-expose-binding-opt
 See [browserContext.exposeBinding()](/api/class-browsercontext.mdx#browser-context-expose-binding) for the context-wide version.
 
 :::note
+
 Functions installed via [page.exposeBinding()](/api/class-page.mdx#page-expose-binding) survive navigations.
 :::
 
@@ -629,6 +636,7 @@ If the [callback](/api/class-page.mdx#page-expose-function-option-callback) retu
 See [browserContext.exposeFunction()](/api/class-browsercontext.mdx#browser-context-expose-function) for context-wide exposed function.
 
 :::note
+
 Functions installed via [page.exposeFunction()](/api/class-page.mdx#page-expose-function) survive navigations.
 :::
 
@@ -672,23 +680,6 @@ const crypto = require('crypto');
 
 ---
 
-### forceGarbageCollection {#page-force-garbage-collection}
-
-<font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.47</font><x-search>page.forceGarbageCollection</x-search>
-
-Force the browser to perform garbage collection.
-
-**Usage**
-
-```js
-await page.forceGarbageCollection();
-```
-
-**Returns**
-- [Promise]&lt;[void]&gt;<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="page-force-garbage-collection-return"/><a href="#page-force-garbage-collection-return" class="list-anchor">#</a>
-
----
-
 ### frame {#page-frame}
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.frame</x-search>
@@ -910,6 +901,7 @@ await page.getByRole('button', { name: /submit/i }).click();
     An attribute that is usually set by `aria-disabled` or `disabled`.
     
     :::note
+    
     Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
     :::
     
@@ -1175,6 +1167,7 @@ The method will throw an error if:
 The method will not throw an error when any valid HTTP status code is returned by the remote server, including 404 "Not Found" and 500 "Internal Server Error".  The status code for such responses can be retrieved by calling [response.status()](/api/class-response.mdx#response-status).
 
 :::note
+
 The method either throws an error or returns a main resource response. The only exceptions are navigation to `about:blank` or navigation to the same URL with a different hash, which would succeed and return `null`.
 :::
 
@@ -1317,6 +1310,7 @@ Pauses script execution. Playwright will stop executing the script and wait for
 User can inspect selectors or perform manual steps while paused. Resume will continue running the original script from the place it was paused.
 
 :::note
+
 This method requires Playwright to be started in a headed mode, with a falsy [headless](/api/class-browsertype.mdx#browser-type-launch-option-headless) option.
 :::
 
@@ -1338,12 +1332,14 @@ await page.pause();
 Returns the PDF buffer.
 
 :::note
+
 Generating a pdf is currently only supported in Chromium headless.
 :::
 
 `page.pdf()` generates a pdf of the page with `print` css media. To generate a pdf with `screen` media, call [page.emulateMedia()](/api/class-page.mdx#page-emulate-media) before calling `page.pdf()`:
 
 :::note
+
 By default, `page.pdf()` generates a pdf with modified colors for printing. Use the [`-webkit-print-color-adjust`](https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-print-color-adjust) property to force rendering of exact colors.
 :::
 
@@ -1382,6 +1378,7 @@ The [format](/api/class-page.mdx#page-pdf-option-format) options are:
 * `A6`: 4.13in x 5.83in
 
 :::note
+
 [headerTemplate](/api/class-page.mdx#page-pdf-option-header-template) and [footerTemplate](/api/class-page.mdx#page-pdf-option-footer-template) markup have the following limitations: > 1. Script tags inside templates are not evaluated. > 2. Page styles are not visible inside templates.
 :::
 
@@ -1542,6 +1539,34 @@ await page.removeLocatorHandler(locator);
 
 ---
 
+### requestGC {#page-request-gc}
+
+<font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.48</font><x-search>page.requestGC</x-search>
+
+Request the page to perform garbage collection. Note that there is no guarantee that all unreachable objects will be collected.
+
+This is useful to help detect memory leaks. For example, if your page has a large object `'suspect'` that might be leaked, you can check that it does not leak by using a [`WeakRef`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakRef).
+
+```js
+// 1. In your page, save a WeakRef for the "suspect".
+await page.evaluate(() => globalThis.suspectWeakRef = new WeakRef(suspect));
+// 2. Request garbage collection.
+await page.requestGC();
+// 3. Check that weak ref does not deref to the original object.
+expect(await page.evaluate(() => !globalThis.suspectWeakRef.deref())).toBe(true);
+```
+
+**Usage**
+
+```js
+await page.requestGC();
+```
+
+**Returns**
+- [Promise]&lt;[void]&gt;<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="page-request-gc-return"/><a href="#page-request-gc-return" class="list-anchor">#</a>
+
+---
+
 ### route {#page-route}
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.route</x-search>
@@ -1551,6 +1576,7 @@ Routing provides the capability to modify network requests that are made by a pa
 Once routing is enabled, every request matching the url pattern will stall unless it's continued, fulfilled or aborted.
 
 :::note
+
 The handler will only be called for the first url if the response is a redirect.
 :::
 
@@ -1598,6 +1624,7 @@ Page routes take precedence over browser context routes (set up with [browserCon
 To remove a route with its handler you can use [page.unroute()](/api/class-page.mdx#page-unroute).
 
 :::note
+
 Enabling routing disables http cache.
 :::
 
@@ -1823,6 +1850,7 @@ This setting will change the default maximum navigation time for the following m
 * [page.waitForURL()](/api/class-page.mdx#page-wait-for-url)
 
 :::note
+
 [page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) takes priority over [page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout), [browserContext.setDefaultTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout) and [browserContext.setDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout).
 :::
 
@@ -1846,6 +1874,7 @@ page.setDefaultNavigationTimeout(timeout);
 This setting will change the default maximum time for all the methods accepting [timeout](/api/class-page.mdx#page-set-default-timeout-option-timeout) option.
 
 :::note
+
 [page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) takes priority over [page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout).
 :::
 
@@ -1869,6 +1898,7 @@ page.setDefaultTimeout(timeout);
 The extra HTTP headers will be sent with every request the page initiates.
 
 :::note
+
 [page.setExtraHTTPHeaders()](/api/class-page.mdx#page-set-extra-http-headers) does not guarantee the order of headers in the outgoing requests.
 :::
 
@@ -2141,6 +2171,7 @@ Returns when the required load state has been reached.
 This resolves when the page reaches a required load state, `load` by default. The navigation must have been committed when this method is called. If current document has already reached the required state, resolves immediately.
 
 :::note
+
 Most of the time, this method is not needed because Playwright [auto-waits before every action](../actionability.mdx).
 :::
 
@@ -2290,6 +2321,7 @@ await page.waitForURL('**/target.html');
 This method returns all of the dedicated [WebWorkers](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API) associated with the page.
 
 :::note
+
 This does not contain ServiceWorkers
 :::
 
@@ -2328,6 +2360,7 @@ page.clock
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.coverage</x-search>
 
 :::note
+
 Only available for Chromium atm.
 :::
 
@@ -3130,6 +3163,7 @@ This method double clicks an element matching [selector](/api/class-page.mdx#pag
 When all steps combined have not finished during the specified [timeout](/api/class-page.mdx#page-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `page.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -4084,6 +4118,7 @@ This method taps an element matching [selector](/api/class-page.mdx#page-tap-opt
 When all steps combined have not finished during the specified [timeout](/api/class-page.mdx#page-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 [page.tap()](/api/class-page.mdx#page-tap) the method will throw if [hasTouch](/api/class-browser.mdx#browser-new-context-option-has-touch) option of the browser context is false.
 :::
 
@@ -4351,6 +4386,7 @@ Use web assertions that assert visibility or a locator-based [locator.waitFor()]
 Returns when element specified by selector satisfies [state](/api/class-page.mdx#page-wait-for-selector-option-state) option. Returns `null` if waiting for `hidden` or `detached`.
 
 :::note
+
 Playwright automatically waits for element to be ready before performing an action. Using [Locator] objects and web-first assertions makes the code wait-for-selector-free.
 :::
 
diff --git a/nodejs/docs/api/class-request.mdx b/nodejs/docs/api/class-request.mdx
index 5a54100566..edc5babf8c 100644
--- a/nodejs/docs/api/class-request.mdx
+++ b/nodejs/docs/api/class-request.mdx
@@ -15,6 +15,7 @@ Whenever the page sends a request for a network resource the following sequence
 If request fails at some point, then instead of `'requestfinished'` event (and possibly instead of 'response' event), the  [page.on('requestfailed')](/api/class-page.mdx#page-event-request-failed) event is emitted.
 
 :::note
+
 HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with `'requestfinished'` event.
 :::
 
diff --git a/nodejs/docs/api/class-snapshotassertions.mdx b/nodejs/docs/api/class-snapshotassertions.mdx
index a93fb7a3a1..04b7455a91 100644
--- a/nodejs/docs/api/class-snapshotassertions.mdx
+++ b/nodejs/docs/api/class-snapshotassertions.mdx
@@ -23,6 +23,7 @@ expect(screenshot).toMatchSnapshot('landing-page.png');
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.22</font><x-search>snapshotAssertions.toMatchSnapshot(name)</x-search>
 
 :::caution
+
 To compare screenshots, use [expect(page).toHaveScreenshot()](/api/class-pageassertions.mdx#page-assertions-to-have-screenshot-1) instead.
 :::
 
@@ -73,6 +74,7 @@ Note that matching snapshots only work with Playwright test runner.
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.22</font><x-search>snapshotAssertions.toMatchSnapshot()</x-search>
 
 :::caution
+
 To compare screenshots, use [expect(page).toHaveScreenshot()](/api/class-pageassertions.mdx#page-assertions-to-have-screenshot-2) instead.
 :::
 
diff --git a/nodejs/docs/api/class-test.mdx b/nodejs/docs/api/class-test.mdx
index 91c3b56312..230dc164b8 100644
--- a/nodejs/docs/api/class-test.mdx
+++ b/nodejs/docs/api/class-test.mdx
@@ -463,6 +463,7 @@ Learn more about the execution modes [here](../test-parallel.mdx).
 * Running tests serially, retrying from the start.
   
   :::note
+  
   Running serially is not recommended. It is usually better to make your tests isolated, so they can be run independently.
   :::
   
@@ -1655,6 +1656,7 @@ See [test.describe.configure()](/api/class-test.mdx#test-describe-configure) for
 Declares a group of tests that should always be run serially. If one of the tests fails, all subsequent tests are skipped. All tests in a group are retried together.
 
 :::note
+
 Using serial is not recommended. It is usually better to make your tests isolated, so they can be run independently.
 :::
 
@@ -1716,6 +1718,7 @@ See [test.describe.configure()](/api/class-test.mdx#test-describe-configure) for
 Declares a focused group of tests that should always be run serially. If one of the tests fails, all subsequent tests are skipped. All tests in a group are retried together. If there are some focused tests or suites, all of them will be run but nothing else.
 
 :::note
+
 Using serial is not recommended. It is usually better to make your tests isolated, so they can be run independently.
 :::
 
diff --git a/nodejs/docs/api/class-testconfig.mdx b/nodejs/docs/api/class-testconfig.mdx
index ff1d6f5a34..ab88e26cde 100644
--- a/nodejs/docs/api/class-testconfig.mdx
+++ b/nodejs/docs/api/class-testconfig.mdx
@@ -959,6 +959,7 @@ For continuous integration, you may want to use the `reuseExistingServer: !proce
 The `port` (but not the `url`) gets passed over to Playwright as a [testOptions.baseURL](/api/class-testoptions.mdx#test-options-base-url). For example port `8080` produces `baseURL` equal `http://localhost:8080`. If `webServer` is specified as an array, you must explicitly configure the `baseURL` (even if it only has one entry).
 
 :::note
+
 It is also recommended to specify [testOptions.baseURL](/api/class-testoptions.mdx#test-options-base-url) in the config, so that tests could use relative urls.
 :::
 
diff --git a/nodejs/docs/api/class-testinfo.mdx b/nodejs/docs/api/class-testinfo.mdx
index 5a89a82fce..e9b4835f85 100644
--- a/nodejs/docs/api/class-testinfo.mdx
+++ b/nodejs/docs/api/class-testinfo.mdx
@@ -674,6 +674,7 @@ testInfo.snapshotDir
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.10</font><x-search>testInfo.snapshotSuffix</x-search>
 
 :::note
+
 Use of [testInfo.snapshotSuffix](/api/class-testinfo.mdx#test-info-snapshot-suffix) is discouraged. Please use [testConfig.snapshotPathTemplate](/api/class-testconfig.mdx#test-config-snapshot-path-template) to configure snapshot paths.
 :::
 
diff --git a/nodejs/docs/api/class-testoptions.mdx b/nodejs/docs/api/class-testoptions.mdx
index 0aabe9c78a..fe6b5b1ccc 100644
--- a/nodejs/docs/api/class-testoptions.mdx
+++ b/nodejs/docs/api/class-testoptions.mdx
@@ -249,6 +249,7 @@ export default defineConfig({
 An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
 
 :::note
+
 When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
 :::
 
@@ -580,6 +581,7 @@ export default defineConfig({
 Options used to launch the browser, as passed to [browserType.launch()](/api/class-browsertype.mdx#browser-type-launch). Specific options [testOptions.headless](/api/class-testoptions.mdx#test-options-headless) and [testOptions.channel](/api/class-testoptions.mdx#test-options-channel) take priority over this.
 
 :::warning
+
 Use custom browser args at your own risk, as some of them may break Playwright functionality.
 :::
 
@@ -1047,6 +1049,7 @@ Learn more about [recording video](../test-use-options.mdx#recording-options).
 Emulates consistent viewport for each page. Defaults to an 1280x720 viewport. Use `null` to disable the consistent viewport emulation. Learn more about [viewport emulation](../emulation#viewport).
 
 :::note
+
 The `null` value opts out from the default presets, makes viewport depend on the host window size defined by the operating system. It makes the execution of the tests non-deterministic.
 :::
 
diff --git a/nodejs/docs/api/class-touchscreen.mdx b/nodejs/docs/api/class-touchscreen.mdx
index d1d00f1912..a2529e4a73 100644
--- a/nodejs/docs/api/class-touchscreen.mdx
+++ b/nodejs/docs/api/class-touchscreen.mdx
@@ -21,6 +21,7 @@ The Touchscreen class operates in main-frame CSS pixels relative to the top-left
 Dispatches a `touchstart` and `touchend` event with a single touch at the position ([x](/api/class-touchscreen.mdx#touchscreen-tap-option-x),[y](/api/class-touchscreen.mdx#touchscreen-tap-option-y)).
 
 :::note
+
 [page.tap()](/api/class-page.mdx#page-tap) the method will throw if [hasTouch](/api/class-browser.mdx#browser-new-context-option-has-touch) option of the browser context is false.
 :::
 
diff --git a/nodejs/docs/browsers.mdx b/nodejs/docs/browsers.mdx
index 7122e9647d..a86961f1a9 100644
--- a/nodejs/docs/browsers.mdx
+++ b/nodejs/docs/browsers.mdx
@@ -166,6 +166,7 @@ While Playwright can download and use the recent Chromium build, it can operate
 Available channels are `chrome`, `msedge`, `chrome-beta`, `msedge-beta` or `msedge-dev`.
 
 :::warning
+
 Certain Enterprise Browser Policies may impact Playwright's ability to launch and control Google Chrome and Microsoft Edge. Running in an environment with browser policies is outside of the Playwright project's scope.
 :::
 
@@ -516,6 +517,7 @@ npx playwright test
 Playwright keeps track of packages that need those browsers and will garbage collect them as you update Playwright to the newer versions.
 
 :::note
+
 Developers can opt-in in this mode via exporting `PLAYWRIGHT_BROWSERS_PATH=$HOME/pw-browsers` in their `.bashrc`.
 :::
 
@@ -561,6 +563,7 @@ npx playwright install
 </Tabs>
 
 :::note
+
 `PLAYWRIGHT_BROWSERS_PATH` does not change installation path for Google Chrome and Microsoft Edge.
 :::
 
diff --git a/nodejs/docs/canary-releases.mdx b/nodejs/docs/canary-releases.mdx
index 4e7710e0da..d231bd640b 100644
--- a/nodejs/docs/canary-releases.mdx
+++ b/nodejs/docs/canary-releases.mdx
@@ -15,7 +15,10 @@ It permits you to **test new unreleased features** instead of waiting for a full
 It is a good way to **give feedback to maintainers**, ensuring the newly implemented feature works as intended.
 
 :::note
- Using a canary release in production might seem risky, but in practice, it's not.  A canary release passes all automated tests and is used to test e.g. the HTML report, Trace Viewer, or Playwright Inspector with end-to-end tests. 
+
+Using a canary release in production might seem risky, but in practice, it's not.
+
+A canary release passes all automated tests and is used to test e.g. the HTML report, Trace Viewer, or Playwright Inspector with end-to-end tests.
 :::
 
 ```txt
diff --git a/nodejs/docs/chrome-extensions.mdx b/nodejs/docs/chrome-extensions.mdx
index 96e4e0638f..d4e57ea7bf 100644
--- a/nodejs/docs/chrome-extensions.mdx
+++ b/nodejs/docs/chrome-extensions.mdx
@@ -9,6 +9,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ## Introduction
 
 :::note
+
 Extensions only work in Chrome / Chromium launched with a persistent context. Use custom browser args at your own risk, as some of them may break Playwright functionality.
 :::
 
@@ -101,6 +102,7 @@ test('popup page', async ({ page, extensionId }) => {
 ## Headless mode
 
 :::danger
+
 `headless=new` mode is not officially supported by Playwright and might result in unexpected behavior.
 :::
 
diff --git a/nodejs/docs/ci-intro.mdx b/nodejs/docs/ci-intro.mdx
index 509eeada1f..e0bbdf25fa 100644
--- a/nodejs/docs/ci-intro.mdx
+++ b/nodejs/docs/ci-intro.mdx
@@ -142,6 +142,7 @@ Downloading the HTML report as a zip file is not very convenient. However, we ca
 The contents of the `$web` storage container can be accessed from a browser by using the [public URL](https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-static-website-how-to?tabs=azure-portal#portal-find-url) of the website.
 
 :::note
+
 This step will not work for pull requests created from a forked repository because such workflow [doesn't have access to the secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow).
 :::
 
diff --git a/nodejs/docs/clock.mdx b/nodejs/docs/clock.mdx
index a4d467d905..d3fd8a715e 100644
--- a/nodejs/docs/clock.mdx
+++ b/nodejs/docs/clock.mdx
@@ -24,7 +24,19 @@ The [Clock] API provides the following methods to control time:
 The recommended approach is to use `setFixedTime` to set the time to a specific value. If that doesn't work for your use case, you can use `install` which allows you to pause time later on, fast forward it, tick it, etc. `setSystemTime` is only recommended for advanced use cases.
 
 :::note
-[page.clock](/api/class-page.mdx#page-clock) overrides native global classes and functions related to time allowing them to be manually controlled:   - `Date`   - `setTimeout`   - `clearTimeout`   - `setInterval`   - `clearInterval`   - `requestAnimationFrame`   - `cancelAnimationFrame`   - `requestIdleCallback`   - `cancelIdleCallback`   - `performance`   - `Event.timeStamp`
+
+[page.clock](/api/class-page.mdx#page-clock) overrides native global classes and functions related to time allowing them to be manually controlled:
+- `Date`
+- `setTimeout`
+- `clearTimeout`
+- `setInterval`
+- `clearInterval`
+- `requestAnimationFrame`
+- `cancelAnimationFrame`
+- `requestIdleCallback`
+- `cancelIdleCallback`
+- `performance`
+- `Event.timeStamp`
 :::
 
 ## Test with predefined time
diff --git a/nodejs/docs/debug.mdx b/nodejs/docs/debug.mdx
index c13535a5bc..cc3c13cd3e 100644
--- a/nodejs/docs/debug.mdx
+++ b/nodejs/docs/debug.mdx
@@ -298,6 +298,7 @@ npx playwright test
 </Tabs>
 
 :::note
+
 **For WebKit**: launching WebKit Inspector during the execution will prevent the Playwright script from executing any further and will reset pre-configured user agent and device emulation.
 :::
 
diff --git a/nodejs/docs/dialogs.mdx b/nodejs/docs/dialogs.mdx
index d09bb22c3c..bfd5089bfc 100644
--- a/nodejs/docs/dialogs.mdx
+++ b/nodejs/docs/dialogs.mdx
@@ -26,6 +26,7 @@ await page.getByRole('button').click();
 As a result, the following snippet will never resolve:
 
 :::warning
+
 WRONG!
 :::
 
diff --git a/nodejs/docs/docker.mdx b/nodejs/docs/docker.mdx
index abf8164eab..359fc7b328 100644
--- a/nodejs/docs/docker.mdx
+++ b/nodejs/docs/docker.mdx
@@ -15,6 +15,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 This Docker image is published to [Microsoft Artifact Registry].
 
 :::info
+
 This Docker image is intended to be used for testing and development purposes only. It is not recommended to use this Docker image to visit untrusted websites.
 :::
 
@@ -80,6 +81,7 @@ We currently publish images with the following tags:
 - `:v1.47.2-focal` - Playwright v1.47.2 release docker image based on Ubuntu 20.04 LTS (Focal Fossa).
 
 :::note
+
 It is recommended to always pin your Docker image to a specific version if possible. If the Playwright version in your Docker image does not match the version in your project/tests, Playwright will be unable to locate browser executables.
 :::
 
diff --git a/nodejs/docs/downloads.mdx b/nodejs/docs/downloads.mdx
index 37085d7213..6cdac65886 100644
--- a/nodejs/docs/downloads.mdx
+++ b/nodejs/docs/downloads.mdx
@@ -13,6 +13,7 @@ For every attachment downloaded by the page, [page.on('download')](/api/class-pa
 You can specify where to persist downloaded files using the [downloadsPath](/api/class-browsertype.mdx#browser-type-launch-option-downloads-path) option in [browserType.launch()](/api/class-browsertype.mdx#browser-type-launch).
 
 :::note
+
 Downloaded files are deleted when the browser context that produced them is closed.
 :::
 
@@ -39,6 +40,7 @@ page.on('download', download => download.path().then(console.log));
 Note that handling the event forks the control flow and makes the script harder to follow. Your scenario might end while you are downloading a file since your main control flow is not awaiting for this operation to resolve.
 
 :::note
+
 For uploading files, see the [uploading files](./input.mdx#upload-files) section.
 :::
 
diff --git a/nodejs/docs/handles.mdx b/nodejs/docs/handles.mdx
index fe5f3f3761..81acf931c5 100644
--- a/nodejs/docs/handles.mdx
+++ b/nodejs/docs/handles.mdx
@@ -30,6 +30,7 @@ const jsHandle = await page.evaluateHandle('window');
 ## Element Handles
 
 :::warning[Discouraged]
+
 The use of [ElementHandle] is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -92,6 +93,7 @@ Handles can be acquired using the page methods such as [page.evaluateHandle()](/
 ## Locator vs ElementHandle
 
 :::caution
+
 We only recommend using [ElementHandle] in the rare cases when you need to perform extensive DOM traversal on a static page. For all user actions and assertions use locator instead.
 :::
 
diff --git a/nodejs/docs/input.mdx b/nodejs/docs/input.mdx
index 4afe476685..c879cc48ee 100644
--- a/nodejs/docs/input.mdx
+++ b/nodejs/docs/input.mdx
@@ -113,6 +113,7 @@ await page.getByRole('button').dispatchEvent('click');
 ## Type characters
 
 :::caution
+
 Most of the time, you should input text with [locator.fill()](/api/class-locator.mdx#locator-fill). See the [Text input](#text-input) section above. You only need to type characters if there is special keyboard handling on the page.
 :::
 
diff --git a/nodejs/docs/locators.mdx b/nodejs/docs/locators.mdx
index 551c0a6d83..b89750155f 100644
--- a/nodejs/docs/locators.mdx
+++ b/nodejs/docs/locators.mdx
@@ -117,6 +117,7 @@ Role locators include [buttons, checkboxes, headings, links, lists, tables, and
 Note that role locators **do not replace** accessibility audits and conformance tests, but rather give early feedback about the ARIA guidelines.
 
 :::note[When to use role locators]
+
 We recommend prioritizing role locators to locate elements, as it is the closest way to how users and assistive technology perceive the page.
 :::
 
@@ -587,6 +588,7 @@ If you'd like to target one of the two or more elements, and you don't know whic
 For example, consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead. In this case, you can wait for either a "New email" button, or a dialog and act accordingly.
 
 :::note
+
 If both "New email" button and security dialog appear on screen, the "or" locator will match both of them, possibly throwing the ["strict mode violation" error](#strictness). In this case, you can use [locator.first()](/api/class-locator.mdx#locator-first) to only match one of them.
 :::
 
@@ -602,6 +604,7 @@ await newEmail.click();
 ### Matching only visible elements
 
 :::note
+
 It's usually better to find a [more reliable way](./locators.mdx#quick-guide) to uniquely identify the element instead of checking the visibility.
 :::
 
diff --git a/nodejs/docs/navigations.mdx b/nodejs/docs/navigations.mdx
index f477112d98..4b55f05bd1 100644
--- a/nodejs/docs/navigations.mdx
+++ b/nodejs/docs/navigations.mdx
@@ -22,6 +22,7 @@ await page.goto('https://example.com');
 The code above loads the page and waits for the web page to fire the [load](https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event) event. The load event is fired when the whole page has loaded, including all dependent resources such as stylesheets, scripts, iframes, and images.
 
 :::note
+
 If the page does a client-side redirect before `load`, [page.goto()](/api/class-page.mdx#page-goto) will wait for the redirected page to fire the `load` event.
 :::
 
diff --git a/nodejs/docs/other-locators.mdx b/nodejs/docs/other-locators.mdx
index 88e36f6b0d..6d02d9d5d1 100644
--- a/nodejs/docs/other-locators.mdx
+++ b/nodejs/docs/other-locators.mdx
@@ -9,6 +9,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ## Introduction
 
 :::note
+
 Check out the main [locators guide](./locators) for most common and recommended locators.
 :::
 
@@ -17,6 +18,7 @@ In addition to recommended locators like [page.getByRole()](/api/class-page.mdx#
 ## CSS locator
 
 :::note
+
 We recommend prioritizing [user-visible locators](./locators.mdx#quick-guide) like text or accessible role instead of using CSS that is tied to the implementation and could break when the page changes.
 :::
 
@@ -64,6 +66,7 @@ Playwright include a number of CSS pseudo-classes to match elements by their tex
   For example, `:text-matches("Log\s*in", "i")` matches `<button>Login</button>` and `<button>log IN</button>`.
 
 :::note
+
 Text matching always normalizes whitespace. For example, it turns multiple spaces into one, turns line breaks into spaces and ignores leading and trailing whitespace.
 :::
 
@@ -118,6 +121,7 @@ The `:is()` pseudo-class is an [experimental CSS pseudo-class](https://developer
 ### CSS: matching elements based on layout
 
 :::note
+
 Matching based on layout may produce unexpected results. For example, a different element could be matched when layout changes by one pixel.
 :::
 
@@ -152,6 +156,7 @@ All layout pseudo-classes support optional maximum pixel distance as the last ar
 ### CSS: pick n-th match from the query result
 
 :::note
+
 It is usually possible to distinguish elements by some attribute or text content, which is more resilient to page changes.
 :::
 
@@ -218,6 +223,7 @@ const parent = page.getByText('Hello').locator('xpath=..');
 ## React locator
 
 :::note
+
 React locator is experimental and prefixed with `_`. The functionality might change in future.
 :::
 
@@ -246,6 +252,7 @@ More examples:
 To find React element names in a tree use [React DevTools](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi).
 
 :::note
+
 React locator supports React 15 and above.
 :::
 
@@ -256,6 +263,7 @@ React locator, as well as [React DevTools](https://chrome.google.com/webstore/de
 ## Vue locator
 
 :::note
+
 Vue locator is experimental and prefixed with `_`. The functionality might change in future.
 :::
 
@@ -283,6 +291,7 @@ More examples:
 To find Vue element names in a tree use [Vue DevTools](https://chrome.google.com/webstore/detail/vuejs-devtools/nhdogjmejiglipccpnnnanhbledajbpd?hl=en).
 
 :::note
+
 Vue locator supports Vue2 and above.
 :::
 
@@ -293,6 +302,7 @@ Vue locator, as well as [Vue DevTools](https://chrome.google.com/webstore/detail
 ## XPath locator
 
 :::warning
+
 We recommend prioritizing [user-visible locators](./locators.mdx#quick-guide) like text or accessible role instead of using XPath that is tied to the implementation and easily break when the page changes.
 :::
 
@@ -324,6 +334,7 @@ await page.locator(
 ## Label to form control retargeting
 
 :::warning
+
 We recommend [locating by label text](./locators.mdx#locate-by-label) instead of relying to label-to-control retargeting.
 :::
 
@@ -352,6 +363,7 @@ await expect(page.locator('label')).toHaveText('Password');
 ## Legacy text locator
 
 :::warning
+
 We recommend the modern [text locator](./locators.mdx#get-by-text) instead.
 :::
 
@@ -385,6 +397,7 @@ Legacy text locator has a few variations:
   ```
   
 :::note
+
 String selectors starting and ending with a quote (either `"` or `'`) are assumed to be a legacy text locators. For example, `"Log in"` is converted to `text="Log in"` internally.
 :::
 
@@ -399,6 +412,7 @@ Input elements of the type `button` and `submit` are matched by their `value` in
 ## id, data-testid, data-test-id, data-test selectors
 
 :::warning
+
 We recommend [locating by test id](./locators.mdx#locate-by-test-id) instead.
 :::
 
@@ -423,6 +437,7 @@ Attribute selectors are not CSS selectors, so anything CSS-specific like `:enabl
 ## Chaining selectors
 
 :::warning
+
 We recommend [chaining locators](./locators.mdx#matching-inside-a-locator) instead.
 :::
 
@@ -448,6 +463,7 @@ If a selector needs to include `>>` in the body, it should be escaped inside a s
 ### Intermediate matches
 
 :::warning
+
 We recommend [filtering by another locator](./locators.mdx#filter-by-childdescendant) to locate elements that contain other elements.
 :::
 
diff --git a/nodejs/docs/selenium-grid.mdx b/nodejs/docs/selenium-grid.mdx
index e3f5db7981..51d446f5a6 100644
--- a/nodejs/docs/selenium-grid.mdx
+++ b/nodejs/docs/selenium-grid.mdx
@@ -11,7 +11,20 @@ import HTMLCard from '@site/src/components/HTMLCard';
 Playwright can connect to [Selenium Grid Hub](https://www.selenium.dev/documentation/grid/) that runs Selenium 4 to launch **Google Chrome** or **Microsoft Edge** browser, instead of running browser on the local machine. Note this feature is **experimental** and is prioritized accordingly.
 
 :::warning
-There is a risk of Playwright integration with Selenium Grid Hub breaking in the future. Make sure you weight risks against benefits before using it.  <br /> <br /> <details> <summary> <span style={{textTransform:'uppercase',fontSize:'smaller',fontWeight:'bold',opacity:'0.6'}}>More details</span> </summary>  Internally, Playwright connects to the browser using [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) websocket. Selenium 4 currently exposes this capability. However, this [might not be the case in the future](https://github.com/SeleniumHQ/selenium/issues/11590#issuecomment-1436113950). If Selenium drops this capability, Playwright will stop working with it. </details>
+
+There is a risk of Playwright integration with Selenium Grid Hub breaking in the future. Make sure you weight risks against benefits before using it.
+
+<details>
+
+<summary>
+
+<span style={{textTransform:'uppercase',fontSize:'smaller',fontWeight:'bold',opacity:'0.6'}}>More details</span>
+
+</summary>
+
+Internally, Playwright connects to the browser using [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) websocket. Selenium 4 currently exposes this capability. However, this [might not be the case in the future](https://github.com/SeleniumHQ/selenium/issues/11590#issuecomment-1436113950). If Selenium drops this capability, Playwright will stop working with it.
+
+</details>
 :::
 
 Before connecting Playwright to your Selenium Grid, make sure that grid works with [Selenium WebDriver](https://www.selenium.dev/documentation/webdriver/). For example, run [one of the examples](https://github.com/SeleniumHQ/selenium/tree/trunk/javascript/node/selenium-webdriver/example) and pass `SELENIUM_REMOTE_URL` environment variable. If webdriver example does not work, look for any errors at your Selenium hub/node/standalone output and search [Selenium issues](https://github.com/SeleniumHQ/selenium/issues) for a possible solution.
diff --git a/nodejs/docs/service-workers-experimental-network-events.mdx b/nodejs/docs/service-workers-experimental-network-events.mdx
index 79a579105d..774e04866a 100644
--- a/nodejs/docs/service-workers-experimental-network-events.mdx
+++ b/nodejs/docs/service-workers-experimental-network-events.mdx
@@ -9,6 +9,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ## Introduction
 
 :::warning
+
 If you're looking to do general network mocking, routing, and interception, please see the [Network Guide](./network.mdx) first. Playwright provides built-in APIs for this use case that don't require the information below. However, if you're interested in requests made by Service Workers themselves, please read below.
 :::
 
@@ -108,6 +109,7 @@ Since the example Service Worker just acts a basic transparent "proxy":
 * Only the Service [Worker]-owned request for the resource was routable via [browserContext.route()](/api/class-browsercontext.mdx#browser-context-route); the [Frame]-owned events for `data.json` are not routeable, as they would not have even had the possibility to hit the external network since the Service Worker has a fetch handler registered.
 
 :::caution
+
 It's important to note: calling [request.frame()](/api/class-request.mdx#request-frame) or [response.frame()](/api/class-response.mdx#response-frame) will **throw** an exception, if called on a [Request]/[Response] that has a non-null [request.serviceWorker()](/api/class-request.mdx#request-service-worker).
 :::
 
diff --git a/nodejs/docs/test-assertions.mdx b/nodejs/docs/test-assertions.mdx
index 67584e61c6..01b57a7a07 100644
--- a/nodejs/docs/test-assertions.mdx
+++ b/nodejs/docs/test-assertions.mdx
@@ -307,6 +307,7 @@ test('amount', async () => {
 ### Compatibility with expect library
 
 :::note
+
 Do not confuse Playwright's `expect` with the [`expect` library](https://jestjs.io/docs/expect). The latter is not fully integrated with Playwright test runner, so make sure to use Playwright's own `expect`.
 :::
 
diff --git a/nodejs/docs/test-global-setup-teardown.mdx b/nodejs/docs/test-global-setup-teardown.mdx
index 89f93f0e15..5fdca856fb 100644
--- a/nodejs/docs/test-global-setup-teardown.mdx
+++ b/nodejs/docs/test-global-setup-teardown.mdx
@@ -133,6 +133,7 @@ You can use the `globalSetup` option in the [configuration file](./test-configur
 Similarly, use `globalTeardown` to run something once after all the tests. Alternatively, let `globalSetup` return a function that will be used as a global teardown. You can pass data such as port number, authentication tokens, etc. from your global setup to your tests using environment variables.
 
 :::note
+
 Using `globalSetup` and `globalTeardown` will not produce traces or artifacts, and options like `headless` or `testIdAttribute` specified in the config file are not applied. If you want to produce traces and artifacts and respect config options, use [project dependencies](#option-1-project-dependencies).
 :::
 
diff --git a/nodejs/docs/test-parallel.mdx b/nodejs/docs/test-parallel.mdx
index c401226f11..8cadbdc5bd 100644
--- a/nodejs/docs/test-parallel.mdx
+++ b/nodejs/docs/test-parallel.mdx
@@ -99,6 +99,7 @@ export default defineConfig({
 You can annotate inter-dependent tests as serial. If one of the serial tests fails, all subsequent tests are skipped. All tests in a group are retried together.
 
 :::note
+
 Using serial is not recommended. It is usually better to make your tests isolated, so they can be run independently.
 :::
 
@@ -214,6 +215,7 @@ When you **disable parallel test execution**, Playwright Test runs test files in
 ### Use a "test list" file
 
 :::warning
+
 Tests lists are discouraged and supported as a best-effort only. Some features such as VS Code Extension and tracing may not work properly with test lists.
 :::
 
diff --git a/nodejs/docs/test-parameterize.mdx b/nodejs/docs/test-parameterize.mdx
index 32286f469c..bdeccd88c0 100644
--- a/nodejs/docs/test-parameterize.mdx
+++ b/nodejs/docs/test-parameterize.mdx
@@ -244,6 +244,7 @@ exports.test = base.test.extend({
 </Tabs>
 
 :::note
+
 Parameterized projects behavior has changed in version 1.18. [Learn more](./release-notes#breaking-change-custom-config-options).
 :::
 
diff --git a/nodejs/docs/test-retries.mdx b/nodejs/docs/test-retries.mdx
index 23f629cdfa..581daa3bbe 100644
--- a/nodejs/docs/test-retries.mdx
+++ b/nodejs/docs/test-retries.mdx
@@ -167,6 +167,7 @@ When running with [retries](#retries), all tests are retried together:
   * `third good` passes
 
 :::note
+
 It is usually better to make your tests isolated, so they can be efficiently run and retried independently.
 :::
 
diff --git a/nodejs/docs/test-use-options.mdx b/nodejs/docs/test-use-options.mdx
index de0edc4071..3c3bcd7a14 100644
--- a/nodejs/docs/test-use-options.mdx
+++ b/nodejs/docs/test-use-options.mdx
@@ -120,6 +120,7 @@ export default defineConfig({
 | [testOptions.proxy](/api/class-testoptions.mdx#test-options-proxy) | [Proxy settings](./network.mdx#http-proxy) used for all pages in the test. |
 
 :::note
+
 You don't have to configure anything to mock network requests. Just define a custom [Route] that mocks the network for a browser context. See our [network mocking guide](./network.mdx) to learn more.
 :::
 
diff --git a/nodejs/docs/testing-library.mdx b/nodejs/docs/testing-library.mdx
index b14a91c01d..668c93cf5a 100644
--- a/nodejs/docs/testing-library.mdx
+++ b/nodejs/docs/testing-library.mdx
@@ -11,6 +11,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 This guide describes migration to Playwright's [Experimental Component Testing](./test-components) from [DOM Testing Library](https://testing-library.com/docs/dom-testing-library/intro/), [React Testing Library](https://testing-library.com/docs/react-testing-library/intro/), [Vue Testing Library](https://testing-library.com/docs/vue-testing-library/intro) and [Svelte Testing Library](https://testing-library.com/docs/svelte-testing-library/intro).
 
 :::note
+
 If you use DOM Testing Library in the browser (for example, you bundle end-to-end tests with webpack), you can switch directly to Playwright Test. Examples below are focused on component tests, but for end-to-end test you just need to replace `await mount` with `await page.goto('http://localhost:3000/')` to open the page under test.
 :::
 
diff --git a/nodejs/docs/trace-viewer.mdx b/nodejs/docs/trace-viewer.mdx
index 1f0e5206ba..4e67ec6a92 100644
--- a/nodejs/docs/trace-viewer.mdx
+++ b/nodejs/docs/trace-viewer.mdx
@@ -46,8 +46,6 @@ When tracing with the [snapshots](/api/class-tracing.mdx#tracing-start-option-sn
 |Action|A snapshot at the moment of the performed input. This type of snapshot is especially useful when exploring where exactly Playwright clicked.|
 |After|A snapshot after the action.|
 
-<br/>
-
 Here is what the typical Action snapshot looks like:
 
 ![action tab in trace viewer](https://github.com/microsoft/playwright/assets/13063165/7168d549-eb0a-4964-9c93-483f03711fa9)
diff --git a/python/docs/api/class-accessibility.mdx b/python/docs/api/class-accessibility.mdx
index b89897a771..d5df396d15 100644
--- a/python/docs/api/class-accessibility.mdx
+++ b/python/docs/api/class-accessibility.mdx
@@ -34,6 +34,7 @@ This method is deprecated. Please use other libraries such as [Axe](https://www.
 Captures the current state of the accessibility tree. The returned object represents the root accessible node of the page.
 
 :::note
+
 The Chromium accessibility tree contains nodes that go unused on most platforms and by most screen readers. Playwright will discard them as well for an easier to process tree, unless [interesting_only](/api/class-accessibility.mdx#accessibility-snapshot-option-interesting-only) is set to `false`.
 :::
 
diff --git a/python/docs/api/class-apirequest.mdx b/python/docs/api/class-apirequest.mdx
index f2310a646b..02db825e9f 100644
--- a/python/docs/api/class-apirequest.mdx
+++ b/python/docs/api/class-apirequest.mdx
@@ -67,6 +67,7 @@ api_request.new_context(**kwargs)
   An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
   
   :::note
+  
   When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
   :::
   
diff --git a/python/docs/api/class-browser.mdx b/python/docs/api/class-browser.mdx
index 79bdbe94c8..24ff272750 100644
--- a/python/docs/api/class-browser.mdx
+++ b/python/docs/api/class-browser.mdx
@@ -70,6 +70,7 @@ In case this browser is obtained using [browser_type.launch()](/api/class-browse
 In case this browser is connected to, clears all created contexts belonging to this browser and disconnects from the browser server.
 
 :::note
+
 This is similar to force quitting the browser. Therefore, you should call [browser_context.close()](/api/class-browsercontext.mdx#browser-context-close) on any [BrowserContext]'s you explicitly created earlier with [browser.new_context()](/api/class-browser.mdx#browser-new-context) **before** calling [browser.close()](/api/class-browser.mdx#browser-close).
 :::
 
@@ -97,6 +98,7 @@ browser.close(**kwargs)
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.new_browser_cdp_session</x-search>
 
 :::note
+
 CDP Sessions are only supported on Chromium-based browsers.
 :::
 
@@ -120,6 +122,7 @@ browser.new_browser_cdp_session()
 Creates a new browser context. It won't share cookies/cache with other browser contexts.
 
 :::note
+
 If directly using this method to create [BrowserContext]s, it is best practice to explicitly close the returned context via [browser_context.close()](/api/class-browsercontext.mdx#browser-context-close) when your code is done with the [BrowserContext], and before calling [browser.close()](/api/class-browser.mdx#browser-close). This will ensure the `context` is closed gracefully and any artifacts—like HARs and videos—are fully flushed and saved.
 :::
 
@@ -213,6 +216,7 @@ await browser.close()
   An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
   
   :::note
+  
   When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
   :::
   
@@ -464,6 +468,7 @@ browser.new_page(**kwargs)
   An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
   
   :::note
+  
   When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
   :::
   
@@ -659,6 +664,7 @@ browser.new_page(**kwargs)
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.start_tracing</x-search>
 
 :::note
+
 This API controls [Chromium Tracing](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool) which is a low-level chromium-specific debugging tool. API to control [Playwright Tracing](../trace-viewer) could be found [here](./class-tracing).
 :::
 
@@ -718,6 +724,7 @@ await browser.stop_tracing()
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browser.stop_tracing</x-search>
 
 :::note
+
 This API controls [Chromium Tracing](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool) which is a low-level chromium-specific debugging tool. API to control [Playwright Tracing](../trace-viewer) could be found [here](./class-tracing).
 :::
 
diff --git a/python/docs/api/class-browsercontext.mdx b/python/docs/api/class-browsercontext.mdx
index 5bf0c34a9f..d7eecc9173 100644
--- a/python/docs/api/class-browsercontext.mdx
+++ b/python/docs/api/class-browsercontext.mdx
@@ -167,6 +167,7 @@ await browser_context.add_init_script(path="preload.js")
 </Tabs>
 
 :::note
+
 The order of evaluation of multiple scripts installed via [browser_context.add_init_script()](/api/class-browsercontext.mdx#browser-context-add-init-script) and [page.add_init_script()](/api/class-page.mdx#page-add-init-script) is not defined.
 :::
 
@@ -289,6 +290,7 @@ context.clear_permissions()
 Closes the browser context. All the pages that belong to the browser context will be closed.
 
 :::note
+
 The default browser context cannot be closed.
 :::
 
@@ -716,6 +718,7 @@ browser_context.grant_permissions(permissions, **kwargs)
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.new_cdp_session</x-search>
 
 :::note
+
 CDP sessions are only supported on Chromium-based browsers.
 :::
 
@@ -761,6 +764,7 @@ browser_context.new_page()
 Routing provides the capability to modify network requests that are made by any page in the browser context. Once route is enabled, every request matching the url pattern will stall unless it's continued, fulfilled or aborted.
 
 :::note
+
 [browser_context.route()](/api/class-browsercontext.mdx#browser-context-route) will not intercept requests intercepted by Service Worker. See [this](https://github.com/microsoft/playwright/issues/1090) issue. We recommend disabling Service Workers when using request interception by setting [service_workers](/api/class-browser.mdx#browser-new-context-option-service-workers) to `'block'`.
 :::
 
@@ -878,6 +882,7 @@ Page routes (set up with [page.route()](/api/class-page.mdx#page-route)) take pr
 To remove a route with its handler you can use [browser_context.unroute()](/api/class-browsercontext.mdx#browser-context-unroute).
 
 :::note
+
 Enabling routing disables http cache.
 :::
 
@@ -1019,6 +1024,7 @@ This setting will change the default maximum navigation time for the following m
 * [page.expect_navigation()](/api/class-page.mdx#page-wait-for-navigation)
 
 :::note
+
 [page.set_default_navigation_timeout()](/api/class-page.mdx#page-set-default-navigation-timeout) and [page.set_default_timeout()](/api/class-page.mdx#page-set-default-timeout) take priority over [browser_context.set_default_navigation_timeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout).
 :::
 
@@ -1042,6 +1048,7 @@ browser_context.set_default_navigation_timeout(timeout)
 This setting will change the default maximum time for all the methods accepting [timeout](/api/class-browsercontext.mdx#browser-context-set-default-timeout-option-timeout) option.
 
 :::note
+
 [page.set_default_navigation_timeout()](/api/class-page.mdx#page-set-default-navigation-timeout), [page.set_default_timeout()](/api/class-page.mdx#page-set-default-timeout) and [browser_context.set_default_navigation_timeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout) take priority over [browser_context.set_default_timeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout).
 :::
 
@@ -1065,6 +1072,7 @@ browser_context.set_default_timeout(timeout)
 The extra HTTP headers will be sent with every request initiated by any page in the context. These headers are merged with page-specific extra HTTP headers set with [page.set_extra_http_headers()](/api/class-page.mdx#page-set-extra-http-headers). If page overrides a particular header, page-specific header value will be used instead of the browser context header value.
 
 :::note
+
 [browser_context.set_extra_http_headers()](/api/class-browsercontext.mdx#browser-context-set-extra-http-headers) does not guarantee the order of headers in the outgoing requests.
 :::
 
@@ -1117,6 +1125,7 @@ await browser_context.set_geolocation({"latitude": 59.95, "longitude": 30.31667}
 </Tabs>
 
 :::note
+
 Consider using [browser_context.grant_permissions()](/api/class-browsercontext.mdx#browser-context-grant-permissions) to grant permissions for the browser context pages to read its geolocation.
 :::
 
@@ -1275,6 +1284,7 @@ browser_context.unroute_all(**kwargs)
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>browserContext.wait_for_event</x-search>
 
 :::note
+
 In most cases, you should use [browser_context.expect_event()](/api/class-browsercontext.mdx#browser-context-wait-for-event).
 :::
 
@@ -1310,6 +1320,7 @@ browser_context.wait_for_event(event, **kwargs)
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.background_pages</x-search>
 
 :::note
+
 Background pages are only supported on Chromium-based browsers.
 :::
 
@@ -1399,6 +1410,7 @@ browser_context.request
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.service_workers</x-search>
 
 :::note
+
 Service workers are only supported on Chromium-based browsers.
 :::
 
@@ -1437,6 +1449,7 @@ browser_context.tracing
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.on("backgroundpage")</x-search>
 
 :::note
+
 Only works with Chromium browser's persistent context.
 :::
 
@@ -1608,6 +1621,7 @@ print(await page.evaluate("location.href"))
 </Tabs>
 
 :::note
+
 Use [page.wait_for_load_state()](/api/class-page.mdx#page-wait-for-load-state) to wait until the page gets to a particular state (you should not need it in most cases).
 :::
 
@@ -1648,6 +1662,7 @@ browser_context.on("request", handler)
 Emitted when a request fails, for example by timing out. To only listen for failed requests from a particular page, use [page.on("requestfailed")](/api/class-page.mdx#page-event-request-failed).
 
 :::note
+
 HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with [browser_context.on("requestfinished")](/api/class-browsercontext.mdx#browser-context-event-request-finished) event and not with [browser_context.on("requestfailed")](/api/class-browsercontext.mdx#browser-context-event-request-failed).
 :::
 
@@ -1701,6 +1716,7 @@ browser_context.on("response", handler)
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.on("serviceworker")</x-search>
 
 :::note
+
 Service workers are only supported on Chromium-based browsers.
 :::
 
diff --git a/python/docs/api/class-browsertype.mdx b/python/docs/api/class-browsertype.mdx
index fee9e004a4..f342a2f079 100644
--- a/python/docs/api/class-browsertype.mdx
+++ b/python/docs/api/class-browsertype.mdx
@@ -117,6 +117,7 @@ This method attaches Playwright to an existing browser instance using the Chrome
 The default browser context is accessible via [browser.contexts](/api/class-browser.mdx#browser-contexts).
 
 :::note
+
 Connecting over the Chrome DevTools Protocol is only supported for Chromium-based browsers.
 :::
 
@@ -217,6 +218,7 @@ browser = await playwright.chromium.launch( # or "firefox" or "webkit".
 - `args` [List]\[[str]\] *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-type-launch-option-args"/><a href="#browser-type-launch-option-args" class="list-anchor">#</a>
   
   :::warning
+  
   Use custom browser args at your own risk, as some of them may break Playwright functionality.
   :::
   
@@ -317,6 +319,7 @@ browser_type.launch_persistent_context(user_data_dir, **kwargs)
 - `args` [List]\[[str]\] *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-type-launch-persistent-context-option-args"/><a href="#browser-type-launch-persistent-context-option-args" class="list-anchor">#</a>
   
   :::warning
+  
   Use custom browser args at your own risk, as some of them may break Playwright functionality.
   :::
   
@@ -369,6 +372,7 @@ browser_type.launch_persistent_context(user_data_dir, **kwargs)
   An array of client certificates to be used. Each certificate object must have either both `certPath` and `keyPath`, a single `pfxPath`, or their corresponding direct value equivalents (`cert` and `key`, or `pfx`). Optionally, `passphrase` property should be provided if the certificate is encrypted. The `origin` property should be provided with an exact match to the request origin that the certificate is valid for.
   
   :::note
+  
   When using WebKit on macOS, accessing `localhost` will not pick up client certificates. You can make it work by replacing `localhost` with `local.playwright`.
   :::
   
diff --git a/python/docs/api/class-dialog.mdx b/python/docs/api/class-dialog.mdx
index 764fa15b86..b17f46b73f 100644
--- a/python/docs/api/class-dialog.mdx
+++ b/python/docs/api/class-dialog.mdx
@@ -69,6 +69,7 @@ asyncio.run(main())
 </Tabs>
 
 :::note
+
 Dialogs are dismissed automatically, unless there is a [page.on("dialog")](/api/class-page.mdx#page-event-dialog) listener. When listener is present, it **must** either [dialog.accept()](/api/class-dialog.mdx#dialog-accept) or [dialog.dismiss()](/api/class-dialog.mdx#dialog-dismiss) the dialog - otherwise the page will [freeze](https://developer.mozilla.org/en-US/docs/Web/JavaScript/EventLoop#never_blocking) waiting for the dialog, and actions like click will never finish.
 :::
 
diff --git a/python/docs/api/class-elementhandle.mdx b/python/docs/api/class-elementhandle.mdx
index c2e0a79480..1572e722f8 100644
--- a/python/docs/api/class-elementhandle.mdx
+++ b/python/docs/api/class-elementhandle.mdx
@@ -11,6 +11,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ElementHandle represents an in-page DOM element. ElementHandles can be created with the [page.query_selector()](/api/class-page.mdx#page-query-selector) method.
 
 :::warning[Discouraged]
+
 The use of ElementHandle is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -394,6 +395,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [timeout](/api/class-elementhandle.mdx#element-handle-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `elementHandle.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -1534,6 +1536,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [timeout](/api/class-elementhandle.mdx#element-handle-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `elementHandle.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
@@ -1753,6 +1756,7 @@ span = await div.wait_for_selector("span", state="attached")
 </Tabs>
 
 :::note
+
 This method does not work across navigations, use [page.wait_for_selector()](/api/class-page.mdx#page-wait-for-selector) instead.
 :::
 
diff --git a/python/docs/api/class-frame.mdx b/python/docs/api/class-frame.mdx
index 9b69903565..57994012ed 100644
--- a/python/docs/api/class-frame.mdx
+++ b/python/docs/api/class-frame.mdx
@@ -759,6 +759,7 @@ await page.get_by_role("button", name=re.compile("submit", re.IGNORECASE)).click
   An attribute that is usually set by `aria-disabled` or `disabled`.
   
   :::note
+  
   Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
   :::
   
@@ -1018,6 +1019,7 @@ The method will throw an error if:
 The method will not throw an error when any valid HTTP status code is returned by the remote server, including 404 "Not Found" and 500 "Internal Server Error".  The status code for such responses can be retrieved by calling [response.status](/api/class-response.mdx#response-status).
 
 :::note
+
 The method either throws an error or returns a main resource response. The only exceptions are navigation to `about:blank` or navigation to the same URL with a different hash, which would succeed and return `null`.
 :::
 
@@ -1294,6 +1296,7 @@ Waits for the required load state to be reached.
 This returns when the frame reaches a required load state, `load` by default. The navigation must have been committed when this method is called. If current document has already reached the required state, resolves immediately.
 
 :::note
+
 Most of the time, this method is not needed because Playwright [auto-waits before every action](../actionability.mdx).
 :::
 
@@ -1438,6 +1441,7 @@ Returns frame's name attribute as specified in the tag.
 If the name is empty, returns the id attribute instead.
 
 :::note
+
 This value is calculated once when the frame is created, and will not update if the attribute is changed later.
 :::
 
@@ -1668,6 +1672,7 @@ This method double clicks an element matching [selector](/api/class-frame.mdx#fr
 When all steps combined have not finished during the specified [timeout](/api/class-frame.mdx#frame-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `frame.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -2001,6 +2006,7 @@ async with frame.expect_navigation():
 </Tabs>
 
 :::note
+
 Usage of the [History API](https://developer.mozilla.org/en-US/docs/Web/API/History_API) to change the URL is considered a navigation.
 :::
 
@@ -2590,6 +2596,7 @@ Use locator-based [frame.locator()](/api/class-frame.mdx#frame-locator) instead.
 Returns the ElementHandle pointing to the frame element.
 
 :::caution
+
 The use of [ElementHandle] is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -2629,6 +2636,7 @@ Use locator-based [frame.locator()](/api/class-frame.mdx#frame-locator) instead.
 Returns the ElementHandles pointing to the frame elements.
 
 :::caution
+
 The use of [ElementHandle] is discouraged, use [Locator] objects instead.
 :::
 
@@ -2890,6 +2898,7 @@ This method taps an element matching [selector](/api/class-frame.mdx#frame-tap-o
 When all steps combined have not finished during the specified [timeout](/api/class-frame.mdx#frame-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `frame.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
@@ -3104,6 +3113,7 @@ Use web assertions that assert visibility or a locator-based [locator.wait_for()
 Returns when element specified by selector satisfies [state](/api/class-frame.mdx#frame-wait-for-selector-option-state) option. Returns `null` if waiting for `hidden` or `detached`.
 
 :::note
+
 Playwright automatically waits for element to be ready before performing an action. Using [Locator] objects and web-first assertions make the code wait-for-selector-free.
 :::
 
diff --git a/python/docs/api/class-framelocator.mdx b/python/docs/api/class-framelocator.mdx
index 8c4fd7bd1d..58158c3bd1 100644
--- a/python/docs/api/class-framelocator.mdx
+++ b/python/docs/api/class-framelocator.mdx
@@ -332,6 +332,7 @@ await page.get_by_role("button", name=re.compile("submit", re.IGNORECASE)).click
   An attribute that is usually set by `aria-disabled` or `disabled`.
   
   :::note
+  
   Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
   :::
   
diff --git a/python/docs/api/class-jshandle.mdx b/python/docs/api/class-jshandle.mdx
index 1583621b4d..68b17b9de0 100644
--- a/python/docs/api/class-jshandle.mdx
+++ b/python/docs/api/class-jshandle.mdx
@@ -220,6 +220,7 @@ js_handle.get_property(property_name)
 Returns a JSON representation of the object. If the object has a `toJSON` function, it **will not be called**.
 
 :::note
+
 The method will return an empty JSON object if the referenced object is not stringifiable. It will throw an error if the object has circular references.
 :::
 
diff --git a/python/docs/api/class-keyboard.mdx b/python/docs/api/class-keyboard.mdx
index 965afdc867..e63fa5cf33 100644
--- a/python/docs/api/class-keyboard.mdx
+++ b/python/docs/api/class-keyboard.mdx
@@ -139,6 +139,7 @@ If [key](/api/class-keyboard.mdx#keyboard-down-option-key) is a modifier key, `S
 After the key is pressed once, subsequent calls to [keyboard.down()](/api/class-keyboard.mdx#keyboard-down) will have [repeat](https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/repeat) set to true. To release the key, use [keyboard.up()](/api/class-keyboard.mdx#keyboard-up).
 
 :::note
+
 Modifier keys DO influence `keyboard.down`. Holding down `Shift` will type the text in upper case.
 :::
 
@@ -191,6 +192,7 @@ await page.keyboard.insert_text("嗨")
 </Tabs>
 
 :::note
+
 Modifier keys DO NOT effect `keyboard.insertText`. Holding down `Shift` will not type the text in upper case.
 :::
 
@@ -209,6 +211,7 @@ Modifier keys DO NOT effect `keyboard.insertText`. Holding down `Shift` will not
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>keyboard.press</x-search>
 
 :::tip
+
 In most cases, you should use [locator.press()](/api/class-locator.mdx#locator-press) instead.
 :::
 
@@ -286,6 +289,7 @@ Shortcut for [keyboard.down()](/api/class-keyboard.mdx#keyboard-down) and [keybo
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>keyboard.type</x-search>
 
 :::caution
+
 In most cases, you should use [locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [locator.press_sequentially()](/api/class-locator.mdx#locator-press-sequentially).
 :::
 
@@ -322,6 +326,7 @@ await page.keyboard.type("World", delay=100) # types slower, like a user
 </Tabs>
 
 :::note
+
 Modifier keys DO NOT effect `keyboard.type`. Holding down `Shift` will not type the text in upper case.
 :::
 
diff --git a/python/docs/api/class-locator.mdx b/python/docs/api/class-locator.mdx
index 263f4d177a..14db00854a 100644
--- a/python/docs/api/class-locator.mdx
+++ b/python/docs/api/class-locator.mdx
@@ -23,7 +23,12 @@ Locators are the central piece of Playwright's auto-waiting and retry-ability. I
 When the locator points to a list of elements, this returns an array of locators, pointing to their respective elements.
 
 :::note
-[locator.all()](/api/class-locator.mdx#locator-all) does not wait for elements to match the locator, and instead immediately returns whatever is present in the page.  When the list of elements changes dynamically, [locator.all()](/api/class-locator.mdx#locator-all) will produce unpredictable and flaky results.  When the list of elements is stable, but loaded dynamically, wait for the full list to finish loading before calling [locator.all()](/api/class-locator.mdx#locator-all).
+
+[locator.all()](/api/class-locator.mdx#locator-all) does not wait for elements to match the locator, and instead immediately returns whatever is present in the page.
+
+When the list of elements changes dynamically, [locator.all()](/api/class-locator.mdx#locator-all) will produce unpredictable and flaky results.
+
+When the list of elements is stable, but loaded dynamically, wait for the full list to finish loading before calling [locator.all()](/api/class-locator.mdx#locator-all).
 :::
 
 **Usage**
@@ -66,6 +71,7 @@ for li in await page.get_by_role('listitem').all():
 Returns an array of `node.innerText` values for all matching nodes.
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [expect(locator).to_have_text()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) with [use_inner_text](/api/class-locatorassertions.mdx#locator-assertions-to-have-text-option-use-inner-text) option to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -107,6 +113,7 @@ texts = await page.get_by_role("link").all_inner_texts()
 Returns an array of `node.textContent` values for all matching nodes.
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [expect(locator).to_have_text()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -535,6 +542,7 @@ When all steps combined have not finished during the specified [timeout](/api/cl
 Returns the number of elements matching the locator.
 
 :::warning[Asserting count]
+
 If you need to assert the number of elements on the page, prefer [expect(locator).to_have_count()](/api/class-locatorassertions.mdx#locator-assertions-to-have-count) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -633,6 +641,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [timeout](/api/class-locator.mdx#locator-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `element.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -1189,6 +1198,7 @@ await locator.click()
 Returns the matching element's attribute value.
 
 :::warning[Asserting attributes]
+
 If you need to assert an element's attribute, prefer [expect(locator).to_have_attribute()](/api/class-locatorassertions.mdx#locator-assertions-to-have-attribute) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1438,6 +1448,7 @@ await page.get_by_role("button", name=re.compile("submit", re.IGNORECASE)).click
   An attribute that is usually set by `aria-disabled` or `disabled`.
   
   :::note
+  
   Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
   :::
   
@@ -1806,6 +1817,7 @@ locator.inner_html(**kwargs)
 Returns the [`element.innerText`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/innerText).
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [expect(locator).to_have_text()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) with [use_inner_text](/api/class-locatorassertions.mdx#locator-assertions-to-have-text-option-use-inner-text) option to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1833,6 +1845,7 @@ locator.inner_text(**kwargs)
 Returns the value for the matching `<input>` or `<textarea>` or `<select>` element.
 
 :::warning[Asserting value]
+
 If you need to assert input value, prefer [expect(locator).to_have_value()](/api/class-locatorassertions.mdx#locator-assertions-to-have-value) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1883,6 +1896,7 @@ Throws elements that are not an input, textarea or a select. However, if the ele
 Returns whether the element is checked. Throws if the element is not a checkbox or radio input.
 
 :::warning[Asserting checked state]
+
 If you need to assert that checkbox is checked, prefer [expect(locator).to_be_checked()](/api/class-locatorassertions.mdx#locator-assertions-to-be-checked) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1929,6 +1943,7 @@ checked = await page.get_by_role("checkbox").is_checked()
 Returns whether the element is disabled, the opposite of [enabled](../actionability.mdx#enabled).
 
 :::warning[Asserting disabled state]
+
 If you need to assert that an element is disabled, prefer [expect(locator).to_be_disabled()](/api/class-locatorassertions.mdx#locator-assertions-to-be-disabled) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -1975,6 +1990,7 @@ disabled = await page.get_by_role("button").is_disabled()
 Returns whether the element is [editable](../actionability.mdx#editable).
 
 :::warning[Asserting editable state]
+
 If you need to assert that an element is editable, prefer [expect(locator).to_be_editable()](/api/class-locatorassertions.mdx#locator-assertions-to-be-editable) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -2021,6 +2037,7 @@ editable = await page.get_by_role("textbox").is_editable()
 Returns whether the element is [enabled](../actionability.mdx#enabled).
 
 :::warning[Asserting enabled state]
+
 If you need to assert that an element is enabled, prefer [expect(locator).to_be_enabled()](/api/class-locatorassertions.mdx#locator-assertions-to-be-enabled) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -2067,6 +2084,7 @@ enabled = await page.get_by_role("button").is_enabled()
 Returns whether the element is hidden, the opposite of [visible](../actionability.mdx#visible).
 
 :::warning[Asserting visibility]
+
 If you need to assert that element is hidden, prefer [expect(locator).to_be_hidden()](/api/class-locatorassertions.mdx#locator-assertions-to-be-hidden) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -2116,6 +2134,7 @@ hidden = await page.get_by_role("button").is_hidden()
 Returns whether the element is [visible](../actionability.mdx#visible).
 
 :::warning[Asserting visibility]
+
 If you need to assert that element is visible, prefer [expect(locator).to_be_visible()](/api/class-locatorassertions.mdx#locator-assertions-to-be-visible) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
@@ -2374,6 +2393,7 @@ Shortcuts such as `key: "Control+o"`, `key: "Control++` or `key: "Control+Shift+
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.38</font><x-search>locator.press_sequentially</x-search>
 
 :::tip
+
 In most cases, you should use [locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page.
 :::
 
@@ -2958,6 +2978,7 @@ If the element is detached from the DOM at any moment during the action, this me
 When all steps combined have not finished during the specified [timeout](/api/class-locator.mdx#locator-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `element.tap()` requires that the `hasTouch` option of the browser context be set to true.
 :::
 
@@ -2970,6 +2991,7 @@ When all steps combined have not finished during the specified [timeout](/api/cl
 Returns the [`node.textContent`](https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent).
 
 :::warning[Asserting text]
+
 If you need to assert text on the page, prefer [expect(locator).to_have_text()](/api/class-locatorassertions.mdx#locator-assertions-to-have-text) to avoid flakiness. See [assertions guide](../test-assertions.mdx) for more details.
 :::
 
diff --git a/python/docs/api/class-mouse.mdx b/python/docs/api/class-mouse.mdx
index 5e4a67087c..26608ff2ef 100644
--- a/python/docs/api/class-mouse.mdx
+++ b/python/docs/api/class-mouse.mdx
@@ -209,6 +209,7 @@ mouse.up(**kwargs)
 Dispatches a `wheel` event. This method is usually used to manually scroll the page. See [scrolling](../input.mdx#scrolling) for alternative ways to scroll.
 
 :::note
+
 Wheel events may cause scrolling if they are not handled, and this method does not wait for the scrolling to finish before returning.
 :::
 
diff --git a/python/docs/api/class-page.mdx b/python/docs/api/class-page.mdx
index c04a5c5c48..e5169e6746 100644
--- a/python/docs/api/class-page.mdx
+++ b/python/docs/api/class-page.mdx
@@ -131,6 +131,7 @@ await page.add_init_script(path="./preload.js")
 </Tabs>
 
 :::note
+
 The order of evaluation of multiple scripts installed via [browser_context.add_init_script()](/api/class-browsercontext.mdx#browser-context-add-init-script) and [page.add_init_script()](/api/class-page.mdx#page-add-init-script) is not defined.
 :::
 
@@ -163,7 +164,12 @@ Things to keep in mind:
 * You can register multiple handlers. However, only a single handler will be running at a time. Make sure the actions within a handler don't depend on another handler.
 
 :::warning
-Running the handler will alter your page state mid-test. For example it will change the currently focused element and move the mouse. Make sure that actions that run after the handler are self-contained and do not rely on the focus and mouse state being unchanged. <br /> <br /> For example, consider a test that calls [locator.focus()](/api/class-locator.mdx#locator-focus) followed by [keyboard.press()](/api/class-keyboard.mdx#keyboard-press). If your handler clicks a button between these two actions, the focused element most likely will be wrong, and key press will happen on the unexpected element. Use [locator.press()](/api/class-locator.mdx#locator-press) instead to avoid this problem. <br /> <br /> Another example is a series of mouse actions, where [mouse.move()](/api/class-mouse.mdx#mouse-move) is followed by [mouse.down()](/api/class-mouse.mdx#mouse-down). Again, when the handler runs between these two actions, the mouse position will be wrong during the mouse down. Prefer self-contained actions like [locator.click()](/api/class-locator.mdx#locator-click) that do not rely on the state being unchanged by a handler.
+
+Running the handler will alter your page state mid-test. For example it will change the currently focused element and move the mouse. Make sure that actions that run after the handler are self-contained and do not rely on the focus and mouse state being unchanged.
+
+For example, consider a test that calls [locator.focus()](/api/class-locator.mdx#locator-focus) followed by [keyboard.press()](/api/class-keyboard.mdx#keyboard-press). If your handler clicks a button between these two actions, the focused element most likely will be wrong, and key press will happen on the unexpected element. Use [locator.press()](/api/class-locator.mdx#locator-press) instead to avoid this problem.
+
+Another example is a series of mouse actions, where [mouse.move()](/api/class-mouse.mdx#mouse-move) is followed by [mouse.down()](/api/class-mouse.mdx#mouse-down). Again, when the handler runs between these two actions, the mouse position will be wrong during the mouse down. Prefer self-contained actions like [locator.click()](/api/class-locator.mdx#locator-click) that do not rely on the state being unchanged by a handler.
 :::
 
 **Usage**
@@ -424,6 +430,7 @@ If [run_before_unload](/api/class-page.mdx#page-close-option-run-before-unload)
 By default, `page.close()` **does not** run `beforeunload` handlers.
 
 :::note
+
 if [run_before_unload](/api/class-page.mdx#page-close-option-run-before-unload) is passed as true, a `beforeunload` dialog might be summoned and should be handled manually via [page.on("dialog")](/api/class-page.mdx#page-event-dialog) event.
 :::
 
@@ -1262,6 +1269,7 @@ The first argument of the [callback](/api/class-page.mdx#page-expose-binding-opt
 See [browser_context.expose_binding()](/api/class-browsercontext.mdx#browser-context-expose-binding) for the context-wide version.
 
 :::note
+
 Functions installed via [page.expose_binding()](/api/class-page.mdx#page-expose-binding) survive navigations.
 :::
 
@@ -1368,6 +1376,7 @@ If the [callback](/api/class-page.mdx#page-expose-function-option-callback) retu
 See [browser_context.expose_function()](/api/class-browsercontext.mdx#browser-context-expose-function) for context-wide exposed function.
 
 :::note
+
 Functions installed via [page.expose_function()](/api/class-page.mdx#page-expose-function) survive navigations.
 :::
 
@@ -1467,23 +1476,6 @@ asyncio.run(main())
 
 ---
 
-### force_garbage_collection {#page-force-garbage-collection}
-
-<font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.47</font><x-search>page.force_garbage_collection</x-search>
-
-Force the browser to perform garbage collection.
-
-**Usage**
-
-```python
-page.force_garbage_collection()
-```
-
-**Returns**
-- [NoneType]<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="page-force-garbage-collection-return"/><a href="#page-force-garbage-collection-return" class="list-anchor">#</a>
-
----
-
 ### frame {#page-frame}
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.frame</x-search>
@@ -1785,6 +1777,7 @@ await page.get_by_role("button", name=re.compile("submit", re.IGNORECASE)).click
   An attribute that is usually set by `aria-disabled` or `disabled`.
   
   :::note
+  
   Unlike most other attributes, `disabled` is inherited through the DOM hierarchy. Learn more about [`aria-disabled`](https://www.w3.org/TR/wai-aria-1.2/#aria-disabled).
   :::
   
@@ -2108,6 +2101,7 @@ The method will throw an error if:
 The method will not throw an error when any valid HTTP status code is returned by the remote server, including 404 "Not Found" and 500 "Internal Server Error".  The status code for such responses can be retrieved by calling [response.status](/api/class-response.mdx#response-status).
 
 :::note
+
 The method either throws an error or returns a main resource response. The only exceptions are navigation to `about:blank` or navigation to the same URL with a different hash, which would succeed and return `null`.
 :::
 
@@ -2214,6 +2208,7 @@ Pauses script execution. Playwright will stop executing the script and wait for
 User can inspect selectors or perform manual steps while paused. Resume will continue running the original script from the place it was paused.
 
 :::note
+
 This method requires Playwright to be started in a headed mode, with a falsy [headless](/api/class-browsertype.mdx#browser-type-launch-option-headless) option.
 :::
 
@@ -2235,12 +2230,14 @@ page.pause()
 Returns the PDF buffer.
 
 :::note
+
 Generating a pdf is currently only supported in Chromium headless.
 :::
 
 `page.pdf()` generates a pdf of the page with `print` css media. To generate a pdf with `screen` media, call [page.emulate_media()](/api/class-page.mdx#page-emulate-media) before calling `page.pdf()`:
 
 :::note
+
 By default, `page.pdf()` generates a pdf with modified colors for printing. Use the [`-webkit-print-color-adjust`](https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-print-color-adjust) property to force rendering of exact colors.
 :::
 
@@ -2301,6 +2298,7 @@ The [format](/api/class-page.mdx#page-pdf-option-format) options are:
 * `A6`: 4.13in x 5.83in
 
 :::note
+
 [header_template](/api/class-page.mdx#page-pdf-option-header-template) and [footer_template](/api/class-page.mdx#page-pdf-option-footer-template) markup have the following limitations: > 1. Script tags inside templates are not evaluated. > 2. Page styles are not visible inside templates.
 :::
 
@@ -2425,6 +2423,59 @@ page.remove_locator_handler(locator)
 
 ---
 
+### request_gc {#page-request-gc}
+
+<font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.48</font><x-search>page.request_gc</x-search>
+
+Request the page to perform garbage collection. Note that there is no guarantee that all unreachable objects will be collected.
+
+This is useful to help detect memory leaks. For example, if your page has a large object `'suspect'` that might be leaked, you can check that it does not leak by using a [`WeakRef`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakRef).
+
+<Tabs
+  groupId="python-flavor"
+  defaultValue="sync"
+  values={[
+    {label: 'Sync', value: 'sync'},
+    {label: 'Async', value: 'async'}
+  ]
+}>
+<TabItem value="sync">
+
+```py
+# 1. In your page, save a WeakRef for the "suspect".
+page.evaluate("globalThis.suspectWeakRef = new WeakRef(suspect)")
+# 2. Request garbage collection.
+page.request_gc()
+# 3. Check that weak ref does not deref to the original object.
+assert page.evaluate("!globalThis.suspectWeakRef.deref()")
+```
+
+</TabItem>
+<TabItem value="async">
+
+```py
+# 1. In your page, save a WeakRef for the "suspect".
+await page.evaluate("globalThis.suspectWeakRef = new WeakRef(suspect)")
+# 2. Request garbage collection.
+await page.request_gc()
+# 3. Check that weak ref does not deref to the original object.
+assert await page.evaluate("!globalThis.suspectWeakRef.deref()")
+```
+
+</TabItem>
+</Tabs>
+
+**Usage**
+
+```python
+page.request_gc()
+```
+
+**Returns**
+- [NoneType]<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="page-request-gc-return"/><a href="#page-request-gc-return" class="list-anchor">#</a>
+
+---
+
 ### route {#page-route}
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.route</x-search>
@@ -2434,6 +2485,7 @@ Routing provides the capability to modify network requests that are made by a pa
 Once routing is enabled, every request matching the url pattern will stall unless it's continued, fulfilled or aborted.
 
 :::note
+
 The handler will only be called for the first url if the response is a redirect.
 :::
 
@@ -2552,6 +2604,7 @@ Page routes take precedence over browser context routes (set up with [browser_co
 To remove a route with its handler you can use [page.unroute()](/api/class-page.mdx#page-unroute).
 
 :::note
+
 Enabling routing disables http cache.
 :::
 
@@ -2804,6 +2857,7 @@ This setting will change the default maximum navigation time for the following m
 * [page.wait_for_url()](/api/class-page.mdx#page-wait-for-url)
 
 :::note
+
 [page.set_default_navigation_timeout()](/api/class-page.mdx#page-set-default-navigation-timeout) takes priority over [page.set_default_timeout()](/api/class-page.mdx#page-set-default-timeout), [browser_context.set_default_timeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout) and [browser_context.set_default_navigation_timeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout).
 :::
 
@@ -2827,6 +2881,7 @@ page.set_default_navigation_timeout(timeout)
 This setting will change the default maximum time for all the methods accepting [timeout](/api/class-page.mdx#page-set-default-timeout-option-timeout) option.
 
 :::note
+
 [page.set_default_navigation_timeout()](/api/class-page.mdx#page-set-default-navigation-timeout) takes priority over [page.set_default_timeout()](/api/class-page.mdx#page-set-default-timeout).
 :::
 
@@ -2850,6 +2905,7 @@ page.set_default_timeout(timeout)
 The extra HTTP headers will be sent with every request the page initiates.
 
 :::note
+
 [page.set_extra_http_headers()](/api/class-page.mdx#page-set-extra-http-headers) does not guarantee the order of headers in the outgoing requests.
 :::
 
@@ -2995,6 +3051,7 @@ page.unroute_all(**kwargs)
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.wait_for_event</x-search>
 
 :::note
+
 In most cases, you should use [page.expect_event()](/api/class-page.mdx#page-wait-for-event).
 :::
 
@@ -3138,6 +3195,7 @@ Returns when the required load state has been reached.
 This resolves when the page reaches a required load state, `load` by default. The navigation must have been committed when this method is called. If current document has already reached the required state, resolves immediately.
 
 :::note
+
 Most of the time, this method is not needed because Playwright [auto-waits before every action](../actionability.mdx).
 :::
 
@@ -3482,6 +3540,7 @@ page.viewport_size
 This method returns all of the dedicated [WebWorkers](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API) associated with the page.
 
 :::note
+
 This does not contain ServiceWorkers
 :::
 
@@ -3855,6 +3914,7 @@ print(await popup.evaluate("location.href"))
 </Tabs>
 
 :::note
+
 Use [page.wait_for_load_state()](/api/class-page.mdx#page-wait-for-load-state) to wait until the page gets to a particular state (you should not need it in most cases).
 :::
 
@@ -4166,6 +4226,7 @@ This method double clicks an element matching [selector](/api/class-page.mdx#pag
 When all steps combined have not finished during the specified [timeout](/api/class-page.mdx#page-dblclick-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 `page.dblclick()` dispatches two `click` events and a single `dblclick` event.
 :::
 
@@ -4497,6 +4558,7 @@ async with page.expect_navigation():
 </Tabs>
 
 :::note
+
 Usage of the [History API](https://developer.mozilla.org/en-US/docs/Web/API/History_API) to change the URL is considered a navigation.
 :::
 
@@ -5447,6 +5509,7 @@ This method taps an element matching [selector](/api/class-page.mdx#page-tap-opt
 When all steps combined have not finished during the specified [timeout](/api/class-page.mdx#page-tap-option-timeout), this method throws a [TimeoutError]. Passing zero timeout disables this.
 
 :::note
+
 [page.tap()](/api/class-page.mdx#page-tap) the method will throw if [has_touch](/api/class-browser.mdx#browser-new-context-option-has-touch) option of the browser context is false.
 :::
 
@@ -5661,6 +5724,7 @@ Use web assertions that assert visibility or a locator-based [locator.wait_for()
 Returns when element specified by selector satisfies [state](/api/class-page.mdx#page-wait-for-selector-option-state) option. Returns `null` if waiting for `hidden` or `detached`.
 
 :::note
+
 Playwright automatically waits for element to be ready before performing an action. Using [Locator] objects and web-first assertions makes the code wait-for-selector-free.
 :::
 
diff --git a/python/docs/api/class-request.mdx b/python/docs/api/class-request.mdx
index 9b40fcec69..6deb630314 100644
--- a/python/docs/api/class-request.mdx
+++ b/python/docs/api/class-request.mdx
@@ -15,6 +15,7 @@ Whenever the page sends a request for a network resource the following sequence
 If request fails at some point, then instead of `'requestfinished'` event (and possibly instead of 'response' event), the  [page.on("requestfailed")](/api/class-page.mdx#page-event-request-failed) event is emitted.
 
 :::note
+
 HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with `'requestfinished'` event.
 :::
 
diff --git a/python/docs/api/class-touchscreen.mdx b/python/docs/api/class-touchscreen.mdx
index 14936cfe71..1e0ebff75b 100644
--- a/python/docs/api/class-touchscreen.mdx
+++ b/python/docs/api/class-touchscreen.mdx
@@ -21,6 +21,7 @@ The Touchscreen class operates in main-frame CSS pixels relative to the top-left
 Dispatches a `touchstart` and `touchend` event with a single touch at the position ([x](/api/class-touchscreen.mdx#touchscreen-tap-option-x),[y](/api/class-touchscreen.mdx#touchscreen-tap-option-y)).
 
 :::note
+
 [page.tap()](/api/class-page.mdx#page-tap) the method will throw if [has_touch](/api/class-browser.mdx#browser-new-context-option-has-touch) option of the browser context is false.
 :::
 
diff --git a/python/docs/api/class-websocket.mdx b/python/docs/api/class-websocket.mdx
index 4e652208bf..63354ca77e 100644
--- a/python/docs/api/class-websocket.mdx
+++ b/python/docs/api/class-websocket.mdx
@@ -48,6 +48,7 @@ web_socket.expect_event(event, **kwargs)
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>webSocket.wait_for_event</x-search>
 
 :::note
+
 In most cases, you should use [web_socket.expect_event()](/api/class-websocket.mdx#web-socket-wait-for-event).
 :::
 
diff --git a/python/docs/browsers.mdx b/python/docs/browsers.mdx
index 6bf8d1bb95..c9fced2a75 100644
--- a/python/docs/browsers.mdx
+++ b/python/docs/browsers.mdx
@@ -95,6 +95,7 @@ While Playwright can download and use the recent Chromium build, it can operate
 Available channels are `chrome`, `msedge`, `chrome-beta`, `msedge-beta` or `msedge-dev`.
 
 :::warning
+
 Certain Enterprise Browser Policies may impact Playwright's ability to launch and control Google Chrome and Microsoft Edge. Running in an environment with browser policies is outside of the Playwright project's scope.
 :::
 
@@ -447,6 +448,7 @@ python playwright_script.py
 Playwright keeps track of packages that need those browsers and will garbage collect them as you update Playwright to the newer versions.
 
 :::note
+
 Developers can opt-in in this mode via exporting `PLAYWRIGHT_BROWSERS_PATH=$HOME/pw-browsers` in their `.bashrc`.
 :::
 
diff --git a/python/docs/chrome-extensions.mdx b/python/docs/chrome-extensions.mdx
index 8459406389..380b6ff943 100644
--- a/python/docs/chrome-extensions.mdx
+++ b/python/docs/chrome-extensions.mdx
@@ -9,6 +9,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ## Introduction
 
 :::note
+
 Extensions only work in Chrome / Chromium launched with a persistent context. Use custom browser args at your own risk, as some of them may break Playwright functionality.
 :::
 
@@ -158,6 +159,7 @@ def test_popup_page(page: Page, extension_id: str) -> None:
 ## Headless mode
 
 :::danger
+
 `headless=new` mode is not officially supported by Playwright and might result in unexpected behavior.
 :::
 
diff --git a/python/docs/clock.mdx b/python/docs/clock.mdx
index 2fbc63b53e..0776914a3d 100644
--- a/python/docs/clock.mdx
+++ b/python/docs/clock.mdx
@@ -24,7 +24,19 @@ The [Clock] API provides the following methods to control time:
 The recommended approach is to use `setFixedTime` to set the time to a specific value. If that doesn't work for your use case, you can use `install` which allows you to pause time later on, fast forward it, tick it, etc. `setSystemTime` is only recommended for advanced use cases.
 
 :::note
-[page.clock](/api/class-page.mdx#page-clock) overrides native global classes and functions related to time allowing them to be manually controlled:   - `Date`   - `setTimeout`   - `clearTimeout`   - `setInterval`   - `clearInterval`   - `requestAnimationFrame`   - `cancelAnimationFrame`   - `requestIdleCallback`   - `cancelIdleCallback`   - `performance`   - `Event.timeStamp`
+
+[page.clock](/api/class-page.mdx#page-clock) overrides native global classes and functions related to time allowing them to be manually controlled:
+- `Date`
+- `setTimeout`
+- `clearTimeout`
+- `setInterval`
+- `clearInterval`
+- `requestAnimationFrame`
+- `cancelAnimationFrame`
+- `requestIdleCallback`
+- `cancelIdleCallback`
+- `performance`
+- `Event.timeStamp`
 :::
 
 ## Test with predefined time
diff --git a/python/docs/debug.mdx b/python/docs/debug.mdx
index 2fda8deace..55497c8cf0 100644
--- a/python/docs/debug.mdx
+++ b/python/docs/debug.mdx
@@ -286,6 +286,7 @@ pytest -s
 </Tabs>
 
 :::note
+
 **For WebKit**: launching WebKit Inspector during the execution will prevent the Playwright script from executing any further and will reset pre-configured user agent and device emulation.
 :::
 
diff --git a/python/docs/dialogs.mdx b/python/docs/dialogs.mdx
index 0c9aeae8a5..8f14c30ab9 100644
--- a/python/docs/dialogs.mdx
+++ b/python/docs/dialogs.mdx
@@ -41,12 +41,14 @@ await page.get_by_role("button".click())
 </Tabs>
 
 :::note
+
 [page.on("dialog")](/api/class-page.mdx#page-event-dialog) listener **must handle** the dialog. Otherwise your action will stall, be it [locator.click()](/api/class-locator.mdx#locator-click) or something else. That's because dialogs in Web are modals and therefore block further page execution until they are handled.
 :::
 
 As a result, the following snippet will never resolve:
 
 :::warning
+
 WRONG!
 :::
 
@@ -77,6 +79,7 @@ await page.get_by_role("button").click() # Will hang here
 </Tabs>
 
 :::note
+
 If there is no listener for [page.on("dialog")](/api/class-page.mdx#page-event-dialog), all dialogs are automatically dismissed.
 :::
 
diff --git a/python/docs/docker.mdx b/python/docs/docker.mdx
index 8bff0e45c6..16d839a27f 100644
--- a/python/docs/docker.mdx
+++ b/python/docs/docker.mdx
@@ -15,6 +15,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 This Docker image is published to [Microsoft Artifact Registry].
 
 :::info
+
 This Docker image is intended to be used for testing and development purposes only. It is not recommended to use this Docker image to visit untrusted websites.
 :::
 
@@ -80,6 +81,7 @@ We currently publish images with the following tags:
 - `:v1.47.0-focal` - Playwright v1.47.0 release docker image based on Ubuntu 20.04 LTS (Focal Fossa).
 
 :::note
+
 It is recommended to always pin your Docker image to a specific version if possible. If the Playwright version in your Docker image does not match the version in your project/tests, Playwright will be unable to locate browser executables.
 :::
 
diff --git a/python/docs/downloads.mdx b/python/docs/downloads.mdx
index de0b5e2334..f0b3808d47 100644
--- a/python/docs/downloads.mdx
+++ b/python/docs/downloads.mdx
@@ -13,6 +13,7 @@ For every attachment downloaded by the page, [page.on("download")](/api/class-pa
 You can specify where to persist downloaded files using the [downloads_path](/api/class-browsertype.mdx#browser-type-launch-option-downloads-path) option in [browser_type.launch()](/api/class-browsertype.mdx#browser-type-launch).
 
 :::note
+
 Downloaded files are deleted when the browser context that produced them is closed.
 :::
 
@@ -89,6 +90,7 @@ page.on("download", handle_download)
 Note that handling the event forks the control flow and makes the script harder to follow. Your scenario might end while you are downloading a file since your main control flow is not awaiting for this operation to resolve.
 
 :::note
+
 For uploading files, see the [uploading files](./input.mdx#upload-files) section.
 :::
 
diff --git a/python/docs/handles.mdx b/python/docs/handles.mdx
index 12a5c8a342..837dc67ee7 100644
--- a/python/docs/handles.mdx
+++ b/python/docs/handles.mdx
@@ -51,6 +51,7 @@ js_handle = await page.evaluate_handle('window')
 ## Element Handles
 
 :::warning[Discouraged]
+
 The use of [ElementHandle] is discouraged, use [Locator] objects and web-first assertions instead.
 :::
 
@@ -178,6 +179,7 @@ Handles can be acquired using the page methods such as [page.evaluate_handle()](
 ## Locator vs ElementHandle
 
 :::caution
+
 We only recommend using [ElementHandle] in the rare cases when you need to perform extensive DOM traversal on a static page. For all user actions and assertions use locator instead.
 :::
 
diff --git a/python/docs/input.mdx b/python/docs/input.mdx
index eb9d49545c..1f1992f870 100644
--- a/python/docs/input.mdx
+++ b/python/docs/input.mdx
@@ -273,6 +273,7 @@ await page.get_by_role("button").dispatch_event('click')
 ## Type characters
 
 :::caution
+
 Most of the time, you should input text with [locator.fill()](/api/class-locator.mdx#locator-fill). See the [Text input](#text-input) section above. You only need to type characters if there is special keyboard handling on the page.
 :::
 
@@ -584,6 +585,7 @@ await page.mouse.up()
 </Tabs>
 
 :::note
+
 If your page relies on the `dragover` event being dispatched, you need at least two mouse moves to trigger it in all browsers. To reliably issue the second mouse move, repeat your [mouse.move()](/api/class-mouse.mdx#mouse-move) or [locator.hover()](/api/class-locator.mdx#locator-hover) twice. The sequence of operations would be: hover the drag element, mouse down, hover the drop element, hover the drop element second time, mouse up.
 :::
 
diff --git a/python/docs/library.mdx b/python/docs/library.mdx
index 25ea2bfbb0..ab67a4e8f9 100644
--- a/python/docs/library.mdx
+++ b/python/docs/library.mdx
@@ -179,6 +179,7 @@ pyinstaller -F main.py
 </Tabs>
 
 :::note
+
 Bundling the browsers with the executables will generate bigger binaries. It is recommended to only bundle the browsers you use.
 :::
 
diff --git a/python/docs/locators.mdx b/python/docs/locators.mdx
index bc2e07e975..11a466a395 100644
--- a/python/docs/locators.mdx
+++ b/python/docs/locators.mdx
@@ -100,6 +100,7 @@ await page.get_by_role("button", name="Sign in").click()
 </Tabs>
 
 :::note
+
 Use the [code generator](./codegen.mdx) to generate a locator, and then edit it as you'd like.
 :::
 
@@ -230,6 +231,7 @@ Role locators include [buttons, checkboxes, headings, links, lists, tables, and
 Note that role locators **do not replace** accessibility audits and conformance tests, but rather give early feedback about the ARIA guidelines.
 
 :::note[When to use role locators]
+
 We recommend prioritizing role locators to locate elements, as it is the closest way to how users and assistive technology perceive the page.
 :::
 
@@ -278,6 +280,7 @@ await page.get_by_label("Password").fill("secret")
 </Tabs>
 
 :::note[When to use label locators]
+
 Use this locator when locating form fields.
 :::
 
@@ -324,6 +327,7 @@ await page.get_by_placeholder("name@example.com").fill("playwright@microsoft.com
 </Tabs>
 
 :::note[When to use placeholder locators]
+
 Use this locator when locating form elements that do not have labels but do have placeholder texts.
 :::
 
@@ -424,6 +428,7 @@ await expect(
 </Tabs>
 
 :::note
+
 Matching by text always normalizes whitespace, even with exact match. For example, it turns multiple spaces into one, turns line breaks into spaces and ignores leading and trailing whitespace.
 :::
 
@@ -476,6 +481,7 @@ await page.get_by_alt_text("playwright logo").click()
 </Tabs>
 
 :::note[When to use alt locators]
+
 Use this locator when your element supports alt text such as `img` and `area` elements.
 :::
 
@@ -522,6 +528,7 @@ await expect(page.get_by_title("Issues count")).to_have_text("25 issues")
 </Tabs>
 
 :::note[When to use title locators]
+
 Use this locator when your element has the `title` attribute.
 :::
 
@@ -568,6 +575,7 @@ await page.get_by_test_id("directions").click()
 </Tabs>
 
 :::note[When to use testid locators]
+
 You can also use test ids when you choose to use the test id methodology or when you can't locate by [role](#locate-by-role) or [text](#locate-by-text).
 :::
 
@@ -710,6 +718,7 @@ await page.locator('//*[@id="tsf"]/div[2]/div[1]/div[1]/div/div[2]/input').click
 </Tabs>
 
 :::note[When to use this]
+
 CSS and XPath are not recommended as the DOM can often change leading to non resilient tests. Instead, try to come up with a locator that is close to how the user perceives the page such as [role locators](#locate-by-role) or [define an explicit testing contract](#locate-by-test-id) using test ids.
 :::
 
@@ -1220,6 +1229,7 @@ If you'd like to target one of the two or more elements, and you don't know whic
 For example, consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead. In this case, you can wait for either a "New email" button, or a dialog and act accordingly.
 
 :::note
+
 If both "New email" button and security dialog appear on screen, the "or" locator will match both of them, possibly throwing the ["strict mode violation" error](#strictness). In this case, you can use [locator.first](/api/class-locator.mdx#locator-first) to only match one of them.
 :::
 
@@ -1260,6 +1270,7 @@ await new_email.click()
 ### Matching only visible elements
 
 :::note
+
 It's usually better to find a [more reliable way](./locators.mdx#quick-guide) to uniquely identify the element instead of checking the visibility.
 :::
 
diff --git a/python/docs/navigations.mdx b/python/docs/navigations.mdx
index 7a2621cb32..e6548f8a77 100644
--- a/python/docs/navigations.mdx
+++ b/python/docs/navigations.mdx
@@ -43,6 +43,7 @@ await page.goto("https://example.com")
 The code above loads the page and waits for the web page to fire the [load](https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event) event. The load event is fired when the whole page has loaded, including all dependent resources such as stylesheets, scripts, iframes, and images.
 
 :::note
+
 If the page does a client-side redirect before `load`, [page.goto()](/api/class-page.mdx#page-goto) will wait for the redirected page to fire the `load` event.
 :::
 
diff --git a/python/docs/other-locators.mdx b/python/docs/other-locators.mdx
index 50478600ea..27fed7612d 100644
--- a/python/docs/other-locators.mdx
+++ b/python/docs/other-locators.mdx
@@ -9,6 +9,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 ## Introduction
 
 :::note
+
 Check out the main [locators guide](./locators) for most common and recommended locators.
 :::
 
@@ -17,6 +18,7 @@ In addition to recommended locators like [page.get_by_role()](/api/class-page.md
 ## CSS locator
 
 :::note
+
 We recommend prioritizing [user-visible locators](./locators.mdx#quick-guide) like text or accessible role instead of using CSS that is tied to the implementation and could break when the page changes.
 :::
 
@@ -125,6 +127,7 @@ Playwright include a number of CSS pseudo-classes to match elements by their tex
   For example, `:text-matches("Log\s*in", "i")` matches `<button>Login</button>` and `<button>log IN</button>`.
 
 :::note
+
 Text matching always normalizes whitespace. For example, it turns multiple spaces into one, turns line breaks into spaces and ignores leading and trailing whitespace.
 :::
 
@@ -258,6 +261,7 @@ The `:is()` pseudo-class is an [experimental CSS pseudo-class](https://developer
 ### CSS: matching elements based on layout
 
 :::note
+
 Matching based on layout may produce unexpected results. For example, a different element could be matched when layout changes by one pixel.
 :::
 
@@ -319,6 +323,7 @@ All layout pseudo-classes support optional maximum pixel distance as the last ar
 ### CSS: pick n-th match from the query result
 
 :::note
+
 It is usually possible to distinguish elements by some attribute or text content, which is more resilient to page changes.
 :::
 
@@ -387,6 +392,7 @@ await page.locator(":nth-match(:text('Buy'), 3)").wait_for()
 </Tabs>
 
 :::note
+
 Unlike [`:nth-child()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:nth-child), elements do not have to be siblings, they could be anywhere on the page. In the snippet above, all three buttons match `:text("Buy")` selector, and `:nth-match()` selects the third button.
 :::
 
@@ -492,6 +498,7 @@ parent = page.get_by_text("Hello").locator('xpath=..')
 ## React locator
 
 :::note
+
 React locator is experimental and prefixed with `_`. The functionality might change in future.
 :::
 
@@ -540,6 +547,7 @@ More examples:
 To find React element names in a tree use [React DevTools](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi).
 
 :::note
+
 React locator supports React 15 and above.
 :::
 
@@ -550,6 +558,7 @@ React locator, as well as [React DevTools](https://chrome.google.com/webstore/de
 ## Vue locator
 
 :::note
+
 Vue locator is experimental and prefixed with `_`. The functionality might change in future.
 :::
 
@@ -597,6 +606,7 @@ More examples:
 To find Vue element names in a tree use [Vue DevTools](https://chrome.google.com/webstore/detail/vuejs-devtools/nhdogjmejiglipccpnnnanhbledajbpd?hl=en).
 
 :::note
+
 Vue locator supports Vue2 and above.
 :::
 
@@ -607,6 +617,7 @@ Vue locator, as well as [Vue DevTools](https://chrome.google.com/webstore/detail
 ## XPath locator
 
 :::warning
+
 We recommend prioritizing [user-visible locators](./locators.mdx#quick-guide) like text or accessible role instead of using XPath that is tied to the implementation and easily break when the page changes.
 :::
 
@@ -637,6 +648,7 @@ await page.locator("xpath=//button").click()
 </Tabs>
 
 :::note
+
 Any selector string starting with `//` or `..` are assumed to be an xpath selector. For example, Playwright converts `'//html/body'` to `'xpath=//html/body'`.
 :::
 
@@ -677,6 +689,7 @@ await page.locator("//span[contains(@class, 'spinner__loading')]|//div[@id='conf
 ## Label to form control retargeting
 
 :::warning
+
 We recommend [locating by label text](./locators.mdx#locate-by-label) instead of relying to label-to-control retargeting.
 :::
 
@@ -747,6 +760,7 @@ await expect(page.locator("label")).to_have_text("Password")
 ## Legacy text locator
 
 :::warning
+
 We recommend the modern [text locator](./locators.mdx#get-by-text) instead.
 :::
 
@@ -858,6 +872,7 @@ Legacy text locator has a few variations:
   </Tabs>
 
 :::note
+
 String selectors starting and ending with a quote (either `"` or `'`) are assumed to be a legacy text locators. For example, `"Log in"` is converted to `text="Log in"` internally.
 :::
 
@@ -872,6 +887,7 @@ Input elements of the type `button` and `submit` are matched by their `value` in
 ## id, data-testid, data-test-id, data-test selectors
 
 :::warning
+
 We recommend [locating by test id](./locators.mdx#locate-by-test-id) instead.
 :::
 
@@ -914,12 +930,14 @@ await page.locator('data-test-id=submit').click()
 </Tabs>
 
 :::note
+
 Attribute selectors are not CSS selectors, so anything CSS-specific like `:enabled` is not supported. For more features, use a proper [css](#css-locator) selector, e.g. `css=[data-test="login"]:enabled`.
 :::
 
 ## Chaining selectors
 
 :::warning
+
 We recommend [chaining locators](./locators.mdx#matching-inside-a-locator) instead.
 :::
 
@@ -945,6 +963,7 @@ If a selector needs to include `>>` in the body, it should be escaped inside a s
 ### Intermediate matches
 
 :::warning
+
 We recommend [filtering by another locator](./locators.mdx#filter-by-childdescendant) to locate elements that contain other elements.
 :::
 
diff --git a/python/docs/selenium-grid.mdx b/python/docs/selenium-grid.mdx
index ceb2d91b28..6f34501609 100644
--- a/python/docs/selenium-grid.mdx
+++ b/python/docs/selenium-grid.mdx
@@ -11,7 +11,20 @@ import HTMLCard from '@site/src/components/HTMLCard';
 Playwright can connect to [Selenium Grid Hub](https://www.selenium.dev/documentation/grid/) that runs Selenium 4 to launch **Google Chrome** or **Microsoft Edge** browser, instead of running browser on the local machine. Note this feature is **experimental** and is prioritized accordingly.
 
 :::warning
-There is a risk of Playwright integration with Selenium Grid Hub breaking in the future. Make sure you weight risks against benefits before using it.  <br /> <br /> <details> <summary> <span style={{textTransform:'uppercase',fontSize:'smaller',fontWeight:'bold',opacity:'0.6'}}>More details</span> </summary>  Internally, Playwright connects to the browser using [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) websocket. Selenium 4 currently exposes this capability. However, this [might not be the case in the future](https://github.com/SeleniumHQ/selenium/issues/11590#issuecomment-1436113950). If Selenium drops this capability, Playwright will stop working with it. </details>
+
+There is a risk of Playwright integration with Selenium Grid Hub breaking in the future. Make sure you weight risks against benefits before using it.
+
+<details>
+
+<summary>
+
+<span style={{textTransform:'uppercase',fontSize:'smaller',fontWeight:'bold',opacity:'0.6'}}>More details</span>
+
+</summary>
+
+Internally, Playwright connects to the browser using [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) websocket. Selenium 4 currently exposes this capability. However, this [might not be the case in the future](https://github.com/SeleniumHQ/selenium/issues/11590#issuecomment-1436113950). If Selenium drops this capability, Playwright will stop working with it.
+
+</details>
 :::
 
 Before connecting Playwright to your Selenium Grid, make sure that grid works with [Selenium WebDriver](https://www.selenium.dev/documentation/webdriver/). For example, run [one of the examples](https://github.com/SeleniumHQ/selenium/tree/trunk/javascript/node/selenium-webdriver/example) and pass `SELENIUM_REMOTE_URL` environment variable. If webdriver example does not work, look for any errors at your Selenium hub/node/standalone output and search [Selenium issues](https://github.com/SeleniumHQ/selenium/issues) for a possible solution.
diff --git a/python/docs/trace-viewer.mdx b/python/docs/trace-viewer.mdx
index 77091a4922..191ebb6904 100644
--- a/python/docs/trace-viewer.mdx
+++ b/python/docs/trace-viewer.mdx
@@ -43,8 +43,6 @@ When tracing with the [snapshots](/api/class-tracing.mdx#tracing-start-option-sn
 |Action|A snapshot at the moment of the performed input. This type of snapshot is especially useful when exploring where exactly Playwright clicked.|
 |After|A snapshot after the action.|
 
-<br/>
-
 Here is what the typical Action snapshot looks like:
 
 ![action tab in trace viewer](https://github.com/microsoft/playwright/assets/13063165/7168d549-eb0a-4964-9c93-483f03711fa9)
diff --git a/python/docs/videos.mdx b/python/docs/videos.mdx
index 71930055be..4cc3d472d2 100644
--- a/python/docs/videos.mdx
+++ b/python/docs/videos.mdx
@@ -101,6 +101,7 @@ path = await page.video.path()
 </Tabs>
 
 :::note
+
 Note that the video is only available after the page or browser context is closed.
 :::
 
diff --git a/src/documentation.js b/src/documentation.js
index ea66d8ca99..876cff9e15 100644
--- a/src/documentation.js
+++ b/src/documentation.js
@@ -801,14 +801,9 @@ function generateSourceCodeComment(spec) {
       node.liType = 'default';
     if (node.type === 'code' && node.codeLang)
       node.codeLang = parseCodeLang(node.codeLang).highlighter;
-    if (node.type === 'note') {
-      // @ts-ignore
-      node.type = 'text';
-      node.text = '**NOTE** ' + node.text;
-    }
   });
   // 5 is a typical member doc offset.
-  return md.render(comments, { maxColumns: 120 - 5, omitLastCR: true, flattenText: true });
+  return md.render(comments, { maxColumns: 120 - 5, omitLastCR: true, flattenText: true, noteMode: 'compact' });
 }
 
 /**
diff --git a/src/markdown.js b/src/markdown.js
index a8ae8d4360..3e206ade3b 100644
--- a/src/markdown.js
+++ b/src/markdown.js
@@ -50,7 +50,6 @@
 
 /** @typedef {MarkdownBaseNode & {
  *    type: 'note',
- *    text: string,
  *    noteType: string,
  *  }} MarkdownNoteNode */
 
@@ -66,8 +65,9 @@
 /** @typedef {{
  * maxColumns?: number,
  * omitLastCR?: boolean,
- * flattenText?: boolean
- * renderCodeBlockTitlesInHeader?: boolean
+ * flattenText?: boolean,
+ * renderCodeBlockTitlesInHeader?: boolean,
+ * noteMode?: 'docusaurus' | 'compact',
  * }} RenderOptions
  */
 
@@ -208,7 +208,7 @@ function buildTree(lines) {
         tokens.push(line.substring(indent.length));
         line = lines[++i];
       }
-      node.text = tokens.join('↵');
+      node.children = parse(tokens.join('\n'));
       appendNode(indent, node);
       continue;
     }
@@ -340,9 +340,21 @@ function innerRenderMdNode(indent, node, lastNode, result, options) {
 
   if (node.type === 'note') {
     newLine();
-    result.push(`${indent}:::${node.noteType}`);
-    result.push(wrapText(node.text, options, indent));
-    result.push(`${indent}:::`);
+    if (options?.noteMode !== 'compact')
+      result.push(`${indent}:::${node.noteType}`);
+    const children = node.children ?? [];
+    if (options?.noteMode === 'compact') {
+      children[0] = {
+        type: 'text',
+        text: `**NOTE** ${children[0].text}`,
+      }
+    }
+    for (const child of children) {
+      innerRenderMdNode(indent, child, lastNode, result, options);
+      lastNode = child;
+    }
+    if (options?.noteMode !== 'compact')
+      result.push(`${indent}:::`);
     newLine();
     return;
   }