chore: make docs MDX-compatible, pt. 2

[samueldemoura]

Summary

Followup to #1724 - I missed a file. Same intent: to make the .md files inside docs/ parseable as MDX so Gatsby can pull them in and build properly.

---

This change is 

Summary by CodeRabbit

• Documentation
  • Clarified compatibility wording to state support for React on Rails versions earlier than 15.

[coderabbitai]

Walkthrough

The Turbolinks documentation for Rails has been updated to clarify the versioning language regarding React on Rails compatibility. The sentence has been modified from stating "React on Rails <15" to "React on Rails earlier than 15." There are no changes to functionality or logic, only a clarification in wording.

Changes

File	Change Summary
docs/rails/turbolinks.md	Updated wording from "React on Rails <15" to "React on Rails earlier than 15" to clarify compatibility.

Poem

In the docs, I hopped with delight,
Tweaking words in the soft morning light.
"<15" transformed with a fluffy twist,
Now "earlier" shines—clarity can't be missed.
I, the rabbit, cheer this update with pure bliss! 🐇

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/rails/turbolinks.md (2)

87-92: Clarify Version Compatibility Wording

The updated sentence now reads “React on Rails earlier than 15,” which is clearer and more descriptive compared to using the symbolic "<15." This improves readability and reduces ambiguity for documentation readers. Please verify that any other references to the version are updated similarly for consistency.

---

1-1: Ensure MDX Compatibility

While the changes here focus on clarifying version compatibility, please double-check that the Markdown syntax used in this file aligns with MDX expectations in your Gatsby configuration. For instance, if additional front matter or JSX components will be added later to enhance MDX features, ensure that the file structure can accommodate those without conflicts.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b9487d4 and 18ba004.

📒 Files selected for processing (1)

• docs/rails/turbolinks.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: dummy-app-integration-tests (oldest)
• GitHub Check: dummy-app-integration-tests (newest)