From 7446550fdbbe222f69dab35bc0317dc9002d46ad Mon Sep 17 00:00:00 2001 From: Dan Dascalescu Date: Sat, 26 Jan 2019 21:37:02 -0800 Subject: [PATCH] docs(api.md): fix typo (#3848) --- docs/api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api.md b/docs/api.md index b54f66a2e10fa..0aca429fb4cab 100644 --- a/docs/api.md +++ b/docs/api.md @@ -348,7 +348,7 @@ To sum up, the only differences between `puppeteer-core` and `puppeteer` are: In most cases, you'll be fine using the `puppeteer` package. However, you should use `puppeteer-core` if: -- you're building another end-user product or library atop of DevTools protocol. For example, one might build PDF generator using `puppeteer-core` and write a custom `install.js` script that downloads [`headless_shell`](https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md) instead of Chromium to save disk space. +- you're building another end-user product or library atop of DevTools protocol. For example, one might build a PDF generator using `puppeteer-core` and write a custom `install.js` script that downloads [`headless_shell`](https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md) instead of Chromium to save disk space. - you're bundling Puppeteer to use in Chrome Extension / browser with the DevTools protocol where downloading an additional Chromium binary is unnecessary. When using `puppeteer-core`, remember to change the *include* line: