-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] Close Hacktoberfest docs tickets with fixes for Vale issues #848
Conversation
View the example dashboards of the current commit live on PyCafe ☕ 🚀Updated on: 2024-11-05 13:17:54 UTC Link: vizro-core/examples/dev/ |
for more information, see https://pre-commit.ci
…vizro into docs/clear-vale-issues
for more information, see https://pre-commit.ci
…vizro into docs/clear-vale-issues
for more information, see https://pre-commit.ci
…vizro into docs/clear-vale-issues
for more information, see https://pre-commit.ci
Switch off the whole of the FAQ page
…vizro into docs/clear-vale-issues
for more information, see https://pre-commit.ci
…vizro into docs/clear-vale-issues
for more information, see https://pre-commit.ci
…vizro into docs/clear-vale-issues
for more information, see https://pre-commit.ci
…vizro into docs/clear-vale-issues
Looks good to me! (I added a comment around one word, though it might still be fine to accept the existing wording there, if that is preferred) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving in advance 👍 (in case it is determined that the existing wording is acceptable)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Co-authored-by: Lingyi Zhang <[email protected]>
Co-authored-by: Lingyi Zhang <[email protected]>
Description
A set of changes to the language of the docs to fix some issues that typically complicate the language. To turn on all Vale suggestions/warnings, I dropped the word "leverage" into a page of docs. It's like a bomb went off, and all the niggles and grievances that Vale was holding onto were surfaced.
Most of them were arguable, but ideally if we can avoid "allow" when we mean "enable" and "provide" when we mean "supply" or "give" then we're helping our users parse the docs a little faster.
I turned off Vale in the FAQs page as that's rather promotional (it takes the old messaging from the readme)
A few issues with Vizro-AI docs in terms of readability: I will take a spin through these docs while @lingyielia is around this week to make sure any further tweaks (beyond what I've done here just to satisfy Vale) don't break the meaning.
Screenshot
Notice
I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":