-
Notifications
You must be signed in to change notification settings - Fork 207
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
Update rpc-providers.mdx #1052
Update rpc-providers.mdx #1052
Conversation
Added Blockdaemon to the RPC & Node providers list.
✅ Deploy Preview for docs-optimism ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Caution Review failedThe pull request is closed. WalkthroughThe pull request introduces a new section for "Blockdaemon" in the "RPC & Node providers" guide within the Changes
Possibly related issues
Possibly related PRs
Suggested reviewers
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
Documentation and Community
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
pages/builders/tools/connect/rpc-providers.mdx (2)
43-45
: Consider using more neutral language in the description.The current description contains marketing-heavy language. Consider revising to:
-Blockdaemon provides institutional-grade blockchain infrastructure, including node, staking, and API solutions, with premium RPC services optimized for [Optimism](https://docs.blockdaemon.com/reference/how-to-access-optimism-api). With free and enhanced options, Blockdaemon's RPC API allows developers to securely interact with on-chain data, broadcast transactions, and build dApps with minimal setup, offering streamlined access to enriched blockchain data and 99.9% uptime reliability to meet diverse needs. +Blockdaemon provides blockchain infrastructure services, including node operations, staking, and API solutions, with RPC services for [Optimism](https://docs.blockdaemon.com/reference/how-to-access-optimism-api). The service offers both free and enhanced tiers, enabling developers to interact with on-chain data, broadcast transactions, and build dApps. Features include enriched blockchain data access and a guaranteed uptime SLA of 99.9%.
47-47
: Standardize the sign-up link format.For consistency with other provider sections (e.g., Infura), consider revising to:
-[Sign up for a free Blockdaemon account here](https://app.blockdaemon.com/signin/register) +[Sign up for a free Blockdaemon account](https://app.blockdaemon.com/signin/register)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
pages/builders/tools/connect/rpc-providers.mdx
(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
pages/builders/tools/connect/rpc-providers.mdx (1)
Pattern **/*.mdx
: "ALWAYS review Markdown content THOROUGHLY with the following criteria:
- Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
- Avoid gender-specific language and use the imperative form.
- Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
- Ensure proper nouns are capitalized in sentences.
- Apply the Oxford comma.
- Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
- Use correct spelling and grammar at all times (IMPORTANT).
- For H1, H2, and H3 headers:
- Use sentence case, capitalizing only the first word.
- Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
- Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
- Flag any headers that seem to inconsistently apply these rules for manual review.
- When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
"
🔇 Additional comments (2)
pages/builders/tools/connect/rpc-providers.mdx (2)
41-42
: LGTM!
The section header follows proper capitalization rules for proper nouns.
49-51
: LGTM!
The supported networks section follows the established format consistently.
Description
Added Blockdaemon to the RPC & Node providers list.
Tests
Additional context
Metadata