Fix typos #747
Fix typos #747
Conversation
They're not actually directly executable, so remove the bit.
WalkthroughThis update consists of minor corrections to typographical errors, formatting, and capitalization across multiple documentation and blog files. No code, logic, or control flow changes were made; all modifications are limited to textual improvements for clarity, accuracy, and readability. Changes
Possibly related PRs
Suggested reviewers
Poem
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
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: 0
🧹 Nitpick comments (3)
website/blog/new-ver-38.md (1)
37-37: Fix verb agreement for third-person singular.
The sentence reads "it allow you", which should be "it allows you".- But the benefits don't stop at individual understanding. The labels field offers a fantastic way to embed more guidance directly into your rules, and it allow you to share coding best practices, style guide reminders, or domain-specific knowledge across your entire team. + But the benefits don't stop at individual understanding. The labels field offers a fantastic way to embed more guidance directly into your rules, and it allows you to share coding best practices, style guide reminders, or domain-specific knowledge across your entire team.🧰 Tools
🪛 LanguageTool
[grammar] ~37-~37: After ‘it’, use the third-person verb form “allows”.
Context: ...idance directly into your rules, and it allow you to share coding best practices, sty...(IT_VBZ)
website/blog/optimize-ast-grep.md (1)
117-117: Typo fix correct; refine grammar and article usage.The correction of “optimzation” → “optimization” is accurate. Additionally, consider tightening the sentence and adjusting the article:
- I have already forsee it so every rule in ast-grep has an optimization called `potential_kinds`. AST node in tree-sitter has its own type encoded in a unsigned number called `kind`. + I had already foreseen it, so every rule in ast-grep has an optimization called `potential_kinds`. AST node in tree-sitter has its own type encoded in an unsigned number called `kind`.
- Change “I have already forsee it” → “I had already foreseen it,”
- Use “an unsigned number” instead of “a unsigned number”
🧰 Tools
🪛 LanguageTool
[uncategorized] ~117-~117: Possible missing comma found.
Context: ...ly make a match. I have already forsee it so every rule in ast-grep has an optimi...(AI_HYDRA_LEO_MISSING_COMMA)
[misspelling] ~117-~117: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...tree-sitter has its own type encoded in a unsigned number calledkind. If a rul...(EN_A_VS_AN)
website/catalog/python/recursive-rewrite-type.md (1)
12-12: Confirm spelling correction for “non-recursive”
Great catch fixing the typo. For smoother readability, consider adding “a” so it reads “using a non-recursive rewriter.”🧰 Tools
🪛 LanguageTool
[uncategorized] ~12-~12: You might be missing the article “a” here.
Context: ...te rewriting loop. So if you are using non-recursive rewriter like [this](https://...(AI_EN_LECTOR_MISSING_DETERMINER_A)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (9)
website/public/parsers/tree-sitter-c.wasmis excluded by!**/*.wasmwebsite/public/parsers/tree-sitter-css.wasmis excluded by!**/*.wasmwebsite/public/parsers/tree-sitter-elixir.wasmis excluded by!**/*.wasmwebsite/public/parsers/tree-sitter-go.wasmis excluded by!**/*.wasmwebsite/public/parsers/tree-sitter-json.wasmis excluded by!**/*.wasmwebsite/public/parsers/tree-sitter-rust.wasmis excluded by!**/*.wasmwebsite/public/parsers/tree-sitter-swift.wasmis excluded by!**/*.wasmwebsite/public/parsers/tree-sitter-tsx.wasmis excluded by!**/*.wasmwebsite/public/tree-sitter.wasmis excluded by!**/*.wasm
📒 Files selected for processing (14)
website/advanced/faq.md(1 hunks)website/blog/new-ver-38.md(1 hunks)website/blog/optimize-ast-grep.md(1 hunks)website/blog/stars-6000.md(1 hunks)website/blog/typed-napi.md(1 hunks)website/catalog/python/recursive-rewrite-type.md(1 hunks)website/catalog/python/refactor-pytest-fixtures.md(1 hunks)website/catalog/typescript/find-import-identifiers.md(8 hunks)website/guide/project/lint-rule.md(1 hunks)website/guide/rewrite-code.md(1 hunks)website/guide/rewrite/transform.md(1 hunks)website/reference/rule.md(1 hunks)website/reference/sgconfig.md(2 hunks)website/reference/yaml.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
website/blog/stars-6000.md
[style] ~96-~96: Consider using “each one”.
Context: ...s](/image/blog/sponsor2.png) We thank each and every one of you, especially ast-grep's sponsors,...
(EACH_AND_EVERY)
website/blog/new-ver-38.md
[grammar] ~37-~37: After ‘it’, use the third-person verb form “allows”.
Context: ...idance directly into your rules, and it allow you to share coding best practices, sty...
(IT_VBZ)
website/catalog/python/recursive-rewrite-type.md
[uncategorized] ~12-~12: You might be missing the article “a” here.
Context: ...te rewriting loop. So if you are using non-recursive rewriter like [this](https://...
(AI_EN_LECTOR_MISSING_DETERMINER_A)
website/blog/optimize-ast-grep.md
[uncategorized] ~117-~117: Possible missing comma found.
Context: ...ly make a match. I have already forsee it so every rule in ast-grep has an optimi...
(AI_HYDRA_LEO_MISSING_COMMA)
[misspelling] ~117-~117: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...tree-sitter has its own type encoded in a unsigned number called kind. If a rul...
(EN_A_VS_AN)
🔇 Additional comments (18)
website/blog/stars-6000.md (1)
96-96: Typo correction is accurate.
Excellent catch fixing "espeically" → "especially".🧰 Tools
🪛 LanguageTool
[style] ~96-~96: Consider using “each one”.
Context: ...s](/image/blog/sponsor2.png) We thank each and every one of you, especially ast-grep's sponsors,...(EACH_AND_EVERY)
website/blog/typed-napi.md (1)
173-173: Consistent capitalization for sentence start.
Capitalizing "E.g." at the beginning of a sentence improves readability.website/guide/rewrite/transform.md (1)
13-13: Corrected spelling of "illustrating".
Good catch fixing "illustring" to "illustrating".website/catalog/python/refactor-pytest-fixtures.md (1)
34-34: Corrected spelling of "straightforward".
The typo "straghtforward" has been fixed to "straightforward".website/reference/rule.md (1)
46-46: Typo fix looks good.The phrase “deep dive doc” is now correct and the link remains accurate.
website/reference/yaml.md (1)
34-34: Typo fix looks good.Corrected “includ” to “include” in the description of the
languagefield.website/advanced/faq.md (1)
200-200: Typo fix looks good.Corrected “scneario” to “scenario” in the FAQ header.
website/guide/project/lint-rule.md (1)
169-169: Capitalization fix is correct.“Meta-variables” is now properly capitalized to match the surrounding documentation style.
website/reference/sgconfig.md (1)
55-55: Approve spelling correction in documentation
The typo “undert” was correctly fixed to “under” in the description ofsnapshotDir.website/catalog/python/recursive-rewrite-type.md (1)
14-14: Approve typo fix
The spelling and formatting of the descriptive text have been corrected appropriately.website/guide/rewrite-code.md (1)
176-176: Approve typo fix for “trivials”
Corrected “trivias” to “trivials” in the context explanation, improving clarity.website/catalog/typescript/find-import-identifiers.md (7)
62-62: Approve whitespace cleanup
Trailing spaces and unnecessary blank lines were removed; no semantic changes.
82-82: Approve whitespace cleanup
Trailing spaces and unnecessary blank lines were removed; no semantic changes.
108-108: Approve whitespace cleanup
Trailing spaces and unnecessary blank lines were removed; no semantic changes.
139-139: Approve whitespace cleanup
Trailing spaces and unnecessary blank lines were removed; no semantic changes.
180-180: Approve whitespace cleanup
Trailing spaces and unnecessary blank lines were removed; no semantic changes.
201-201: Approve whitespace cleanup
Trailing spaces and unnecessary blank lines were removed; no semantic changes.
292-292: Approve whitespace cleanup in example
Removed trailing spaces in the import example; formatting is now consistent.
Summary by CodeRabbit