From d401cf09456c7bb15483c81d7f76a9db6beb0234 Mon Sep 17 00:00:00 2001
From: TheFrenchGhosty <47571719+TheFrenchGhosty@users.noreply.github.com>
Date: Sun, 13 Mar 2022 16:07:13 +0000
Subject: [PATCH] Takedown-Notices - Enhancement and typos fixes

---
 docs/Takedown-Notices.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/Takedown-Notices.md b/docs/Takedown-Notices.md
index 88c1d7c..924ad07 100644
--- a/docs/Takedown-Notices.md
+++ b/docs/Takedown-Notices.md
@@ -1,8 +1,8 @@
 # Takedown Notices
 
-While running Invidious, it is very possible you will receive a takedown notice at some point. A copyright agent will probably search the ID of an infringing video on a search engine and see an Invidious instance appear. At least in the United States and in Europe, Invidious instances should in theory be immune those kind of takedown.
+If you are running a public Invidious instance, it is very possible that you will end up receiving a takedown notice at some point. A copyright agent will probably search the ID of an infringing video on a search engine and see your instance appear. At least in the United States and in Europe, Invidious instances are, in theory, legal.
 
-Do note that most requests are invalid and technically illegal since they aren't sent by a lawyer, so you can, in theory, never replies to them (unless they are a company/law firm). If you want to be safe you can obviously counter to all of them.
+Do note that most requests are invalid and technically illegal since they aren't sent by a lawyer, so you can, in theory, never reply to them (unless they are a company/law firm). If you want to be safe you can obviously counter all of them.
 
 To counter them "easily", we decided to provide templates depending on where your instance is located.