Skip to content

docs: html tags updated #27164

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
May 26, 2023
Merged

docs: html tags updated #27164

merged 1 commit into from
May 26, 2023

Conversation

aanchal88
Copy link
Contributor

No description provided.

@angular-robot angular-robot bot added the area: docs Related to the documentation label May 25, 2023
@devversion devversion removed their request for review May 25, 2023 10:42
@aanchal88
Copy link
Contributor Author

Hii @crisbeto , please review the PR.

@andrewseguin
Copy link
Contributor

What's the purpose of changing <b> to <strong>?

@aanchal88
Copy link
Contributor Author

Hii @andrewseguin, Using the tag is generally considered more appropriate when we want to convey importance or emphasize content. It's recommended to use while can be used for purely visual purposes without any specific semantic meaning.
Thank you!

@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 labels May 26, 2023
@crisbeto crisbeto merged commit b7a466d into angular:main May 26, 2023
crisbeto pushed a commit that referenced this pull request May 26, 2023
(cherry picked from commit b7a466d)
@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 Jul 3, 2023
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 area: docs Related to the documentation target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants