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: