|
diff --git a/docs/guides/locators.md b/docs/guides/locators.md
index 96adbdbb42c..cbce26fb2b5 100644
--- a/docs/guides/locators.md
+++ b/docs/guides/locators.md
@@ -86,7 +86,7 @@ The following preconditions are automatically checked:
await page.locator('input').fill('value');
```
-Automatically detects the input type and choose an approritate way to fill it out with the provided value.
+Automatically detects the input type and choose an appropriate way to fill it out with the provided value.
The following preconditions are automatically checked:
diff --git a/docs/index.md b/docs/index.md
index 41bc2c7a20d..d889e103e49 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -49,7 +49,7 @@ When you install Puppeteer, it automatically downloads a recent version of
[Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing/) (~170MB macOS, ~282MB Linux, ~280MB Windows) and a `chrome-headless-shell` binary (starting with Puppeteer v21.6.0) that is [guaranteed to
work](https://pptr.dev/faq#q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy)
with Puppeteer. The browser is downloaded to the `$HOME/.cache/puppeteer` folder
-by default (starting with Puppeteer v19.0.0). See [configuration](https://pptr.dev/api/puppeteer.configuration) for configuration options and environmental variables to control the download behavor.
+by default (starting with Puppeteer v19.0.0). See [configuration](https://pptr.dev/api/puppeteer.configuration) for configuration options and environmental variables to control the download behavior.
If you deploy a project using Puppeteer to a hosting provider, such as Render or
Heroku, you might need to reconfigure the location of the cache to be within
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index 914fed4c87f..7bf4e1b4f74 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -689,7 +689,7 @@ and if you want to run Puppeteer tests in amazon-linux, follow these steps.
Now Puppeteer can launch Chromium to run your tests. If you do not enable EPEL
and if you continue installing chromium as part of `npm install`, Puppeteer
-cannot launch Chromium due to unavailablity of `libatk-1.0.so.0` and many more
+cannot launch Chromium due to unavailability of `libatk-1.0.so.0` and many more
packages.
## Code Transpilation Issues
diff --git a/packages/puppeteer-core/src/api/BrowserContext.ts b/packages/puppeteer-core/src/api/BrowserContext.ts
index 5e6a5d5d5cf..7cedd5f3a47 100644
--- a/packages/puppeteer-core/src/api/BrowserContext.ts
+++ b/packages/puppeteer-core/src/api/BrowserContext.ts
@@ -151,7 +151,7 @@ export abstract class BrowserContext extends EventEmitter
*
* @deprecated In Chrome, the
* {@link Browser.defaultBrowserContext | default browser context} can also be
- * "icognito" if configured via the arguments and in such cases this getter
+ * "incognito" if configured via the arguments and in such cases this getter
* returns wrong results (see
* https://github.com/puppeteer/puppeteer/issues/8836). Also, the term
* "incognito" is not applicable to other browsers. To migrate, check the
diff --git a/website/versioned_docs/version-22.6.3/api/puppeteer.browsercontext.isincognito.md b/website/versioned_docs/version-22.6.3/api/puppeteer.browsercontext.isincognito.md
index d0881e41910..04fbfc638e0 100644
--- a/website/versioned_docs/version-22.6.3/api/puppeteer.browsercontext.isincognito.md
+++ b/website/versioned_docs/version-22.6.3/api/puppeteer.browsercontext.isincognito.md
@@ -6,7 +6,7 @@ sidebar_label: BrowserContext.isIncognito
> Warning: This API is now obsolete.
>
-> In Chrome, the [default browser context](./puppeteer.browser.defaultbrowsercontext.md) can also be "icognito" if configured via the arguments and in such cases this getter returns wrong results (see https://github.com/puppeteer/puppeteer/issues/8836). Also, the term "incognito" is not applicable to other browsers. To migrate, check the [default browser context](./puppeteer.browser.defaultbrowsercontext.md) instead: in Chrome all non-default contexts are incognito, and the default context might be incognito if you provide the `--incognito` argument when launching the browser.
+> In Chrome, the [default browser context](./puppeteer.browser.defaultbrowsercontext.md) can also be "incognito" if configured via the arguments and in such cases this getter returns wrong results (see https://github.com/puppeteer/puppeteer/issues/8836). Also, the term "incognito" is not applicable to other browsers. To migrate, check the [default browser context](./puppeteer.browser.defaultbrowsercontext.md) instead: in Chrome all non-default contexts are incognito, and the default context might be incognito if you provide the `--incognito` argument when launching the browser.
Whether this [browser context](./puppeteer.browsercontext.md) is incognito.
diff --git a/website/versioned_docs/version-22.6.3/api/puppeteer.browsercontext.md b/website/versioned_docs/version-22.6.3/api/puppeteer.browsercontext.md
index ab7c2230785..a184bf06818 100644
--- a/website/versioned_docs/version-22.6.3/api/puppeteer.browsercontext.md
+++ b/website/versioned_docs/version-22.6.3/api/puppeteer.browsercontext.md
@@ -158,7 +158,7 @@ In Chrome, the [default browser context](./puppeteer.browser.defaultbrowserconte
**Deprecated:**
-In Chrome, the [default browser context](./puppeteer.browser.defaultbrowsercontext.md) can also be "icognito" if configured via the arguments and in such cases this getter returns wrong results (see https://github.com/puppeteer/puppeteer/issues/8836). Also, the term "incognito" is not applicable to other browsers. To migrate, check the [default browser context](./puppeteer.browser.defaultbrowsercontext.md) instead: in Chrome all non-default contexts are incognito, and the default context might be incognito if you provide the `--incognito` argument when launching the browser.
+In Chrome, the [default browser context](./puppeteer.browser.defaultbrowsercontext.md) can also be "incognito" if configured via the arguments and in such cases this getter returns wrong results (see https://github.com/puppeteer/puppeteer/issues/8836). Also, the term "incognito" is not applicable to other browsers. To migrate, check the [default browser context](./puppeteer.browser.defaultbrowsercontext.md) instead: in Chrome all non-default contexts are incognito, and the default context might be incognito if you provide the `--incognito` argument when launching the browser.
|
|
diff --git a/website/versioned_docs/version-22.6.3/guides/locators.md b/website/versioned_docs/version-22.6.3/guides/locators.md
index 96adbdbb42c..cbce26fb2b5 100644
--- a/website/versioned_docs/version-22.6.3/guides/locators.md
+++ b/website/versioned_docs/version-22.6.3/guides/locators.md
@@ -86,7 +86,7 @@ The following preconditions are automatically checked:
await page.locator('input').fill('value');
```
-Automatically detects the input type and choose an approritate way to fill it out with the provided value.
+Automatically detects the input type and choose an appropriate way to fill it out with the provided value.
The following preconditions are automatically checked:
diff --git a/website/versioned_docs/version-22.6.3/index.md b/website/versioned_docs/version-22.6.3/index.md
index 41bc2c7a20d..d889e103e49 100644
--- a/website/versioned_docs/version-22.6.3/index.md
+++ b/website/versioned_docs/version-22.6.3/index.md
@@ -49,7 +49,7 @@ When you install Puppeteer, it automatically downloads a recent version of
[Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing/) (~170MB macOS, ~282MB Linux, ~280MB Windows) and a `chrome-headless-shell` binary (starting with Puppeteer v21.6.0) that is [guaranteed to
work](https://pptr.dev/faq#q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy)
with Puppeteer. The browser is downloaded to the `$HOME/.cache/puppeteer` folder
-by default (starting with Puppeteer v19.0.0). See [configuration](https://pptr.dev/api/puppeteer.configuration) for configuration options and environmental variables to control the download behavor.
+by default (starting with Puppeteer v19.0.0). See [configuration](https://pptr.dev/api/puppeteer.configuration) for configuration options and environmental variables to control the download behavior.
If you deploy a project using Puppeteer to a hosting provider, such as Render or
Heroku, you might need to reconfigure the location of the cache to be within
diff --git a/website/versioned_docs/version-22.6.3/troubleshooting.md b/website/versioned_docs/version-22.6.3/troubleshooting.md
index 914fed4c87f..7bf4e1b4f74 100644
--- a/website/versioned_docs/version-22.6.3/troubleshooting.md
+++ b/website/versioned_docs/version-22.6.3/troubleshooting.md
@@ -689,7 +689,7 @@ and if you want to run Puppeteer tests in amazon-linux, follow these steps.
Now Puppeteer can launch Chromium to run your tests. If you do not enable EPEL
and if you continue installing chromium as part of `npm install`, Puppeteer
-cannot launch Chromium due to unavailablity of `libatk-1.0.so.0` and many more
+cannot launch Chromium due to unavailability of `libatk-1.0.so.0` and many more
packages.
## Code Transpilation Issues
|