Fix Typographical Errors in Documentation and Comments

[kilavvy]

Description:
This pull request corrects minor typographical errors in the codebase. Specifically, it updates the spelling of "example" and "transferred" in documentation and comments within the following files:

• packages/thirdweb/src/extensions/erc721/drops/write/claimToBatch.ts
• packages/thirdweb/src/extensions/unstoppable-domains/read/resolveName.ts

These changes improve the clarity and professionalism of the code documentation and comments. No functional code changes are included.

---

PR-Codex overview

This PR focuses on correcting typos in comments within the codebase, enhancing clarity and readability.

Detailed summary

• In claimToBatch.ts, corrected "exampple" to "example".
• In resolveName.ts, corrected "transfered" to "transferred".

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

Summary by CodeRabbit

• Documentation
  • Fixed minor typos in code comments to improve clarity. No changes to functionality or user experience.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 479ec4c

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

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merge-queue - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[coderabbitai]

Walkthrough

This update corrects typographical errors in comments within two source files. The changes involve fixing misspelled words in documentation comments, with no modifications to the logic, functionality, or exported interfaces of the codebase.

Changes

File(s)	Change Summary
.../erc721/drops/write/claimToBatch.ts	Fixed typo in a documentation comment ("exampple" → "example").
.../unstoppable-domains/read/resolveName.ts	Fixed typo in a documentation comment ("transfered" → "transferred").

Possibly related PRs

• Fix typos in comments and test descriptions #7323: Corrects typos in comments and documentation, similar to this PR.
• docs: fix typos in doc string #7301: Fixes typographical errors in comments or docstrings only.
• chore: fix typos #7180: Addresses typos in comments and identifiers without code logic changes.

Suggested labels

packages

---

📜 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 5f57300 and 479ec4c.

📒 Files selected for processing (2)

• packages/thirdweb/src/extensions/erc721/drops/write/claimToBatch.ts (1 hunks)
• packages/thirdweb/src/extensions/unstoppable-domains/read/resolveName.ts (1 hunks)

🔇 Additional comments (2)

packages/thirdweb/src/extensions/unstoppable-domains/read/resolveName.ts (1)

62-62: Typo fixed: corrected “transfered” to “transferred”.

The comment now uses the correct spelling, improving documentation clarity.

packages/thirdweb/src/extensions/erc721/drops/write/claimToBatch.ts (1)

104-104: Typo fixed: corrected “exampple” to “example”.

The documentation comment now reads correctly, enhancing readability.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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]

@kilavvy is attempting to deploy a commit to the thirdweb Team on Vercel.

A member of the Team first needs to authorize it.