docs: Fix typo on learn/kiichain/vision-of-kiichain.md

[ejabae11122]

Description

Fix Typo on learn/kiichain/vision-of-kiichain.md

Type of change

• Documentation (updates documentation on the project)

How Has This Been Tested?

• Haven been checked the learn/kiichain/vision-of-kiichain.md

[coderabbitai]

Walkthrough

• In learn/kiichain/vision-of-kiichain.md, the opening sentence was reformatted to use an em dash (—) instead of a hyphen.
• A stray backslash line at the end of the section was removed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title clearly states that a documentation typo was fixed in the specified file, directly reflecting the main change in the pull request without introducing unrelated information.
Description Check	✅ Passed	The pull request description specifies that a typo was fixed in the relevant markdown file and categorizes the change as documentation, which aligns with the actual modifications.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6826f89 and c7fedf7.

📒 Files selected for processing (1)

• learn/kiichain/vision-of-kiichain.md (1 hunks)

🔇 Additional comments (1)

learn/kiichain/vision-of-kiichain.md (1)

11-11: Typo fix looks good.

The em dash substitution reads smoothly and aligns with standard typography in the doc.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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