docs: fix typo #12050
Merged
docs: fix typo #12050
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
Lightning00Blade
approved these changes
Mar 6, 2024
|
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use -- conventional-commit-lint bot |
PUPPETEER_SKIP_CHROME_HEADLESSS_HELL_DOWNLOAD should be PUPPETEER_SKIP_CHROME_HEADLESS_SHELL_DOWNLOAD
Lightning00Blade
force-pushed
the
yotam/fix-type-in-docs
branch
from
299c8d8
to
bda5af3
Compare
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.
What kind of change does this PR introduce?
Fix a typo in the docs:
PUPPETEER_SKIP_CHROME_HEADLESSS_HELL_DOWNLOADis incompatible with the value implemented in code which isPUPPETEER_SKIP_CHROME_HEADLESS_SHELL_DOWNLOADDid you add tests for your changes?
Not required
If relevant, did you update the documentation?
Yes
Summary
Aligning the docs with the code.
Does this PR introduce a breaking change?
No
Other information