Skip to content

docs: name the client_routes spellings on the client routes page - #1139

Closed
nikagra wants to merge 1 commit into
scylladb:scylla-4.xfrom
nikagra:client-routes-spellings
Closed

nikagra wants to merge 1 commit into
scylladb:scylla-4.xfrom
nikagra:client-routes-spellings

Conversation

@nikagra

@nikagra nikagra commented Sep 24, 2026 •

Copy link
Copy Markdown

Depends on: nothing (independent of #1151; they merge in either order)
Blocks: nothing

The docs search indexes visible text, and the client routes page never spells the feature client_routes or clientroutes (only the table name). One sentence, as gocql's page does. The same sentence goes into the per-version backports so they don't diverge from the mainline.

Verified by rendering the page in the four-version local build and grepping its text for each epic term.

Refs #1119
Jira: DRIVER-1042

🤖 Generated with Claude Code

The docs search indexes visible text, and the page names the feature
only as "client routes" and the table system.client_routes. Say that it
is also written client_routes or clientroutes, as gocql's page does.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@coderabbitai

coderabbitai Bot commented Sep 24, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

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

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant