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"
kamranahmedse · May 2, 2023 · da391fe · da391fe
1 parent 953ca92
commit da391fe
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/...a/best-practices/frontend-performance/content/analyse-stylesheets-complexity.md b/...a/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
@@ -2,7 +2,7 @@
 
 > Avoid using embed or inline CSS inside your `<body>` (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 `<head>` (and follow the others CSS performance rules)
 

diff --git a/...data/best-practices/frontend-performance/content/use-non-blocking-javascript.md b/...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 `<script>` tag (particularly is inside the `<head>`), it stops to fetch and run it. Adding async or defer are highly recommended if your scripts are placed in the top of your page but less valuable if just before your `</body>` tag. But it's a good practice to always use these attributes to avoid any performance issue.
 
-- Add `async` (if the script don't rely on other scripts) or `defer` (if the script relies upon or relied upon by an async script) as an attribute to your script tag.
+- Add `async` (if the script doesn't rely on other scripts) or `defer` (if the script relies upon or is relied upon by an async script) as an attribute to your script tag.
 - If you have small scripts, maybe use inline script place above async scripts.
 
 - [Remove Render-Blocking JavaScript](https://developers.google.com/speed/docs/insights/BlockingJS)