Merge pull request #1374 from JamBalaya56562/docs-typos

docs: fix typos

Author: danielrozenberg

README.md

@@ -89,7 +89,7 @@ npm run test:node -- packages/optimizer
 
 ### Style & Linting
 
-This codebase adheres to the [Google Javascript Styleguide](https://google.github.io/styleguide/jsguide.html) and is enforced using ESLint. ESLint is run as part of the test suite, but you can also explicity run it via:
+This codebase adheres to the [Google Javascript Styleguide](https://google.github.io/styleguide/jsguide.html) and is enforced using ESLint. ESLint is run as part of the test suite, but you can also explicitly run it via:
 
 ```
 # run ESLint

packages/cors/README.md

@@ -84,7 +84,7 @@ app.use(ampCors({
 
 ### Logging
 
-For debugging requests, you can enable the verbose loggin mode via the `verbose` option:
+For debugging requests, you can enable the verbose logging mode via the `verbose` option:
 
 ```
 app.use(ampCors({

packages/optimizer/README.md

@@ -244,7 +244,7 @@ Enables hero image optimization. Hero images will either be auto detected or you
 
 The maximum number of hero images that can be marked up using `data-hero` is `2`. This number can be increased using the `maxHeroImageCount` parameter.
 
-Hero images are optimized by server-side rendering the `img` element inside the `amp-img` element. This can siginificantly improve image rendering performance and reduce the [largest contentful paint](https://web.dev/lcp/) (LCP) metric from [Core Web Vitals](https://web.dev/vitals/).
+Hero images are optimized by server-side rendering the `img` element inside the `amp-img` element. This can significantly improve image rendering performance and reduce the [largest contentful paint](https://web.dev/lcp/) (LCP) metric from [Core Web Vitals](https://web.dev/vitals/).
 
 - name: `optimizeHeroImages`
 - valid options: `[true|false]`