From da391fe9ed17520bb0e1cfd3d5c5e804a9ad6efe Mon Sep 17 00:00:00 2001 From: Rita Bradley <41173740+ritabradley@users.noreply.github.com> Date: Tue, 2 May 2023 12:33:33 -0700 Subject: [PATCH] Fix typos (#3795) * Fix typos - Add 's' to reason - Change "it's" to is - Remove unnecessary hyphen * Fix typos - change 'remove' to 'removing' - change comma to semicolon * Fix typos - change "don't" to "doesn't" - add "is" before "relied upon" --- .../content/analyse-stylesheets-complexity.md | 4 ++-- .../frontend-performance/content/avoid-inline-css.md | 2 +- .../content/use-non-blocking-javascript.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/data/best-practices/frontend-performance/content/analyse-stylesheets-complexity.md b/src/data/best-practices/frontend-performance/content/analyse-stylesheets-complexity.md index e650d1a02..2c4103e5f 100644 --- a/src/data/best-practices/frontend-performance/content/analyse-stylesheets-complexity.md +++ b/src/data/best-practices/frontend-performance/content/analyse-stylesheets-complexity.md @@ -2,9 +2,9 @@ > Analyzing your stylesheets can help you to flag issues, redundancies and duplicate CSS selectors. -Sometimes you may have redundancies or validation errors in your CSS, analysing your CSS files and removed these complexities can help you to speed up your CSS files (because your browser will read them faster). +Sometimes you may have redundancies or validation errors in your CSS, analysing your CSS files and removing these complexities can help you to speed up your CSS files (because your browser will read them faster). -Your CSS should be organized, using a CSS preprocessor can help you with that. Some online tools listed below can also help you analysing and correct your code. +Your CSS should be organized; using a CSS preprocessor can help you with that. Some online tools listed below can also help you analysing and correct your code. - [TestMyCSS | Optimize and Check CSS Performance](http://www.testmycss.com/) - [CSS Stats](https://cssstats.com/) diff --git a/src/data/best-practices/frontend-performance/content/avoid-inline-css.md b/src/data/best-practices/frontend-performance/content/avoid-inline-css.md index 04f70c4dc..479a4f2bc 100644 --- a/src/data/best-practices/frontend-performance/content/avoid-inline-css.md +++ b/src/data/best-practices/frontend-performance/content/avoid-inline-css.md @@ -2,7 +2,7 @@ > Avoid using embed or inline CSS inside your `` (Not valid for HTTP/2) -One of the first reason it's because it's a good practice to separate content from design. It also helps you have a more maintainable code and keep your site accessible. But regarding performance, it's simply because it decreases the file-size of your HTML pages and the load time. +One of the first reasons is because it's a good practice to separate content from design. It also helps you have a more maintainable code and keep your site accessible. But regarding performance, it's simply because it decreases the file size of your HTML pages and the load time. Always use external stylesheets or embed CSS in your `` (and follow the others CSS performance rules) diff --git a/src/data/best-practices/frontend-performance/content/use-non-blocking-javascript.md b/src/data/best-practices/frontend-performance/content/use-non-blocking-javascript.md index 1b64a5883..75d74e0d4 100644 --- a/src/data/best-practices/frontend-performance/content/use-non-blocking-javascript.md +++ b/src/data/best-practices/frontend-performance/content/use-non-blocking-javascript.md @@ -12,7 +12,7 @@ JavaScript files are loaded asynchronously using async or deferred using defer a JavaScript blocks the normal parsing of the HTML document, so when the parser reaches a `