Fix typo README.md #4033
Fix typo README.md #4033
Conversation
|
@VitalikBerashvili is attempting to deploy a commit to the OsmoLabs Team on Vercel. A member of the Team first needs to authorize it. |
WalkthroughThe pull request involves a minor documentation update in the Changes
Note: No functional changes were made to the code or documentation structure. 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
packages/bridge/README.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
packages/bridge/README.md
[duplication] ~3-~3: Possible typo: you repeated a word.
Context: ...osis-labs/bridge Provides a single API for for interacting with multiple bridge provid...
(ENGLISH_WORD_REPEAT_RULE)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Summary
| @@ -1,6 +1,6 @@ | |||
| # @osmosis-labs/bridge | |||
|
|
|||
| Provides a single API for for interacting with multiple bridge providers, with a focus on IBC asset info for a single chain. Relies on canonical chain and asset identifiers across ecosystems for identifying assets and chains. Some bridge providers include routing and swap aggregation capabilites. New providers can be added by implementing the `BridgeProvider` interface. The interface includes some optional components that can be used to support alternative bridge features, such as the `getDepositAddress` for briding via a send transaction to a generated deposit address. | |||
| Provides a single API for for interacting with multiple bridge providers, with a focus on IBC asset info for a single chain. Relies on canonical chain and asset identifiers across ecosystems for identifying assets and chains. Some bridge providers include routing and swap aggregation capabilities. New providers can be added by implementing the `BridgeProvider` interface. The interface includes some optional components that can be used to support alternative bridge features, such as the `getDepositAddress` for briding via a send transaction to a generated deposit address. | |||
There was a problem hiding this comment.
Remove repeated word "for".
There is a duplicate word in the sentence: "API for for interacting".
Apply this diff to fix the typo:
-Provides a single API for for interacting with multiple bridge providers
+Provides a single API for interacting with multiple bridge providers📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Provides a single API for for interacting with multiple bridge providers, with a focus on IBC asset info for a single chain. Relies on canonical chain and asset identifiers across ecosystems for identifying assets and chains. Some bridge providers include routing and swap aggregation capabilities. New providers can be added by implementing the `BridgeProvider` interface. The interface includes some optional components that can be used to support alternative bridge features, such as the `getDepositAddress` for briding via a send transaction to a generated deposit address. | |
| Provides a single API for interacting with multiple bridge providers, with a focus on IBC asset info for a single chain. Relies on canonical chain and asset identifiers across ecosystems for identifying assets and chains. Some bridge providers include routing and swap aggregation capabilities. New providers can be added by implementing the `BridgeProvider` interface. The interface includes some optional components that can be used to support alternative bridge features, such as the `getDepositAddress` for briding via a send transaction to a generated deposit address. |
🧰 Tools
🪛 LanguageTool
[duplication] ~3-~3: Possible typo: you repeated a word.
Context: ...osis-labs/bridge Provides a single API for for interacting with multiple bridge provid...
(ENGLISH_WORD_REPEAT_RULE)
Pull Request: Fix Typo in
README.mdSummary
This pull request corrects a typo in the
README.mdfile. The word "for" was repeated and has been removed to improve readability, and the word "capabilites" was corrected to "capabilities."Changes.