docs: Correct thirdweb capitalization and updating links. #1130
Conversation
Updating to proper capitalization. Updating link.
Updating thirdweb capitals as well as links.
Updating thirdweb capitalization and UTM links.
Updating number of chains supported.
✅ Deploy Preview for docs-optimism ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
📝 Walkthrough📝 WalkthroughWalkthroughThe pull request introduces several updates to the documentation files related to account abstraction and associated tools. Key changes include the renaming of "ThirdWeb" to "thirdweb" across multiple documents, ensuring consistent capitalization. URLs for thirdweb have been updated to new links that include tracking parameters, enhancing the ability to monitor user engagement. The "account-abstraction.mdx" file has been reorganized into distinct sections, providing clearer information about account abstraction, bundlers, the Superchain paymaster, and a list of relevant tools. Additionally, the inclusion criteria for developers wishing to feature their products have been specified. In the "faucets.mdx" file, links for the Thirdweb Sepolia Faucet and the Thirdweb OP Sepolia Faucet have been updated to new URLs with tracking parameters. The "nft-tools.mdx" file reflects an increase in the multi-chain support value for thirdweb from "1100+" to "2500+", along with updated URLs. Overall, these changes aim to improve the clarity and accessibility of the documentation. Possibly related PRs
Suggested labels
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
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
pages/builders/tools/build/account-abstraction.mdx (1)
55-57: Improve grammar and formatting in the thirdweb descriptionThe content requires minor grammatical and formatting improvements while maintaining the correct lowercase spelling of "thirdweb".
Apply these changes:
-* [thirdweb](https://portal.thirdweb.com/react/v5/account-abstraction/get-started?utm_source=opdocs&utm_medium=docs): - offers the complete tool-kit to leverage account abstraction technology to enable seamless user experiences for your users. This includes Account Factory contracts that lets your users spin up Smart Accounts, Bundler for UserOps support, and Paymaster to enable gas sponsorships. +* [thirdweb](https://portal.thirdweb.com/react/v5/account-abstraction/get-started?utm_source=opdocs&utm_medium=docs): + offers the complete toolkit to leverage account abstraction technology to enable seamless user experiences for your users. This includes Account Factory contracts that let your users spin up Smart Accounts, Bundler for UserOps support, and Paymaster to enable gas sponsorships.🧰 Tools
🪛 LanguageTool
[grammar] ~56-~56: Possible subject-verb agreement error detected.
Context: ...includes Account Factory contracts that lets your users spin up Smart Accounts, Bund...(PLURAL_THAT_AGREEMENT)
pages/builders/tools/build/nft-tools.mdx (1)
37-37: Fix table formattingThe table fence is misaligned, which may cause rendering issues in some Markdown processors.
Apply proper table column alignment by ensuring consistent spacing in the table row:
-| Multi-chain | 3 | 5 | 6 | 11 | 2500+ [(all EVM chains)](https://thirdweb.com/dashboard/infrastructure/rpc-edge?utm_source=opdocs&utm_medium=docs) | 9 | +| Multi-chain | 3 | 5 | 6 | 11 | 2500+ [(all EVM chains)](https://thirdweb.com/dashboard/infrastructure/rpc-edge?utm_source=opdocs&utm_medium=docs) | 9 |🧰 Tools
🪛 GitHub Check: lint
[warning] 37-37:
Misaligned table fence
[warning] 37-37:
Misaligned table fence
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (3)
pages/builders/tools/build/account-abstraction.mdx(1 hunks)pages/builders/tools/build/faucets.mdx(1 hunks)pages/builders/tools/build/nft-tools.mdx(2 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
pages/builders/tools/build/account-abstraction.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.
"
pages/builders/tools/build/faucets.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.
"
pages/builders/tools/build/nft-tools.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.
"
🪛 GitHub Check: lint
pages/builders/tools/build/faucets.mdx
[warning] 42-42:
Misaligned table fence
[warning] 42-42:
Misaligned table fence
[warning] 43-43:
Cell should be padded with 1 space, not 12
[warning] 43-43:
Misaligned table fence
[warning] 43-43:
Misaligned table fence
pages/builders/tools/build/nft-tools.mdx
[warning] 37-37:
Misaligned table fence
[warning] 37-37:
Misaligned table fence
🔇 Additional comments (2)
pages/builders/tools/build/nft-tools.mdx (2)
26-26: LGTM: Correct capitalization and URL update
The changes correctly implement the lowercase "thirdweb" branding and add appropriate tracking parameters to the URL.
37-37: LGTM: Updated statistics and URL
The changes accurately reflect the increased multi-chain support (2500+) and maintain consistent URL tracking parameters.
🧰 Tools
🪛 GitHub Check: lint
[warning] 37-37:
Misaligned table fence
[warning] 37-37:
Misaligned table fence
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (2)
pages/builders/tools/build/faucets.mdx(1 hunks)pages/builders/tools/build/nft-tools.mdx(2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- pages/builders/tools/build/faucets.mdx
🧰 Additional context used
📓 Path-based instructions (1)
pages/builders/tools/build/nft-tools.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 (3)
pages/builders/tools/build/nft-tools.mdx (3)
26-26: LGTM: Correct capitalization and URL format
The capitalization of "thirdweb" matches the official branding, and the URL structure with tracking parameters is consistent with documentation standards.
49-49: LGTM: Consistent URL structure
The Moralis documentation URL update follows the consistent pattern of adding tracking parameters for external links.
37-37: Verify the significant increase in multi-chain support
The multi-chain support number has increased significantly from 1100+ to 2500+. While the link provides context, it would be good to verify this substantial change.
✅ Verification successful
Multi-chain support increase from 1100+ to 2500+ chains is confirmed
The git history shows the previous value was indeed 1100+ EVM chains, and it has been updated to 2500+ chains. The change is properly documented with an updated reference link to thirdweb's infrastructure dashboard.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Search for any previous mentions of multi-chain support numbers
rg -i "multi.?chain.*(\d+)" --type mdx
Length of output: 68
Script:
#!/bin/bash
# Search for any previous mentions of chain numbers in markdown files
rg -i "(\d+)\+.*(?:chain|evm)" --type md
rg -i "chain.*(\d+)\+" --type md
# Also check for any mentions in the git history of the specific file
git log -p -- pages/builders/tools/build/nft-tools.mdx | rg -i "(\d+)\+.*(?:chain|evm)"
Length of output: 2990
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
pages/builders/tools/build/nft-tools.mdx (1)
44-44: Fix grammatical number agreement in pricing fieldThe text "NFT Checkouts free for seller (Unlimited transactions)" has a number agreement issue between the singular "seller" and the plural context.
Apply this change:
-NFT Checkouts free for seller (Unlimited transactions) +NFT Checkouts free for sellers (Unlimited transactions)🧰 Tools
🪛 LanguageTool
[uncategorized] ~44-~44: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...paign=optimism). NFT Checkouts free for seller (Unlimited transactions). | | Image Hos...(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
pages/builders/tools/build/nft-tools.mdx(2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
pages/builders/tools/build/nft-tools.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.
"
🪛 LanguageTool
pages/builders/tools/build/nft-tools.mdx
[uncategorized] ~44-~44: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...paign=optimism). NFT Checkouts free for seller (Unlimited transactions). | | Image Hos...
(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)
🔇 Additional comments (3)
pages/builders/tools/build/nft-tools.mdx (3)
26-26: LGTM: URL update with tracking parameters
The URL update for thirdweb is consistent with the tracking parameter format used across the documentation.
49-49: LGTM: Moralis API URL update
The Moralis API URL update with tracking parameters is consistent with the documentation standards.
37-37: Verify the significant increase in multi-chain support
The multi-chain support number for thirdweb has increased significantly from 1100+ to 2500+. Let's verify this claim.
Description
The goal of this PR is to update the capitalization of instances of
thirdwebalong with providing updated links.