testdriverai 5.6.3 → 5.6.5

package/docs/interactive/generate.mdx

@@ -21,7 +21,7 @@ The `/generate` command is an experimental feature that instructs TestDriver to
 - TestDriver generates 10 Markdown files every time the `/generate` command is called.
 - The generated files are stored in the `./testdriver/generate/*.md` directory.
 
-## Example Output
+## Example output
 Here's an example of a generated test file (`test-search-function.md`):
 ```markdown
 1. Click on the search icon.
@@ -31,7 +31,7 @@ Here's an example of a generated test file (`test-search-function.md`):
 
 ## Protips
 - Use `/generate` to quickly create exploratory tests for regression testing or feature validation.
-- Combine `/generate` with the GitHub action to generate and run regression tests in parallel.
+- Combine `/generate` with the GitHub Action to generate and run regression tests in parallel.
 - Review the generated Markdown files and convert them into YAML test scripts for reuse.
 
 ## Gotchas

package/docs/interactive/run.mdx

@@ -1,39 +1,39 @@
 ---
 title: "/run"
 sidebarTitle: "/run"
-description: "Run a test plan from a file."
+description: "Run a test file from a file."
 icon: "play"
 ---
 
 ## Description
-The `/run` command is used to execute a test plan from a specified file. This command performs each step defined in the test plan and outputs the results.
+The `/run` command is used to execute a test file from a specified file. This command performs each step defined in the test file and outputs the results.
 
 ## Usage
 ```bash
 /run <file>
 ```
 
-## Example Usage
+## Example usage
 ```bash
 testdriverai
-> /run helloworld.yml
+> /run helloworld.yaml
 ```
-This command runs the `helloworld.yml` test plan, executing each command in the file sequentially.
+This command runs the `helloworld.yaml` test file, executing each command in the file sequentially.
 
 ## Behavior
-- TestDriver will execute the test plan, performing each command as defined in the file.
+- TestDriver will execute the test file, performing each command as defined in the file.
 - If the test completes successfully, the program will exit with code `0`.
 - If any failures occur during the test, the program will output the errors and exit with code `1`.
 
 ## Protips
 - Ensure the test file path is correct and accessible before running the command.
-- Use descriptive filenames for your test plans to make them easier to identify.
+- Use descriptive filenames for your test files to make them easier to identify.
 - Combine `/run` with debugging tools to troubleshoot failing tests.
 
 ## Gotchas
 - This command will exit the program upon execution, so ensure all necessary setup is complete before running it.
-- Any errors in the test plan (e.g., invalid commands or missing arguments) will cause the test to fail.
+- Any errors in the test file (for example, invalid commands or missing arguments) will cause the test to fail.
 
 ## Notes
-- The `/run` command is ideal for executing pre-created test plans in an interactive session.
-- Use this command to validate and debug your test plans during development.
+- The `/run` command is ideal for executing pre-created test files in an interactive session.
+- Use this command to validate and debug your test files during development.

package/docs/interactive/save.mdx

@@ -13,7 +13,7 @@ The `/save` command saves the current state of the test script to a file. This c
 /save
 ```
 
-## Example Usage
+## Example usage
 ```bash
 testdriverai
 > /save
@@ -41,7 +41,7 @@ testdriverai
 
 ## Behavior
 - The `/save` command generates a YAML file with the current test script, including all executed steps and commands.
-- The file can be used as a reusable test plan for future executions.
+- The file can be used as a reusable test file for future executions.
 
 ## Protips
 - Use `/save` frequently during interactive sessions to preserve your progress and avoid losing work.
@@ -49,7 +49,7 @@ testdriverai
 
 ## Gotchas
 - Ensure you have write permissions in the directory where the file will be saved.
-- The saved script reflects the current state of the session. Any unexecuted commands will not be included.
+- The saved script reflects the current state of the session. Any unexecuted commands won't be included.
 
 ## Notes
 - The `/save` command is ideal for creating reusable test scripts from interactive sessions.

package/docs/interactive/undo.mdx

@@ -17,7 +17,7 @@ The `/undo` command removes the last generated command or step from the current
 - The `/undo` command removes the most recently added command or step from the test script.
 - You can call `/undo` multiple times to remove multiple commands or steps.
 
-## Example Usage
+## Example usage
 
 ### Before `/undo`
 ```yaml

package/docs/overview/comparison.mdx

@@ -5,7 +5,7 @@ description: "TestDriver vs Playwright vs Selenium"
 icon: boxing-glove
 ---
 
-### Application Support
+### Application support
 
 TestDriver operates a full desktop environment, so it can run any application.
 
@@ -16,7 +16,7 @@ TestDriver operates a full desktop environment, so it can run any application.
 | Chrome Extensions | ✅            |          |        |
 
 
-### Testing Features
+### Testing features
 
 TestDriver is AI first.
 
@@ -31,7 +31,7 @@ TestDriver is AI first.
 | Team Dashboard        | ✅            |          |        |
 | Team Collaboration    | ✅            |          |        |
 
-### Test Coverage
+### Test coverage
 
 TestDriver has more coverage than selector-based frameworks.
 
@@ -49,7 +49,7 @@ TestDriver has more coverage than selector-based frameworks.
 | `<canvas>`         | ✅            |          |        |
 | `<video>`          | ✅            |          |        |
 
-### Debugging Features
+### Debugging features
 
 Debugging features are powered by [Dashcam.io](https://dashcam.io).
 
@@ -63,7 +63,7 @@ Debugging features are powered by [Dashcam.io](https://dashcam.io).
 | Team Dashboard     | ✅            |          |        |
 | Team Collaboration | ✅            |          |        |
 
-### Web Browser Support
+### Web browser support
 
 TestDriver is browser agnostic and supports any version of any browser.
 
@@ -77,7 +77,7 @@ TestDriver is browser agnostic and supports any version of any browser.
 | Opera    | ✅            |          | ✅       |
 | Safari   | ✅            |          | ✅       |
 
-### Operating System Support
+### Operating system support
 
 TestDriver currently supports Mac and Windows!
 

package/docs/overview/faq.mdx

@@ -6,7 +6,7 @@ icon: "block-question"
 ---
 
 
-## What is TestDriver?
+## What's TestDriver?
 TestDriver is an AI-powered testing platform that simulates user interactions to automate end-to-end testing for web, desktop, and mobile applications.
 
 ## How does TestDriver work?
@@ -67,7 +67,7 @@ Yes. TestDriver supports parallel execution using multiple VMs or containers.
 Yes. It can log CPU, memory, load times, and frame rates to help catch performance regressions.
 
 ## Can it validate non-deterministic output?
-Yes. It uses AI assertions to verify outcomes even when outputs vary (e.g., generated text or dynamic UIs).
+Yes. It uses AI assertions to verify outcomes even when outputs vary (for example, generated text or dynamic UIs).
 
 ## Can it test workflows with variable inputs?
 Yes. It supports data-driven tests using parameterized inputs.

package/docs/overview/quickstart.mdx

@@ -217,4 +217,4 @@ TestDriver can also generate tests without any input! Instead, it will suggest t
 
 </Step>
 
-</Steps>
+</Steps>

package/docs/overview/upgrading.mdx

@@ -5,7 +5,9 @@ description: "Learn how to upgrade TestDriver for the latest features and improv
 icon: "circle-up"
 ---
 
-## How to Upgrade TestDriver
+import YmlWarning from '/snippets/yml-warning.mdx'
+
+## How to upgrade TestDriver
 To upgrade TestDriver, follow these steps:
 1. **Check for Updates**: Regularly check the [TestDriver NPM Package](https://www.npmjs.com/package/testdriverai)
 2. **Update Command**: Use the following command to update TestDriver to the latest version:
@@ -17,10 +19,12 @@ To upgrade TestDriver, follow these steps:
    npm install -g testdriverai@beta
    ```
 
-In your existing Github Action setup, you may need to update the `version` field in the `workflows/testdriver.yaml` file(s) to match the version of TestDriver you want to use. Leaving it blank will run `latest` by default. Here is an example of what to replace:
+<YmlWarning/>
+
+In your existing GitHub Actions setup, you may need to update the `version` field in the `workflows/testdriver.yaml` file(s) to match the version of TestDriver you want to use. Leaving it blank will run `latest` by default. Here is an example of what to replace:
 
 ```yaml {16}
-name: TestDriver.ai
+name: TestDriver
 
 on:
   push:
@@ -56,7 +60,7 @@ jobs:
 Would become:
 
 ```yaml {16}
-name: TestDriver.ai
+name: TestDriver
 
 on:
   push:

package/docs/overview/what-is-testdriver.mdx

@@ -1,6 +1,6 @@
 ---
-title: "What is TestDriver?"
-sidebarTitle: "What is TestDriver?"
+title: "What's TestDriver?"
+sidebarTitle: "What's TestDriver?"
 description: "TestDriver is a computer-use agent for QA testing of user interfaces."
 icon: "circle-info"
 ---
@@ -21,9 +21,9 @@ TestDriver uses AI vision and keyboard and mouse control to automate end-to-end
 
 TestDriver is different from other computer-use agents in that it produces a `YAML` test script that increases the speed and repeatability of testing.
 
-### Selectorless Testing
+### Selectorless testing
 
-Unlike traditional frameworks (e.g., Selenium, Playwright), TestDriver doesn't rely on CSS selectors or static analysis. Instead, tests are described in plain English, such as:
+Unlike traditional frameworks (for example, Selenium, Playwright), TestDriver doesn't rely on CSS selectors or static analysis. Instead, tests are described in plain English, such as:
 
 ```
 > Open Google Chrome and search for "testdriver"
@@ -60,7 +60,7 @@ Old and Busted (Selectors)  | New Hotness (TestDriver)
 |:----------------------|:-------------------|
 ```div[class="product-card"] >> text="Add to Cart" >> nth=2``` | buy the 2nd product
 
-These high level instructions are easier to create and maintain because they are loosely coupled from the codebase. We're describing a high level goal, not a low level interaction.
+These high level instructions are easier to create and maintain because they're loosely coupled from the codebase. We're describing a high level goal, not a low level interaction.
 
 The tests will still continue to work even when the junior developer changes .product-card to .product.card or the designers change Add to Cart to Buy Now . The concepts remain the same so the AI will adapt. 
 
@@ -68,7 +68,7 @@ The tests will still continue to work even when the junior developer changes .pr
 
 TestDriver uses a combination of reinforcement learning and computer vision. The context from successful text executions inform future executions. Here's an example of the context our model considers when locating a text match:
 
-Context| What is it? | Touchpoint
+Context| What's it? | Touchpoint
 |:----------|:------------------|:----------------|
 Prompt | Desired outcome | User Input
 Screenshot | Image of computer desktop | Runtime

package/docs/quickstart.mdx

@@ -57,7 +57,7 @@ TestDriver will generate steps like:
 <Step title="Run Saved Tests">
 Once saved, you can run your test file anytime:  
 ```bash
-testdriverai run path/to/test.yml
+testdriverai run path/to/test.yaml
 ```
 </Step>
 

package/docs/scenarios/ai-chatbot.mdx

@@ -1,6 +1,6 @@
 ---
-title: "AI Chatbot"
-sidebarTitle: "AI Chatbot"
+title: "AI Chatbots"
+sidebarTitle: "AI Chatbots"
 description: "Integrate AI chatbots into your testing workflow."
 icon: "message-bot"
 ---
@@ -18,7 +18,7 @@ This scenario is an example of how to set up and run tests for an AI chatbot usi
 
 <TestPrereqs />
 
-## Scenario Overview
+## Scenario overview
 1. Load a website with an AI chatbot. 
 2. Type a chat message or ask a question.
 3. Wait for the chatbot to respond.

package/docs/scenarios/cookie-banner.mdx

@@ -11,14 +11,14 @@ With TestDriver, you can automate the testing of cookie banners on your web appl
 
 <TestPrereqs />
 
-## Scenario Overview
+## Scenario overview
 1. **Visit the Site**: The test will navigate to the target URL.
 2. **Check for Cookie Banner**: It will verify if the cookie banner is displayed.
 3. **Decline Cookies**: The test will simulate a user clicking the "Decline All" button on the cookie banner.
 
 
 
-## TestDriver in Action
+## TestDriver in action
 <iframe
   width="560"
   height="315"

package/docs/scenarios/file-upload.mdx

@@ -11,14 +11,14 @@ This scenario demonstrates how to automate testing the file upload functionality
 
 <TestPrereqs />
 
-## Scenario Overview
+## Scenario overview
 1. Load a website with a file upload feature. 
 2. Generate a file that will be used for the upload.
 3. Use TestDriver to perform the file upload process. 
 4. Check if the uploaded file is processed correctly by the application.
 
 
-## TestDriver in Action
+## TestDriver in action
 <iframe
   width="560"
   height="315"

package/docs/scenarios/form-filling.mdx

@@ -9,14 +9,14 @@ import TestPrereqs from '/snippets/test-prereqs.mdx'
 
 <TestPrereqs />
 
-## Scenario Overview
+## Scenario overview
 1. Open a webpage containing a form (Log in, Registration, etc.).
 2. Use TestDriver to fill in the form fields with test data.
-3. Submit the form and verify the expected outcome (e.g., successful login, registration confirmation, redirect etc.).
+3. Submit the form and verify the expected outcome (for example, successful login, registration confirmation, redirect etc.).
 
 
 
-## TestDriver in Action
+## TestDriver in action
 <iframe
   width="560"
   height="315"

package/docs/scenarios/log-in.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Login Scenario"
+title: "Login"
 sidebarTitle: "Login"
 description: "Test login functionality with TestDriver"
 icon: "lock"
@@ -11,7 +11,7 @@ Test login functionality with TestDriver. This scenario demonstrates how to auto
 
 <TestPrereqs />
 
-## Scenario Overview
+## Scenario overview
 1. Visit the login page of the web application.
 2. Enter the username and password into the respective fields (see [Reusable Snippets](/features/reusable-snippets#How-to Create-and-Use-Reusable-Snippets)).
 3. Click the "Login" button.
@@ -20,7 +20,7 @@ Test login functionality with TestDriver. This scenario demonstrates how to auto
 
 
 ### Setup your test environment with predefined credentials.
-In this example, we will use GitHub secret management to store our credentials.
+This example uses GitHub secret management to store credentials.
 
 <Tip>You can also use the [`exec`](commands/exec) command to fetch a test user dynamically from a database or API.</Tip>
 

package/docs/scenarios/pdf-generation.mdx

@@ -11,11 +11,11 @@ Test PDF generation functionality with TestDriver. This scenario demonstrates ho
 
 <TestPrereqs />
 
-## Scenario Overview
+## Scenario overview
 1. Open a webpage or desktop app that will allow you to generate a PDF.
-2. Trigger the PDF generation process (e.g., by clicking a button).
+2. Trigger the PDF generation process (for example, by clicking a button).
 3. Verify that the PDF is generated successfully and contains the expected content.
 4. Optionally, check the file size and format of the generated PDF.
 
-## What Next?
+## What's next
 From here you can automate and add coverage to your PDF generation process, removing manual testing from the equation.

package/docs/scenarios/spell-check.mdx

@@ -11,10 +11,10 @@ This scenario demonstrates how to automate testing the spell check functionality
 
 <TestPrereqs />
 
-## Scenario Overview
+## Scenario overview
 1. Open up a webpage that has text input and a spell check function.
 2. Enter a misspelled word into the text input field.
-3. Trigger the spell check function (e.g., by clicking a button or losing focus on the input field).
+3. Trigger the spell check function (for example, by clicking a button or losing focus on the input field).
 4. Verify that the spell checker identifies the misspelled word and provides suggestions for correction.
 5. Optionally, select a suggestion and apply it to the text input field.
 

package/docs/security/action.mdx

@@ -7,12 +7,12 @@ icon: shield-check
 
 import GitignoreWarning from '/snippets/gitignore-warning.mdx';
 
-## Open Source
+## Open source
 The TestDriver Action is open source, and its source code is available for review. You can find the repository here:
 
 <Card horizontal="true" icon="github"> [GitHub - testdriverai/action](https://github.com/testdriverai/action) </Card>
 
-## Ephemeral Virtual Machine Runners
+## Ephemeral virtual machine runners
 TestDriver tests are executed on private virtual machines (VMs) managed by Amazon EC2. These VMs are ephemeral, meaning they only exist for the duration of the test execution. Once the test is complete:
 - The VM is destroyed.
 - The hard disk is wiped to ensure no residual data remains.
@@ -20,15 +20,15 @@ TestDriver tests are executed on private virtual machines (VMs) managed by Amazo
 ## Secrets
 To securely manage private information, we recommend storing sensitive data as secrets in your GitHub repository. Learn more about [storing secrets in GitHub](https://docs.github.com/en/actions/security-guides/encrypted-secrets).
 
-### Handling Secrets
+### Handling secrets
 - **Prerun Scripts**: Any secrets supplied within prerun scripts or prompts are transmitted over SSL to the TestDriver API. Prerun scripts are **not persisted**.
 - **Agent Prompts**: Secrets supplied to agent prompts are persisted (see [Agent Security](/security/agent)).
 - **Secure Workflows**: If your workflow requires secret sharing and you encounter issues, please contact us for assistance.
 
-### Common Use Case
+### Common use case
 A common workflow involves using prerun scripts to securely access a private staging website via basic authentication. This allows you to log into staging environments without persisting sensitive data on TestDriver servers.
 
-## Environment-Specific Security
+## Environment-specific security
 
 <GitignoreeWarning/>
 
@@ -46,7 +46,7 @@ Testing staging environments may require secure information, such as credentials
 ### Development
 TestDriver can clone feature branches and build code on its virtual machines using workflows similar to GitHub Actions.
 
-#### GitHub Token for Development
+#### GitHub token for development
 To test development branches of private codebases, you must supply a GitHub personal access token within the GitHub Action. This token is used to:
 - Clone the codebase onto the VM.
 - Build and test the code in an isolated environment.

package/docs/security/agent.mdx

@@ -13,7 +13,7 @@ The TestDriver Agent doesn't contain any AI models within it. Instead, it upload
 
 The TestDriver API leverages OpenAI models behind the scenes. For more information about OpenAI and its privacy practices, visit their [privacy center](https://openai.com/privacy).
 
-## Desktop Context Collected
+## Desktop context collected
 During execution, the TestDriver Agent uploads the following information to the API:
 
 - **User Input Prompts**: The commands and prompts you provide to TestDriver.
@@ -22,30 +22,30 @@ During execution, the TestDriver Agent uploads the following information to the
 - **Mouse Position**: The current position of the mouse pointer.
 - **Desktop Screenshots**: Screenshots of the primary display.
 
-### Data Persistence
+### Data persistence
 - **Desktop Context**: All collected desktop context, except for screenshots, is persisted in the TestDriver database.
 - **Desktop Screenshots**: Screenshots are uploaded to the server for processing but aren't stored in the database.
 
-### Desktop Screenshots
+### Desktop screenshots
 TestDriver frequently captures screenshots of the desktop to provide the AI with decision-making context. These screenshots are uploaded to the API but aren't persisted in the database. 
 
 - **Primary Display Only**: Screenshots are limited to the primary display.
-- **Privacy Recommendation**: For complete privacy, it is recommended to run TestDriver within a virtual machine on your desktop.
+- **Privacy Recommendation**: For complete privacy, it's recommended to run TestDriver within a virtual machine on your desktop.
 
 **Important**: TestDriver can't operate without visual context. don't install TestDriver if you are uncomfortable with capturing images of the desktop.
 
-## Collected Data Details
+## Collected data details
 
-### Active Window
+### Active window
 Information about the open windows on the desktop is reported using the `active-window` module. This includes details such as the application name and window titles.
 
-### System Information
+### System information
 System details, such as operating system, CPU, and memory, are reported using the `systeminformation` module.
 
-### User Prompts
+### User prompts
 The prompts you input into TestDriver are uploaded to the API and stored in a database. This data is used to provide the AI with a history of context for better decision-making.
 
-## Additional Analytics
+## Additional analytics
 When running `testdriver init`, you will be asked if you would like to share additional analytics. Sharing usage analytics is **opt-in**, and no extra data will be collected unless explicitly enabled.
 
 To disable additional analytics, set the `TD_ANALYTICS` environment variable to `false`:
@@ -53,7 +53,7 @@ To disable additional analytics, set the `TD_ANALYTICS` environment variable to
 TD_ANALYTICS=false
 ```
 
-## Rate Limiting and Restrictions
+## Rate limiting and restrictions
 While the TestDriver Agent is free to use, TestDriver reserves the right to rate limit or restrict usage by IP address for any reason.
 
 ## Notes

package/docs/security/platform.mdx

@@ -12,19 +12,19 @@ The TestDriver web dashboard provides a secure interface for managing and review
 
 Dashcam and TestDriver share the same API and web application back end, which includes robust privacy and security features.
 
-## Security Features
+## Security features
 
 ### SSL
 - All data transmitted between your browser and the TestDriver web application is encrypted using HTTPS.
 
-### OAuth Authentication
+### Authentication
 - Users can only authenticate via OAuth, provided by Auth0, ensuring secure and reliable user authentication.
 
-### Team Management
+### Team management
 - Administrators can add or remove individual team members.
 - Only administrators have the ability to manage team settings.
 
-### Role-Based Access Control (RBAC)
+### Role-based access control (RBAC)
 - The first user to create a team is designated as the administrator.
 - Administrators:
   - Are the only users who can view the API key.
@@ -32,9 +32,9 @@ Dashcam and TestDriver share the same API and web application back end, which in
   - can't be removed from the team.
 - All other users are normal members with limited access.
 
-### API Key Rotation
+### API key rotation
 - Teams can rotate their API key for enhanced security.
-- It is recommended to rotate the API key every 90 days to minimize risk.
+- It's recommended to rotate the API key every 90 days to minimize risk.
 
 <Check>
     For more details on **Team Management** see the [Team documentation](/account/team).
@@ -42,7 +42,7 @@ Dashcam and TestDriver share the same API and web application back end, which in
 
 <GitignoreWarning/>
 
-### Secret Masking
+### Secret masking
 - Test replay logs and network requests are automatically scanned for sensitive information, such as:
   - Credit card numbers
   - Emails
@@ -50,7 +50,7 @@ Dashcam and TestDriver share the same API and web application back end, which in
   - API keys
 - Detected secrets are masked with asterisks (`****`) to prevent exposure.
 
-### Encrypted At Rest
+### Encrypted at rest
 - Test replays and logs are securely stored on Amazon S3 and encrypted at rest.
 - Test results are only accessible via temporary signed URLs.
 - Signed URLs are generated exclusively for team users and expire after a set duration.
@@ -59,3 +59,5 @@ Dashcam and TestDriver share the same API and web application back end, which in
 - The TestDriver web dashboard is designed with privacy and security as top priorities.
 - For additional security, ensure your team rotates API keys regularly and reviews team member access permissions.
 - If you have specific security concerns or questions, please contact TestDriver support.
+
+<Tip>See complete docs about the dashboard features [here](/account/dashboard)</Tip>

package/docs/snippets/test-prereqs.mdx

@@ -1,7 +1,7 @@
 ## Prerequisites
 Before running the tests, ensure you have performed the following steps:
 
-1. Install the [VS Code Extension](/getting-started/vscode) for TestDriver
+1. Install the [VS Code extension](/getting-started/vscode) for TestDriver
 2. If you haven't already, signup for a Free Trial on the [TestDriver website](https://testdriver.ai/pricing)
 3. Install the [TestDriver CLI](/cli/overview) globally using npm or just follow the VS Code Extension Setup Walkthrough:
 ```bash

package/docs/snippets/yml-warning.mdx

@@ -0,0 +1 @@
+<Warning>TestDriver v5 uses the `.yaml` file extension for all test files. This is a breaking change from v4 which uses the `.yml` extension!</Warning>

package/docs/tutorials/advanced-test.mdx

@@ -1,11 +1,11 @@
 ---
-title: "Tutorial: Advanced Test"
+title: "Tutorial: Advanced test"
 description: "Explore advanced testing techniques and features in TestDriver."
-sidebarTitle: "Advanced Test"
+sidebarTitle: "Advanced test"
 icon: "flask-round"
 ---
 
-# Advanced Test Tutorial
+# Advanced test tutorial
 
 Welcome to the Advanced Test Tutorial. In this guide, we will explore advanced testing techniques and features available in TestDriver. This tutorial assumes you have a basic understanding of TestDriver and its functionalities.
 
@@ -16,7 +16,7 @@ Before starting, ensure you have completed the basic TestDriver tutorial and hav
 - TestDriver installed and configured.
 - A sample project to test.
 
-## Advanced Features Overview
+## Advanced features overview
 
 TestDriver provides several advanced features to enhance your testing capabilities:
 
@@ -25,9 +25,9 @@ TestDriver provides several advanced features to enhance your testing capabiliti
 3. **Test Hooks**: Use hooks to execute code before or after tests.
 4. **Parallel Execution**: Speed up testing by running tests in parallel.
 
-## Step-by-Step Guide
+## Step-by-step guide
 
-### Step 1: Setting Up Custom Assertions
+### Step 1: Setting up custom assertions
 
 Custom assertions allow you to define specific conditions for your tests. Here's an example:
 
@@ -36,7 +36,7 @@ def assert_custom_condition(value):
     assert value > 0, "Value must be greater than 0"
 ```
 
-### Step 2: Using Parameterized Tests
+### Step 2: Using parameterized tests
 
 Parameterized tests enable you to test multiple scenarios with different inputs. Example:
 
@@ -48,7 +48,7 @@ def test_is_positive(input, expected):
     assert (input > 0) == expected
 ```
 
-### Step 3: Implementing Test Hooks
+### Step 3: Implementing test hooks
 
 Test hooks let you execute code before or after tests. Example:
 
@@ -60,7 +60,7 @@ def teardown_function():
     print("Cleaning up test environment")
 ```
 
-### Step 4: Running Tests in Parallel
+### Step 4: Running tests in parallel
 
 Parallel execution can be achieved using pytest-xdist. Install it with: