Merge pull request #68 from woocommerce/docs/minor-fixes

Minor docs fixes (capitalization and phrasing)

Author: zhongruige

docs/intro.md

@@ -14,7 +14,7 @@ QIT (Quality Insights Toolkit) is a testing platform developed by WooCommerce fo
 **Key Features:**
 - **Managed test suites:** Run pre-configured end-to-end tests, activation tests, security scans, PHPStan analysis, API tests, and more.
 - **Custom E2E testing:** Write and run your own Playwright-based E2E tests directly through QIT.
-- **Continuous quality checks:** Easily integrate QIT with your development workflows (CLI, GitHub Actions, etc.).
+- **Continuous quality checks: Seamlessly integrate QIT into your development workflows via CLI, GitHub Actions, and more.
 - **Marketplace integration:** Currently in closed beta for extensions listed on the WooCommerce Marketplace.
 
 <video controls style={{ width:"100%", height:"100%" }}>
@@ -24,7 +24,7 @@ QIT (Quality Insights Toolkit) is a testing platform developed by WooCommerce fo
 
 ## Requirements
 
-- **Woocommerce.com partner developer account:** You must have at least one extension listed on the WooCommerce.com Marketplace to access QIT.
+- **WooCommerce.com partner developer account:** You must have at least one extension listed on the WooCommerce.com Marketplace to access QIT.
 - **PHP 7.2.5+ and composer:** Required if you plan to use QIT locally via the CLI.
 
 ## Quick start guide
@@ -86,7 +86,7 @@ While full QIT access is currently exclusive to WooCommerce.com Partner Develope
 ## Ways to use QIT
 
 - **Command line (CLI):** Perfect for integrating into your local development workflow or CI pipelines. See [CLI Getting Started](./installation-setup/cli-installation.md).
-- **Woocommerce.com dashboard:** Run and view tests directly in the vendor dashboard UI. See [Getting Started with Dashboard](./using-qit/running-tests-dashboard.md).
+- **WooCommerce.com dashboard:** Run and view tests directly in the vendor dashboard UI. See [Getting Started with Dashboard](./using-qit/running-tests-dashboard.md).
 - **GitHub actions:** Integrate QIT tests into your GitHub workflows. See [GitHub Workflows Setup](./using-qit/github-workflows.md).
 
 :::info  

docs/managed-tests/plugin-check.md

@@ -1,6 +1,6 @@
-# wordpress.org Plugin Check tests
+# WordPress.org Plugin Check tests
 
-wordpress.org Plugin Check tests run the [wordpress.org automated plugin check](https://wordpress.org/plugins/plugin-check) tool against your extension. This optional test focuses on guidelines and patterns important for submitting plugins to the WordPress.org directory.
+WordPress.org Plugin Check tests run the [WordPress.org automated plugin check](https://wordpress.org/plugins/plugin-check) tool against your extension. This optional test focuses on guidelines and patterns important for submitting plugins to the WordPress.org directory.
 
 **Note:** Currently, these checks are not automatically triggered for WooCommerce Marketplace submissions. They are available for developers who also distribute on wordpress.org or wish to maintain broader WordPress best-practices.
 
@@ -9,13 +9,13 @@ wordpress.org Plugin Check tests run the [wordpress.org automated plugin check](
 The tool currently runs checks from the `plugin_repo` category, which helps identify violations of the [WordPress.org Plugin Review Guidelines](https://make.wordpress.org/plugins/handbook/performing-reviews/review-checklist/). These may include:
 
 - **Core guideline compliance:** Detects code that violates mandatory directory rules.
-- **Repository readiness:** Flags improper file structures, disallowed functions, or patterns that could prevent listing on wordpress.org.
+- **Repository readiness:** Flags improper file structures, disallowed functions, or patterns that could prevent listing on WordPress.org.
 - **General code health:** May highlight deprecated functions, insecure code usage, or general best-practice concerns.
 
 ## Interpreting results
 
 - **Success:** No major issues detected.
-- **Warnings/Failures:** Potential guideline violations or best-practice deviations are highlighted. While not necessarily blocking for WooCommerce Marketplace, they could impact your plugin’s acceptability on wordpress.org.
+- **Warnings/Failures:** Potential guideline violations or best-practice deviations are highlighted. While not necessarily blocking for WooCommerce Marketplace, they could impact your plugin’s acceptability on WordPress.org.
 
 ## Next steps if it fails
 

docs/support/faqs.md

@@ -11,7 +11,7 @@ A: Full QIT functionality, including managed tests and cloud runs, requires a Wo
 ## Installation and setup
 
 **Q: How do I install the QIT CLI?**  
-Please refer to the [CLI Installation](../installation-setup/cli-installation.md) page for instrutions on installing the QIT CLI.
+Please refer to the [CLI Installation](../installation-setup/cli-installation.md) page for instructions on installing the QIT CLI.
 
 **Q: What are the prerequisites for running tests locally?**  
 Please check the [Local Test Environment Introduction](../environment/introduction.md) for more details.

docs/test-execution/useful-commands.md

@@ -55,8 +55,8 @@ Displays info such as:
 ```
 Run Id              344745
 Test Type           security
-Wordpress Version   6.1.1
-Woocommerce Version 7.2.2
+WordPress Version   6.1.1
+WooCommerce Version 7.2.2
 Status              warning
 Is Development      Yes
 Woo Extension       My Extension

docs/using-qit/running-tests-dashboard.md

@@ -4,7 +4,7 @@ If you prefer a user interface (UI) over the command line, the WooCommerce Vendo
 
 ## Prerequisites
 
-- **Woocommerce.com partner developer account:** Ensure you are logged in with the vendor account associated with your extension.
+- **WooCommerce.com partner developer account:** Ensure you are logged in with the vendor account associated with your extension.
 - **Extension listed on the WooCommerce marketplace:** The dashboard features are only available for extensions listed on WooCommerce.com.
 
 ## Accessing the vendor dashboard

src/components/TestTypes.js

@@ -24,7 +24,7 @@ export default function TestTypes({ includeCode = false }) {
                         style={{ display: includeCode ? 'inline-block' : 'none' }}>run:malware</code></li>
                     <li><a href="/docs/managed-tests/validation">Validation tests</a> <code
                         style={{ display: includeCode ? 'inline-block' : 'none' }}>run:validation</code></li>
-                    <li><a href="/docs/managed-tests/plugin-check">wordpress.org Plugin Check tests</a> <code
+                    <li><a href="/docs/managed-tests/plugin-check">WordPress.org Plugin Check tests</a> <code
                         style={{ display: includeCode ? 'inline-block' : 'none' }}>run:plugin-check</code></li>
                     <li>Performance tests <i>(Coming soon)</i></li>
                 </ul>