diff --git a/src/development/messages/relaying/overview.md b/src/development/messages/relaying/overview.md
index 37694b9..ce3b5eb 100644
--- a/src/development/messages/relaying/overview.md
+++ b/src/development/messages/relaying/overview.md
@@ -4,12 +4,12 @@ Relaying Messages can be done one of three ways:
 
 1. Manual Relaying 
     
-    Manual Relaying is usally done on the front end, and has the front end fetch the VAA it just created and then submit on the target chain. This means the user ends up paying for the gas fee to submit the tx on the target chain and has to go through the additional step. 
+    Manual Relaying is usally done on the front end.  Manual relyaing requires the front end to fetch the VAA it just created and then submit on the target chain. This means the user ends up paying for the gas fee and has to go through the additional step to submit the tx on the target chain. 
 
 2. Protocol Specific Relayers
 
-    Protocols and Apps can run their own relayers, listening to messages as they are created by the Core Bridge and submitting them to their application on the target chain. This is the ideal user experience but means more work for the developer.
+    Protocols and Apps can run their own relayers, listening to messages as they are created by the Core Bridge and submitting them to their application on the target chain. This is the ideal user experience but requires more work from the developer.
 
 3. Generic Relayers
 
-    Generic Relayers can pick up any app or protocol's messages and submit them to the target chain for a fee. This is the ideal developer and user experience, but still being developed. 
\ No newline at end of file
+    Generic Relayers can pick up any app or protocol's messages and submit them to the target chain for a fee. This is the ideal developer and user experience, but is still being developed.