doc: fix typos

[Skanislav]

Summary by CodeRabbit

• Documentation
  • Corrected several typographical errors in user-facing documentation and notes, including spelling fixes for "Support" and "components" and improved wording in descriptions and callouts. No changes to functionality or behavior.

[coderabbitai]

Walkthrough

Several typographical errors were corrected in documentation and metadata files across the project. These changes involved fixing misspelled words in GitHub Action metadata, documentation pages, and public notes related to the Ethereum Identity Kit. No functional, logical, or structural code changes were introduced.

Changes

Files/Paths	Change Summary
.github/actions/checks/action.yml	Fixed typo in skip-steps input description ("comma-seperated" → "comma-separated").
pages/docs/index.mdx	Corrected typos: "Supprt" → "Support" and "componentss" → "components".
public/llms/complete/llms-full.txt, public/llms/eik/llms-full.txt	Fixed typo in documentation note: "Supprt" → "Support".

Poem

A hop, a skip, a typo gone,
With every word, we leap along.
"Support" now spelled the proper way,
Our docs are brighter, come what may!
🐇✨

The rabbit cheers, the errors flee—
Polished prose for all to see!

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[vercel]

@Skanislav is attempting to deploy a commit to the EFP Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.github/actions/checks/action.yml (1)

6-6: Clarify wording for better readability

“Format is comma-separated steps to skip” reads awkwardly. Consider re-phrasing to something like:

-    description: "Format is comma-separated steps to skip. Example: 'build,typecheck'"
+    description: "Comma-separated list of steps to skip (e.g. 'build,typecheck')."

pages/docs/index.mdx (1)

55-55: Minor grammar polish

Add a definite article and tighten the sentence:

-If you are using `dark` className prop to handle dark mode, components will automatically adapt to the color scheme of your application.
+If you are using the `dark` className prop to handle dark mode, components will automatically adapt to your application's color scheme.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e7fc438 and 5f82c0f.

📒 Files selected for processing (4)

• .github/actions/checks/action.yml (1 hunks)
• pages/docs/index.mdx (2 hunks)
• public/llms/complete/llms-full.txt (1 hunks)
• public/llms/eik/llms-full.txt (1 hunks)

🧰 Additional context used

🪛 LanguageTool

pages/docs/index.mdx

[grammar] ~55-~55: Use articles correctly.
Context: ...ereum-identity-kit/css' ``` If you are using dark className prop to handle dark mo...

(QB_NEW_EN_OTHER_ERROR_IDS_000004)

---

[grammar] ~55-~55: Use proper spacing conventions.
Context: ...to the color scheme of your application. ### You're all set! Library is typed with T...

(QB_NEW_EN_OTHER_ERROR_IDS_000007)

🔇 Additional comments (3)

public/llms/complete/llms-full.txt (1)

10036-10036: Typo fix looks good—“Support” spells it out clearly.
No additional issues spotted.

public/llms/eik/llms-full.txt (1)

930-930: Typo fix looks good – “Support” is now spelled correctly.

pages/docs/index.mdx (1)

8-8: Typo fix looks good
The “Support” correction improves clarity without altering meaning.