Update README.md

README.md

@@ -1,5 +1,5 @@
 # A simple low-level DNS resolver
-This project consists of a DNS server written from scratch in Rust, based on RFCs 1034 and 1035. The server listens for a stream of bytes representing the DNS message on a UDP port, decodes it, looks for a resource record (RR) matching the query, and returns the encoded information back to the origin. The resource record is currently being held in records.json.
+This project consists of a DNS server written from scratch in Rust, based on RFCs [1034](https://www.rfc-editor.org/rfc/rfc1034) and [1035](https://www.rfc-editor.org/rfc/rfc1035). The server listens for a stream of bytes representing the DNS message on a UDP port, decodes it, looks for a resource record (RR) matching the query, and returns the encoded information back to the origin. The resource record is currently being held in records.json.
 
 The server can be run by passing the port as an argument. You can pick any as long as it's not being used or reserved.
 ```bash
@@ -11,13 +11,13 @@ Its functionality can be tested with a tool like `dig` on localhost and the spec
 dig +retry=0 -p 1053 @127.0.0.1 +noedns example.com A
 ```
 ## Records
-`A` records for amazon.co.uk stored in `records.json`.
+`A` records for amazon.co.uk as stored in `records.json`.
 <figure>
   <img src="media/records-json.png" alt="" height="200" />
 </figure>
 
 ## Input and output stream
-Stream of bytes from the query and the response message sent back to the origin. As we can see, one response has been sent for each RR, which corresponds to the ones in `records.json`. 
+Stream of bytes from the query and the response messages transmitted. As we can see, the response bytes are based on the request and there's one answer for each RR, corresponding to the ones defined in `records.json`. 
 <figure>
   <img src="media/server-logs.png" alt="" height="100" />
 </figure>