docs: @marko/tree-sitter name + writing guidelines

[DylanPiercey]

• README now references the published package name @marko/tree-sitter instead of the old tree-sitter-marko (the npm install/require example pointed at the wrong package). The tree-sitter-marko.wasm filename is kept — that's the conventional tree-sitter-<lang>.wasm grammar-wasm name, not the package.
• Apply the marko-js docs writing guidelines: remove all emdashes, drop second-person voice, and replace the **Bold**: description list in "Tag types" with prose.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7984ff47-dc4c-43ce-a226-af3d929dba08

📥 Commits

Reviewing files that changed from the base of the PR and between 6f268a7 and fb1b46c.

📒 Files selected for processing (1)

• README.md

---

Walkthrough

This PR updates README.md to reflect the package rename from tree-sitter-marko to @marko/tree-sitter, affecting the top-level heading and Node.js usage example. The documentation for editor integrations (tree-sitter CLI, Helix, Zed) is reformatted and expanded with clarification on grammar discovery mechanisms. Grammar reference sections covering structural notes, tag types, embedded language injection, and fidelity notes are rewritten for improved clarity and organization.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly summarizes the main changes: updating documentation to use the correct @marko/tree-sitter package name and applying writing guidelines.
Description check	✅ Passed	The description clearly explains the rationale behind the changes, including the package name correction and the writing guidelines being applied.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/package-name-and-style

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}