From e07567f26838faf08fff004466ad5153ceb55581 Mon Sep 17 00:00:00 2001 From: Vse Mozhet Byt Date: Wed, 5 Sep 2018 00:38:55 +0300 Subject: [PATCH] docs(api.md): fix a typo (#3196) --- docs/api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api.md b/docs/api.md index f39f63757776b..811cc760e6753 100644 --- a/docs/api.md +++ b/docs/api.md @@ -324,7 +324,7 @@ Every release since v1.7.0 we publish two packages: `puppeteer` is a *product* for browser automation. When installed, it downloads a version of Chromium, which it then drives using `puppeteer-core`. Being an end-user product, `puppeteer` supports a bunch of convenient `PUPPETEER_*` env variables to tweak its behavior. -`puppetee-core` is a *library* to help drive anything that supports DevTools protocol. `puppeteer-core` doesn't download Chromium when installed. Being a library, `puppeteer-core` is fully driven +`puppeteer-core` is a *library* to help drive anything that supports DevTools protocol. `puppeteer-core` doesn't download Chromium when installed. Being a library, `puppeteer-core` is fully driven through its programmatic interface and disregards all the `PUPPETEER_*` env variables. To sum up, the only differences between `puppeteer-core` and `puppeteer` are: