Skip to content

fix(guides/theming.md) Typo fix of theming.md #28353

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

Merged
merged 1 commit into from
Jan 3, 2024

Conversation

programmerkgit
Copy link
Contributor

@programmerkgit programmerkgit commented Jan 2, 2024

I guess the word "us" might be a typo of "use".

Seems wrong passage

The recommended approach is to rely on the theme mixins to lay down your base styles, and if needed us the single dimension mixins to override particular aspects for parts of your app (see the section on...

### Seems wrong passage

The recommended approach is to rely on the `theme` mixins to lay down your base styles, and if
needed *us* the single dimension mixins to override particular aspects for parts of your app (see the
section on...

### Seems wrong passage

The recommended approach is to rely on the `theme` mixins to lay down your base styles, and if
needed *use* the single dimension mixins to override particular aspects for parts of your app (see the
section on
Copy link

google-cla bot commented Jan 2, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@programmerkgit programmerkgit changed the title Typo fix of theming.md fix()Typo fix of theming.md Jan 3, 2024
@programmerkgit programmerkgit changed the title fix()Typo fix of theming.md fix(guides/theming.md) Typo fix of theming.md Jan 3, 2024
@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed labels Jan 3, 2024
@crisbeto crisbeto removed the request for review from jelbourn January 3, 2024 12:59
@crisbeto crisbeto merged commit 5ab2e7a into angular:main Jan 3, 2024
crisbeto pushed a commit that referenced this pull request Jan 3, 2024
The recommended approach is to rely on the `theme` mixins to lay down your base styles, and if
needed *us* the single dimension mixins to override particular aspects for parts of your app (see the
section on...

The recommended approach is to rely on the `theme` mixins to lay down your base styles, and if
needed *use* the single dimension mixins to override particular aspects for parts of your app (see the
section on

(cherry picked from commit 5ab2e7a)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants