docs/block-development/cart-and-checkout-blocks/how-to-additional-checkout-fields-guide.md (2)

75-75: Ensure blank lines around fenced code blocks.

Add a blank line before and after each code fence to satisfy markdownlint MD031.

-Example:
```php
+Example:
+
+```php
...
-```
+```
+

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 markdownlint-cli2 (0.17.2)</summary>

75-75: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)

</details>
<details>
<summary>🪛 GitHub Actions: CI</summary>

[error] 75-75: markdownlint MD031/blanks-around-fences: Fenced code blocks should be surrounded by blank lines

</details>

</details>

---

`80-80`: **Refine preposition for clarity.**

Change “saved to both the customer and the order” to “saved for both the customer and the order” for grammatical correctness.


```diff
-These fields are saved to both the customer and the order
+These fields are saved for both the customer and the order

🧰 Tools

🪛 LanguageTool

[uncategorized] ~80-~80: The preposition “for” seems more likely in this position than the preposition “to”.
Context: ...nd billing address forms. They’re saved to both the customer and the order, so ret...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_TO_FOR)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md (1)

7-7: Fix the broken link to the additional fields guide
The URL has an extra slash and the slug is missing “checkout.” Update it to:

- If you've already learned how to [add additional fields to the WooCommerce Checkout Block](https://developer.woocommerce.com//docs/block-development/cart-and-checkout-blocks/how-to-add-additional-fields-guide),
+ If you've already learned how to [add additional fields to the WooCommerce Checkout Block](https://developer.woocommerce.com/docs/block-development/cart-and-checkout-blocks/how-to-additional-checkout-fields-guide),

docs/block-development/cart-and-checkout-blocks/how-to-additional-checkout-fields-guide.md (1)

62-62: Replace “to” with “for” in the description
Change the preposition for better clarity and accuracy in “saved to both the customer and the order.”

- They’re saved to both the customer and the order, so returning customers won’t need to refill them.
+ They’re saved for both the customer and the order, so returning customers won’t need to refill them.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~62-~62: The preposition “for” seems more likely in this position than the preposition “to”.
Context: ...nd billing address forms. They’re saved to both the customer and the order, so ret...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_TO_FOR)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

docs/block-development/cart-and-checkout-blocks/how-to-additional-checkout-fields-guide.md (2)

78-79: Verify image path resolution.

---

97-98: Verify image path resolution.

docs/block-development/cart-and-checkout-blocks/how-to-additional-checkout-fields-guide.md (4)

1-4: Align frontmatter title with page heading.
The post_title in the frontmatter ("How to Add Additional Fields") doesn’t match the H1 ("How to Add Additional Fields to the WooCommerce Checkout Block"). For consistency, update the frontmatter to reflect the full title.

-post_title: How to Add Additional Fields
+post_title: How to Add Additional Fields to the WooCommerce Checkout Block
-sidebar_label: How to add additional fields in checkout
+sidebar_label: How to Add Additional Fields in Checkout

---

8-12: Use consistent terminology in intro.
Replace "In this post" with "In this guide" to match the document scope, and consider refining "head to" to "refer to" for tone consistency:

-In this post, we’ll walk through the process of adding your own additional fields to your checkout form and show you practical examples you can implement right away.
+In this guide, we’ll walk through the process of adding your own additional fields to your checkout form and show you practical examples you can implement right away.

-For a deeper dive on the fields and helper methods referenced in this guide, please head to the [Additional Checkout Fields](https://developer.woocommerce.com/docs/block-development/cart-and-checkout-blocks/additional-checkout-fields) documentation.
+For a deeper dive on the fields and helper methods referenced in this guide, please refer to the [Additional Checkout Fields](https://developer.woocommerce.com/docs/block-development/cart-and-checkout-blocks/additional-checkout-fields) documentation.

---

61-64: Clarify and adjust grammar in Address description.
Consider updating to specify that fields are saved to the customer's account and to the order, and using "for" instead of "to":

-These fields appear in both the shipping and billing address forms. They’re saved to both the customer and the order, so returning customers won’t need to refill them.
+These fields appear in both the shipping and billing address forms. They’re saved for both the customer’s account and the order, so returning customers won’t need to refill them.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~63-~63: The preposition “for” seems more likely in this position than the preposition “to”.
Context: ...nd billing address forms. They’re saved to both the customer and the order, so ret...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_TO_FOR)

---

191-193: Link to companion guide.
Since there's a "How to Make Additional Fields Conditional" guide in this PR, add a link for discoverability:

-Now that you've learned how to add additional fields to the WooCommerce Checkout Block, consider exploring more advanced features such as conditional field visibility, dynamic field values, and integrating with third-party services.
+Now that you've learned how to add additional fields to the WooCommerce Checkout Block, consider exploring more advanced features such as conditional field visibility (see [How to Make Additional Fields Conditional](./how-to-conditional-additional-fields.md)), dynamic field values, and integrating with third-party services.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md (1)

9-9: Fix broken link to the additional fields guide
This URL has a double slash and the wrong slug—also noted in a previous review.

- If you've already learned how to [add additional fields to the WooCommerce Checkout Block](https://developer.woocommerce.com//docs/block-development/cart-and-checkout-blocks/how-to-add-additional-fields-guide),
+ If you've already learned how to [add additional fields to the WooCommerce Checkout Block](./how-to-additional-checkout-fields-guide.md),

docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md (3)

1-4: Allow fenced code blocks to satisfy linting without rewriting examples
CI is failing MD046 (code-block-style) for all fenced PHP examples. Rather than convert dozens of snippets, disable the rule for this file by adding a markdownlint directive after the frontmatter.

--- a/docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md
+++ b/docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md
@@
 ---
+<!-- markdownlint-disable MD046 -->

---

347-348: Insert blank line before heading
MD022 is reporting "Headings should be surrounded by blank lines" for "## Available data for conditions".

--- a/docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md
+++ b/docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md
@@
-## Available data for conditions
+ 
+## Available data for conditions

---

365-365: Remove extraneous trailing marker
The closing --- at the end of the file is not needed and may be confusing.

--- a/docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md
- ---

docs/block-development/cart-and-checkout-blocks/how-to-additional-checkout-fields-guide.md (1)

171-171: Grammar: add missing article for clarity
Include "a" to improve the phrasing around user experience.

- You can enhance your fields with HTML attributes for better user experience:
+ You can enhance your fields with HTML attributes for a better user experience:

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

docs/block-development/cart-and-checkout-blocks/how-to-additional-checkout-fields-guide.md (2)

67-67: Suggest preposition adjustment
Change “saved to both the customer and the order” to “saved for both the customer and the order” for clearer phrasing.

---

171-171: Add missing article
Modify “for better user experience” to “for a better user experience” to include the necessary article.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md (1)

15-19: Fix list indentation
The indented asterisks render as code blocks instead of list items. Remove leading spaces so they render correctly as a bulleted list.

docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md (5)

1-4: Align frontmatter title with page heading
The post_title (“How to Add Conditional Additional Checkout Fields”) and the H1 (“How to Make Your WooCommerce Additional Checkout Fields Conditionally Visible in the Checkout Block”) don’t match exactly. Consider unifying them for consistency.

---

1-9: Add cross-link to the basic additional fields guide
To help readers follow the progressive path, include a link at the top referencing the “How to Add Additional Checkout Fields” guide (e.g. a relative link to how-to-additional-checkout-fields-guide.md).

---

7-7: Use an info/admonition block for version requirement
Highlight the WooCommerce 9.9.0 requirement in an admonition (e.g., :::note) instead of plain text to improve visibility.

---

195-207: Correct array indentation and bracket alignment
The closing bracket for the 'required' block is misaligned, which makes the PHP example harder to read. Align the ], under the 'required' key for consistency.

---

346-346: Add blank line before heading
Ensure the “## Available data for conditions” heading has a blank line above it to comply with markdown style guidelines.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

docs/block-development/cart-and-checkout-blocks/how-to-conditional-additional-fields.md (2)

27-34: Correct the JSON Schema snippet comments.

The comment under the required key wrongly says “Define when to hide here” — it should clarify that this block defines when the field is required.

Apply this diff:

@@ 28,29c28,29
-    // Define when to hide here
+    // Define when the field is required
@@ 31,32c31,32
-    // Define when to hide here
+    // Define when the field is hidden

---

7-10: Add a cross-reference to the foundational guide.

This document builds on the “How to Add Additional Checkout Fields” guide but doesn’t link to it. Adding a relative link at the top helps readers follow the progression.

Example:

@@ 9,10c9,12
-Conditional visibility allows you to create smart, adaptive checkout forms that only show relevant fields when needed, reducing form clutter and improving the customer experience.
+If you haven’t yet registered additional checkout fields, see [How to Add Additional Checkout Fields](./how-to-additional-checkout-fields-guide.md) first.
+
+Conditional visibility allows you to create smart, adaptive checkout forms that only show relevant fields when needed, reducing form clutter and improving the customer experience.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro