docs: fix broken anchor links in low-level form guide

[Jacky-J126]

All Submissions:

• Have you followed the guidelines stated in CONTRIBUTING.md file?
• Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change

• Bug fix (non-breaking change which fixes an issue)

Description

In docs/library/forms/form-ll.md, the Form Message paragraph links "client side validation" and "server side validation" to #client-side-validation and #server-side-validation, but this page has no such headings, so both anchors are dead.

This PR points both links to the existing ## Validation section instead.

Verification

• Checked every #anchor link on the page against its headings using both GitHub's anchor rules and the reflex.dev docs slug rules: 2 broken links before the change, 0 after.
• codespell and ruff format --check pass on the modified file.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[greptile-apps]

Greptile Summary

Updates the low-level form guide to repair its validation links and clarify how form validation works.

• Adds dedicated client-side and server-side validation headings.
• Corrects the force_match prop attribution from Form Control to Form Message.
• Clarifies the roles of type, match, and as_child.

Confidence Score: 5/5

The documentation-only change appears safe to merge and leaves no actionable findings.

The added headings resolve the broken anchors, and the accompanying wording corrections accurately describe the documented validation props and behavior.

Important Files Changed

Filename	Overview
docs/library/forms/form-ll.md	Repairs validation anchors and improves the accuracy and organization of the form-validation documentation.

_{Reviews (2): Last reviewed commit: "docs: clarify low-level form validation ..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 32 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing Jacky-J126:docs/fix-broken-anchor-links (8506ada) with main (c49a85d)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩