fix: typos in documentation files

[leopardracer]

This pull request contains changes to improve clarity, correctness and structure.

Summary by CodeRabbit

• Refactor
  • Updated the fee recommendation interface for improved consistency.
• Documentation
  • Corrected a typographical error to enhance clarity in internal comments.

[vercel]

@leopardracer is attempting to deploy a commit to the distributed-crafts Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The pull request updates a type name in the mempool module by renaming MempoolRecomendedFee to MempoolRecommendedFee and adjusts its usage in type declarations, method return types, and internal calls within the MempoolClient class. Additionally, a typographical error in a comment within the wallet UTXO module has been corrected to improve documentation clarity.

Changes

File	Change Summary
sdk/src/mempool.ts	Renamed type from MempoolRecomendedFee to MempoolRecommendedFee and updated its usage in declarations, method returns, and the getJson call.
sdk/src/wallet/utxo.ts	Fixed a typo in the comment of getInputFromUtxoAndTx, correcting "containts" to "contains".

Poem

I'm a bouncing bunny in the code,
Fixing typos on every road.
Types renamed with a gentle hop,
Comments now clear, neat, and on top.
Hoppy fixes make our modules glow! 🐇

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

sdk/src/mempool.ts (1)

5-15: Minor suggestion: Consider updating API naming in comments

The comments refer to "Memopool API" but the constants are named "MEMPOOL_BASE_PATH". Consider updating the comments to consistently use "Mempool" instead of "Memopool" for better alignment with the code.

- * Base path for the mainnet Memopool API.
+ * Base path for the mainnet Mempool API.
...
- * Base path for the testnet Memopool API.
+ * Base path for the testnet Mempool API.
...
- * Base path for the regtest Memopool API.
+ * Base path for the regtest Mempool API.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4ffe160 and bae76da.

📒 Files selected for processing (2)

• sdk/src/mempool.ts (3 hunks)
• sdk/src/wallet/utxo.ts (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• sdk/src/wallet/utxo.ts

🔇 Additional comments (4)

sdk/src/mempool.ts (4)

20-20: Excellent typographical correction!

You've appropriately fixed the spelling error in the type name, changing MempoolRecomendedFee to MempoolRecommendedFee. This kind of attention to detail improves code quality and readability.

---

79-79: Good documentation update!

You've correctly updated the JSDoc return type annotation to use the fixed type name. Maintaining consistency between code and documentation is important.

---

88-88: Return type properly corrected!

The method return type has been consistently updated to use the corrected type name.

---

89-89: Type parameter correctly updated!

You've systematically updated the generic type parameter in the method call to match the renamed type.