From c1d6f0556775d24fbe998a3b8d21e666ff4fc67d Mon Sep 17 00:00:00 2001
From: laylavish <128162304+laylavish@users.noreply.github.com>
Date: Mon, 8 Jan 2024 09:30:52 -0500
Subject: [PATCH] Update README.md

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index d8cc932..1a75c5b 100644
--- a/README.md
+++ b/README.md
@@ -42,8 +42,9 @@ I created a [repo that houses good tips & tricks for Google Search's operators](
 
 ## Q&A 
 
-Q: Why isn't the whole element being removed? 
-A: With this implementation, it preserves the ability to continuously scroll through Google Images without being blocked. See, if you outright block a website and remove its element from view (the traditional way), and your query returns too many images that are from your blocklist, Google Images will not allow you to scroll any farther than just the first few rows of images. What this implementation is doing here is setting the offending website's opacity to zero, which essentially blocks it. Doing it in this way bypasses the limitation from before, but it can look disorganized compared to the former.
+**Q**: Why isn't the whole element being removed? 
+
+**A**: With this implementation, it preserves the ability to continuously scroll through Google Images without being blocked. See, if you outright block a website and remove its element from view (the traditional way), and your query returns too many images that are from your blocklist, Google Images will not allow you to scroll any farther than just the first few rows of images. What this implementation is doing here is setting the offending website's opacity to zero, which essentially blocks it. Doing it in this way bypasses the limitation from before, but it can look disorganized compared to the former.
 
 ## Special thanks