Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos and improve consistency across documentation files #2408

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Dimitrolito
Copy link

@Dimitrolito Dimitrolito commented Nov 24, 2024

This pull request addresses several typos and consistency issues in various documentation files across the repo. The following changes have been made:

  • Corrected typos such as "an fid" to "a fid" and "an fname" to "a fname" to ensure correct usage of indefinite articles.
  • Fixed the use of "A" vs "An" before words starting with consonant and vowel sounds where necessary.
  • Updated descriptions and fixed formatting for clarity and consistency.

Why is this change needed?

This change is needed to maintain consistency and clarity in the documentation, making it easier to understand and follow. It also ensures that all references to terms like "fid" and "fname" are grammatically correct.

Merge Checklist:


PR-Codex overview

This PR primarily focuses on minor textual corrections and improvements in documentation related to the ViemLocalEip712Signer, IdRegistryEvent, and NameRegistryEvent in the Farcaster protocol.

Detailed summary

  • Corrected spelling of LocalAсcount in ViemLocalEip712Signer.md.
  • Removed redundant wording in README.md files and ensured consistency.
  • Clarified descriptions in Events.md for IdRegistryEvent and NameRegistryEvent.
  • Improved formatting of event types in Events.md.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Copy link

changeset-bot bot commented Nov 24, 2024

⚠️ No Changeset found

Latest commit: 300b0fd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Nov 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
hub-monorepo ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 24, 2024 3:26pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant