Skip to content
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] Grammar fix for global class names docs #16778

Merged
merged 2 commits into from
Jul 28, 2019

Conversation

joshwooding
Copy link
Member

Reference: #16770 (review)

cc @mbrookes

@joshwooding joshwooding added the docs Improvements or additions to the documentation label Jul 27, 2019
@joshwooding joshwooding requested a review from mbrookes July 27, 2019 23:18
@mui-pr-bot
Copy link

No bundle size changes comparing 3f9fa1f...d88bc8e

Generated by 🚫 dangerJS against d88bc8e

Copy link
Member

@mbrookes mbrookes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Josh!


- With a rule name of the [\`classes\` object prop](/customization/components/#overriding-styles-with-classes).
- With a [global class name](/customization/components/#overriding-styles-with-global-class-names).
- With a theme and an [\`overrides\` property](/customization/globals/#css).

If it's not enough, you can find the [implementation of the component](${SOURCE_CODE_ROOT_URL}${normalizePath(
If that's not sufficient, you can check the [implementation of the component](${SOURCE_CODE_ROOT_URL}${normalizePath(
reactAPI.filename,
)}) for more detail.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
)}) for more detail.
)}) for more details.

Copy link
Member

@oliviertassinari oliviertassinari Jul 28, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems to depend on the context. Do we want to focus on the quality or the quantity of extra information: https://english.stackexchange.com/questions/123672/detail-or-details-read-on-for-more-detail-details?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note, we were using "detail" in the past, highlighting the quality aspect. We are also using "detail" when the ref is attached to an imperative handle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to the documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants