updating dqkd docs

Author: mmandichqrypt

content/DQKD/_index.md

@@ -11,7 +11,7 @@ disableToc = "true"
 DQKD is a functional and easy-to-set-up alternative to [QKD](https://www.nsa.gov/Cybersecurity/Quantum-Key-Distribution-QKD-and-Quantum-Cryptography-QC/), aiming to attain the level of security granted by QKD with a fraction of the deployment cost. We do so by using Qrypt's [BLAST](https://www.qrypt.com/wp-content/uploads/2022/03/Whitepaper-EverlastingSecurity.pdf#page=9) technology to generate key material safely at the endpoints. Unlike standard QKD, Qrypt's BLAST-based QKD removes the need for specialized instalations such as satalite and fiber optic.
 ## How it works:
 ### From the User Perspective (simplest example)
-1. Alice wants to generate symmetric keys with bob, without sending the key material directly between her and Bob
+1. Alice wants to generate symmetric keys with Bob, without sending the key material directly between her and Bob
 
 2. Using her cert from Qrypt, and the ID of Bob's Key Management Entity (KME), Alice calls the API for a single key.
 
@@ -23,7 +23,7 @@ DQKD is a functional and easy-to-set-up alternative to [QKD](https://www.nsa.gov
 
 5. Bob then sends a request to his KME through the same API to replicate the key. 
 
-6. From his on-site KME, Bob then recieves the key material that was generated by Alice, and can then use that material to sensitive data to Alice.
+6. From his on-site KME, Bob then recieves the key material that was generated by Alice, and can then use that material to send sensitive data to Alice.
 See graphic below for a visual. 
 
 ![FullPage](images/dqkddiagram.svg)