Docs: change some title containing '&' to bypass Algolia issue #37400
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
mdo
approved these changes
Dec 26, 2022
mdo
force-pushed
the
main-jd-fix-other-h1-titles
branch
from
1aba86a
to
f3ae3eb
Compare
|
We should report this upstream. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related
&displayed in Algolia search results titles #37342Description
Change "&" in "and" in h1 titles to bypass an Algolia issue displaying them as "&" in the results.
Motivation & Context
Some other titles need to be modified in the same spirit as #37397.
Type of changes
Checklist
npm run lint)Live previews