fix: typos in comments

[NAM-MAN]

Fix typos in comments:

• is is → is (x3)
• a a → a
• to to → to (x3)

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

AI Detection Analysis 🔍

Confidence Score: 60%

Reasoning: The pull request focuses on fixing very specific and repetitive types of typos in comments, without broader changes to logic or code. While it is possible for a human to make these corrections, the uniformity and consistency across multiple files and the nature of the changes align with actions commonly taken by automated tools or scripts focused on natural language correction. The summary itself displays a list of exact substitutions in a concise and structured format, a style often seen in AI-generated or assisted outputs.

Key Indicators:

• The changelog mentions correcting multiple identical typos (e.g., "is is → is (x3)"), suggesting automated identification.
• Changes are consistent in formatting and scope (all in comments), lacking variability typical of human editing styles.
• The description is succinct and formulaic, resembling the output of a script or LLM summarization.
• The phrase "Fix typos in comments" and the itemized list format match common structures generated by AI-based tools like GitHub Copilot or AI writing assistants.

While a human might have made these changes, the pattern and format are more suggestive of AI assistance.

✅ No strong indicators of AI generation detected

[bep]

This isn't entirely correct.

[bep]

"to to" sounds odd, but it is correct.

[NAM-MAN]

Thanks @bep for catching that! You're absolutely right - I missed that to is a variable/parameter name in those cases, so "to to" is actually correct (preposition + variable name).

I've reverted the changes to append.go and chain.go, keeping only the genuine typo fixes:

• is is → is (x3)
• a a → a
• to to → to (only in pagelexer_shortcode.go where it's not a variable name)

Sorry for the noise! 🙇