Skip to content

fix: Renaming userguide titles in V23 doc folder - #1995

Open
Dindihub wants to merge 2 commits into
vitessio:prodfrom
Dindihub:rename-userguides-v23
Open

fix: Renaming userguide titles in V23 doc folder#1995
Dindihub wants to merge 2 commits into
vitessio:prodfrom
Dindihub:rename-userguides-v23

Conversation

@Dindihub

Copy link
Copy Markdown

This PR covers some of the renaming suggestions mentioned in issue #1974
If these suggestions are welcome, I will address the other issues mentioned, including changing the heading hierarchy, in another PR

Signed-off-by: Dindihub <sadindi03@gmail.com>
@Dindihub
Dindihub force-pushed the rename-userguides-v23 branch from a27f480 to 33416e9 Compare June 25, 2025 11:56
@netlify

netlify Bot commented Jun 26, 2025

Copy link
Copy Markdown

Deploy Preview for vitess ready!

Name Link
🔨 Latest commit af58efb
🔍 Latest deploy log https://app.netlify.com/projects/vitess/deploys/6a5b3fbf5cdd7100084dee5a
😎 Deploy Preview https://deploy-preview-1995--vitess.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Dindihub Dindihub changed the title fix: Renaming of userguide titles in V23 fix: Renaming userguide titles in V23 Jul 7, 2025
@Dindihub Dindihub changed the title fix: Renaming userguide titles in V23 fix: Renaming userguide titles in V23 doc folder Jul 7, 2025
@mattlord

Copy link
Copy Markdown
Member

Hi @Dindihub !

I apologize for the delay on this. Please feel free to ping me in the Vitess slack about things like this if they seem to have fallen through the cracks.

This work seems like it's worth carrying forward. If so, we should make the same changes to the 24.0 and 25.0 docs. Are you interested in doing that here?

Thanks! ❤️

@Dindihub

Copy link
Copy Markdown
Author

Hi @Dindihub !

I apologize for the delay on this. Please feel free to ping me in the Vitess slack about things like this if they seem to have fallen through the cracks.

This work seems like it's worth carrying forward. If so, we should make the same changes to the 24.0 and 25.0 docs. Are you interested in doing that here?

Thanks! ❤️

Hey @mattlord ,
Understandable about the delay. I'll make the changes to About V24 & V25. I'll also reach out on slack for a larger project for the docs that I have in mind.

Thanks

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.

2 participants