docs: fix title cases (#21439)

docs/src/canary-releases-js.md

@@ -1,6 +1,6 @@
 ---
 id: canary-releases
-title: "Canary Releases"
+title: "Canary releases"
 ---
 
 Playwright for Node.js has a canary releases system.

docs/src/chrome-extensions-js-python.md

@@ -1,6 +1,6 @@
 ---
 id: chrome-extensions
-title: "Chrome Extensions"
+title: "Chrome extensions"
 ---
 
 :::note

docs/src/codegen-intro.md

@@ -1,6 +1,6 @@
 ---
 id: codegen-intro
-title: "Test Generator"
+title: "Test generator"
 ---
 
 Playwright comes with the ability to generate tests out of the box and is a great way to quickly get started with testing. It will open two windows, a browser window where you interact with the website you wish to test and the Playwright Inspector window where you can record your tests, copy the tests, clear your tests as well as change the language of your tests.

docs/src/codegen.md

@@ -1,6 +1,6 @@
 ---
 id: codegen
-title: "Test Generator"
+title: "Test generator"
 ---
 
 Playwright comes with the ability to generate tests out of the box and is a great way to quickly get started with testing. It will open two windows, a browser window where you interact with the website you wish to test and the Playwright Inspector window where you can record your tests, copy the tests, clear your tests as well as change the language of your tests.

docs/src/mock-browser-js.md

@@ -1,6 +1,6 @@
 ---
 id: mock-browser-apis
-title: "Mock Browser APIs"
+title: "Mock browser APIs"
 ---
 
 Playwright provides native support for most of the browser features. However, there are some experimental APIs

docs/src/other-locators.md

@@ -1,6 +1,6 @@
 ---
 id: other-locators
-title: "Other Locators"
+title: "Other locators"
 ---
 
 :::tip

docs/src/pom.md

@@ -1,6 +1,6 @@
 ---
 id: pom
-title: "Page Object Models"
+title: "Page object models"
 ---
 Large test suites can be structured to optimize ease of authoring and maintenance. Page object models are one such approach to structure your test suite. 
 

docs/src/running-tests-csharp.md

@@ -1,6 +1,6 @@
 ---
 id: running-tests
-title: "Running Tests"
+title: "Running tests"
 ---
 
 You can run a single test, a set of tests or all tests. Tests can be run on different browsers. By default tests are run in a headless manner meaning no browser window will be opened while running the tests and results will be seen in the terminal. If you prefer you can run your tests in headed mode by using the `headless` test run parameter.

docs/src/running-tests-java.md

@@ -1,6 +1,6 @@
 ---
 id: running-tests
-title: "Running Tests"
+title: "Running tests"
 ---
 
 Playwright tests can be run in a variety of ways. We recommend hooking it up to your favorite test runner, e.g. [JUnit](./test-runners.md) since it gives you the ability to run tests in parallel, run single test, etc.
@@ -85,4 +85,4 @@ See [here](./test-runners.md) for further details on how to run tests in paralle
 
 - [Debugging tests](./debug.md)
 - [Generate tests with Codegen](./codegen.md)
-- [See a trace of your tests](./trace-viewer-intro.md)
+- [See a trace of your tests](./trace-viewer-intro.md)

docs/src/running-tests-js.md

@@ -1,6 +1,6 @@
 ---
 id: running-tests
-title: "Running Tests"
+title: "Running tests"
 ---
 
 You can run a single test, a set of tests or all tests. Tests can be run on one browser or multiple browsers. By default tests are run in a headless manner meaning no browser window will be opened while running the tests and results will be seen in the terminal.

docs/src/running-tests-python.md

@@ -1,6 +1,6 @@
 ---
 id: running-tests
-title: "Running Tests"
+title: "Running tests"
 ---
 
 You can run a single test, a set of tests or all tests. Tests can be run on one browser or multiple browsers. By default tests are run in a headless manner meaning no browser window will be opened while running the tests and results will be seen in the terminal. If you prefer you can run your tests in headed mode by using the `--headed` flag.
@@ -83,4 +83,4 @@ Check out our [debugging guide](./debug.md) to learn more about the [Playwright
 ## What's Next
 
 - [Generate tests with Codegen](./codegen.md)
-- [See a trace of your tests](./trace-viewer-intro.md)
+- [See a trace of your tests](./trace-viewer-intro.md)

docs/src/test-fixtures-js.md

@@ -1,6 +1,6 @@
 ---
 id: test-fixtures
-title: "Advanced: fixtures"
+title: "Fixtures"
 ---
 
 Playwright Test is based on the concept of test fixtures. Test fixtures are used to establish environment for each test, giving the test everything it needs and nothing else. Test fixtures are isolated between tests. With fixtures, you can group tests based on their meaning, instead of their common setup.

docs/src/test-retries-js.md

@@ -1,6 +1,6 @@
 ---
 id: test-retries
-title: "Test retry"
+title: "Retries"
 ---
 
 Test retries are a way to automatically re-run a test when it fails. This is useful when a test is flaky and fails intermittently. Test retries are configured in the [configuration file](./test-configuration.md).

docs/src/test-webserver-js.md

@@ -1,6 +1,6 @@
 ---
 id: test-webserver
-title: "Web Server"
+title: "Web server"
 ---
 
 Playwright comes with a `webserver` option in the config file which gives you the ability to launch a local dev server before running your tests. This is ideal for when writing your tests during development and when you don't have a staging or production url to test against.

docs/src/trace-viewer-intro-csharp-java-python.md

@@ -1,6 +1,6 @@
 ---
 id: trace-viewer-intro
-title: "Trace Viewer"
+title: "Trace viewer"
 ---
 
 Playwright Trace Viewer is a GUI tool that lets you explore recorded Playwright traces of your tests meaning you can go back and forward though each action of your test and visually see what was happening during each action.

docs/src/trace-viewer-intro-js.md

@@ -1,6 +1,6 @@
 ---
 id: trace-viewer-intro
-title: "Trace Viewer"
+title: "Trace viewer"
 ---
 
 Playwright Trace Viewer is a GUI tool that lets you explore recorded Playwright traces of your tests meaning you can go back and forward through each action of your test and visually see what was happening during each action.

docs/src/trace-viewer.md

@@ -1,6 +1,6 @@
 ---
 id: trace-viewer
-title: "Trace Viewer"
+title: "Trace viewer"
 ---
 
 

docs/src/writing-tests-csharp.md

@@ -1,6 +1,6 @@
 ---
 id: writing-tests
-title: "Writing Tests"
+title: "Writing tests"
 ---
 
 Playwright assertions are created specifically for the dynamic web. Checks are automatically retried until the necessary conditions are met. Playwright comes with [auto-wait](./actionability.md) built in meaning it waits for elements to be actionable prior to performing actions. Playwright provides the [Expect](./test-assertions) function to write assertions.
@@ -246,4 +246,4 @@ public class UnitTest1 : PageTest
 
 - [Run single test, multiple tests, headed mode](./running-tests.md)
 - [Generate tests with Codegen](./codegen.md)
-- [See a trace of your tests](./trace-viewer-intro.md)
+- [See a trace of your tests](./trace-viewer-intro.md)

docs/src/writing-tests-java.md

@@ -1,6 +1,6 @@
 ---
 id: writing-tests
-title: "Writing Tests"
+title: "Writing tests"
 ---
 
 Playwright assertions are created specifically for the dynamic web. Checks are automatically retried until the necessary conditions are met. Playwright comes with [auto-wait](./actionability.md) built in meaning it waits for elements to be actionable prior to performing actions. Playwright provides [assertThat](./test-assertions.md) overloads to write assertions.

docs/src/writing-tests-js.md

@@ -1,6 +1,6 @@
 ---
 id: writing-tests
-title: "Writing Tests"
+title: "Writing tests"
 ---
 
 Playwright tests are simple, they

docs/src/writing-tests-python.md

@@ -1,6 +1,6 @@
 ---
 id: writing-tests
-title: "Writing Tests"
+title: "Writing tests"
 ---
 
 Playwright assertions are created specifically for the dynamic web. Checks are automatically retried until the necessary conditions are met. Playwright comes with [auto-wait](./actionability.md) built in meaning it waits for elements to be actionable prior to performing actions. Playwright provides an [expect](./test-assertions.md) function to write assertions.
@@ -94,4 +94,4 @@ def test_main_navigation(page: Page):
 
 - [Run single test, multiple tests, headed mode](./running-tests.md)
 - [Generate tests with Codegen](./codegen.md)
-- [See a trace of your tests](./trace-viewer-intro.md)
+- [See a trace of your tests](./trace-viewer-intro.md)