From 5aa5b6d579c33cf0fe2e86e7c0b78987b18f2763 Mon Sep 17 00:00:00 2001
From: q1800 <95879668+q1800@users.noreply.github.com>
Date: Sun, 24 Apr 2022 21:53:08 -0500
Subject: [PATCH] Typo

---
 Strict-blocking.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Strict-blocking.md b/Strict-blocking.md
index 0ddd72a..8214057 100644
--- a/Strict-blocking.md
+++ b/Strict-blocking.md
@@ -15,7 +15,7 @@ This means that using the same test case above, **uBO will block the web page**
 
 ![Page was fully blocked](https://cloud.githubusercontent.com/assets/585534/8160013/14466ca0-133a-11e5-8d3c-28169288f35a.png)
 
-Why the change? Because [issue #1013](https://github.com/chrisaljoudi/uBlock/issues/1013) brought forth why it is desirable sometimes to completely block a web site, as opposed to what the ABP-filtering semantic dictates.
+Why the change? Because [issue #1013](https://github.com/chrisaljoudi/uBlock/issues/1013) brought forth why it is desirable sometimes to completely block a website, as opposed to what the ABP-filtering semantic dictates.
 
 In the end, the chosen solution is to now have web page themselves subject to filtering, just like all secondary resources.