diff --git a/knowledge-base/moneropedia/eepsite.md b/knowledge-base/moneropedia/eepsite.md
index d07173d6..ddfd3dee 100644
--- a/knowledge-base/moneropedia/eepsite.md
+++ b/knowledge-base/moneropedia/eepsite.md
@@ -10,7 +10,7 @@ summary: "A website or service hosted within the I2P network"
 
 Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different?
 
-While the original definition of eepsite has been lost with time, its use-case remains: a website or service that is hosted within (and only accessible by) the @I2P network.
+While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network.
 
 ### In-depth Information
 
@@ -27,4 +27,4 @@ Alternate names include:
 
 ### Notes
 
-To learn how to setup an Eeepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
+To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
diff --git a/knowledge-base/moneropedia/garlic-routing.md b/knowledge-base/moneropedia/garlic-routing.md
index bc2fe510..cdcd7d8a 100644
--- a/knowledge-base/moneropedia/garlic-routing.md
+++ b/knowledge-base/moneropedia/garlic-routing.md
@@ -8,15 +8,15 @@ summary: "Routing technology as implemented in Kovri/I2P"
 
 ### The Basics
 
-The term *Garlic Routing* has a diverse history with various interpretations.
+The term *Garlic Routing* has a diverse history of varying interpretations.
 
-As it currently stands, Monero defines *Garlic Routing* as the way @Kovri and @I2P create a message-based anonymous overlay network of internet peers.
+As it currently stands, Monero defines *Garlic Routing* as the method in which @Kovri and @I2P create a message-based anonymous overlay network of internet peers.
 
 ### History
 
-I written form, the term *Garlic Routing* can be seen as early as June of 2000 in Roger Dingledine's [Free Haven Master's thesis](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from [Onion Routing](http://www.onion-router.net/).
+In written form, the term *Garlic Routing* can be seen as early as June of 2000 in Roger Dingledine's [Free Haven Master's thesis](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term [Onion Routing](http://www.onion-router.net/).
 
-As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term:
+As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *Garlic Routing*:
 
 Nick Mathewson:
 >[I think that there was some attempt to come up with a plant whose structure resembled the 'leaky-pipe' topology of tor, but I don't believe we ever settled on one.]
@@ -37,5 +37,5 @@ Note: as seen in [Tor](https://torproject.org/), *Onion Routing* also uses layer
 
 ### Notes
 
-- Permission received from Nick Mathewson and Roger Dingledine for historical quotes
-- For more technical details, read [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing).
+- Permission to use the aforementioned quotes granted by Nick Mathewson and Roger Dingledine
+- For more technical details, read [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing)