From 6d72b0362793373f8fa82818d9af0ec036008971 Mon Sep 17 00:00:00 2001
From: q1800 <95879668+q1800@users.noreply.github.com>
Date: Sun, 24 Apr 2022 21:43:42 -0500
Subject: [PATCH] Typos

---
 Dynamic-filtering:-rule-syntax.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Dynamic-filtering:-rule-syntax.md b/Dynamic-filtering:-rule-syntax.md
index cce1dd5..a95dda5 100644
--- a/Dynamic-filtering:-rule-syntax.md
+++ b/Dynamic-filtering:-rule-syntax.md
@@ -47,7 +47,7 @@ Type-based rules are used to filter specific types of request on a web page. Cur
 - `3p-script`: 3rd-party scripts, i.e. scripts which are pulled from a different domain name than that of the current web page
 - `3p-frame`: 3rd-party frames, i.e. frames elements which are pulled from a different domain name than that of current web page
 
-These rules can apply everywhere, or be specific to a web site. For instance blocking 3rd-party frames is a very good habit security-wise: `* * 3p-frame block`. This rule translates into "globally block 3rd-party frames".
+These rules can apply everywhere, or be specific to a website. For instance blocking 3rd-party frames is a very good habit security-wise: `* * 3p-frame block`. This rule translates into "globally block 3rd-party frames".
 
 Another example: `wired.com * image block`, which means "block images from all origins when visiting a web page on wired.com".
 
@@ -63,7 +63,7 @@ With hostname-based rule, the request type is always `*`, meaning the rule will
 
 For example, `* disqus.com * block` means "globally block all net requests to `disqus.com`".
 
-Just like type-based rules, a hostname-based rule can apply only when visiting a specific web site, for example: `wired.com disqus.com * noop`, which means "do not apply dynamic filtering to network requests to `disqus.com` when visiting a web page on `wired.com`. Since this last rule is more specific than the previous one, it will override the global blocking of `disqus.com` everywhere.
+Just like type-based rules, a hostname-based rule can apply only when visiting a specific website, for example: `wired.com disqus.com * noop`, which means "do not apply dynamic filtering to network requests to `disqus.com` when visiting a web page on `wired.com`. Since this last rule is more specific than the previous one, it will override the global blocking of `disqus.com` everywhere.
 
 ***
 
@@ -76,6 +76,6 @@ A matching rule can do one of three things:
     - Thus you can use them to block with 100% certainty (unless you set another overriding dynamic filter rule).
 - `allow`: matching network request will be allowed.
     - `allow` dynamic filters rules override any existing static and dynamic block filters.
-    - Thus they are most useful to create finer-grained exceptions, and to un-break web sites broken by some static filters somewhere.
+    - Thus they are most useful to create finer-grained exceptions, and to un-break websites broken by some static filters somewhere.
 - `noop`: exclude network requests from being subjected to dynamic filtering.
     - It cancels dynamic filtering, but it does not cancel static filtering.