docs: fix docs links (#19510)

Signed-off-by: Max Schmitt <max@schmitt.mx> Co-authored-by: Max Schmitt <max@schmitt.mx>
microsoft · Dec 20, 2022 · 6846765 · 6846765
1 parent 412c11d
commit 6846765
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/docs/src/api/class-page.md b/docs/src/api/class-page.md
@@ -825,7 +825,7 @@ Get the browser context that the page belongs to.
 Only available for Chromium atm.
 :::
 
-Browser-specific Coverage implementation. See [Coverage](#class-coverage) for more details.
+Browser-specific Coverage implementation. See [Coverage](./class-coverage) for more details.
 
 ## async method: Page.dblclick
 * since: v1.8

diff --git a/docs/src/api/class-playwright.md b/docs/src/api/class-playwright.md
@@ -186,7 +186,7 @@ Playwright methods might throw errors if they are unable to fulfill a request. F
 [`method: Locator.waitFor`] might fail if the selector doesn't match any nodes during the given timeframe.
 
 For certain types of errors Playwright uses specific error classes. These classes are available via
-[`playwright.errors`](#playwrighterrors).
+[`playwright.errors`](#playwright-errors).
 
 An example of handling a timeout error:
 

diff --git a/docs/src/test-configuration-js.md b/docs/src/test-configuration-js.md
@@ -435,7 +435,7 @@ const config: PlaywrightTestConfig = {
 export default config;
 ```
 
-However, most common ones like `headless` or `viewport` are available directly in the `use` section - see [basic options](#basic-options), [emulation](#emulation) or [network](#network).
+However, most common ones like `headless` or `viewport` are available directly in the `use` section - see [basic options](#basic-options), [emulation](./emulation.md) or [network](#network).
 
 ## Explicit Context Creation and Option Inheritance
 

diff --git a/docs/src/webview2.md b/docs/src/webview2.md
@@ -428,6 +428,6 @@ public class Tests : WebView2Test
 
 ## Debugging
 
-Inside your webview2 control, you can just right-click to open the context menu and select "Inspect" to open the DevTools or press <kbd>F12</kbd>. You can also use the [WebView2.OpenDevToolsWindow](https://docs.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.wpf.webview2.opendevtoolswindow?view=webview2-dotnet-1.0.1343.22) method to open the DevTools programmatically.
+Inside your webview2 control, you can just right-click to open the context menu and select "Inspect" to open the DevTools or press <kbd>F12</kbd>. You can also use the [WebView2.CoreWebView2.OpenDevToolsWindow](https://learn.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.core.corewebview2.opendevtoolswindow?view=webview2-dotnet-1.0.1462.37) method to open the DevTools programmatically.
 
 For debugging tests, see the Playwright [Debugging guide](./debug).