Update README.md

README.md

@@ -2,7 +2,7 @@
 
 ## Motivation
 
-I have various mass-storage NFS/SMB shares which are only available locally, moreover I have strict firewall rules in place to only allow SSH access to my servers from within the same broadcast zone.
+I have various mass-storage NFS/SMB shares which are only available locally, moreover I have strict firewall rules in place to only allow SSH access to my servers from within the same broadcast domain.
 
 Though secure, this imposes the obvious limitation of only being able to access said servers or shares when I'm at home.
 
@@ -49,7 +49,7 @@ For this task, WireGuard's cryptography, asymmetric key-pairing and minimal over
 
 - Support for Dynamic home IP addresses via [BashDDNS](https://git.tobiastime.xyz/Tobias/BashDDNS), and specifying a domain name as the endpoint for the client
 
-- Lightweight, with a dedicated virtual machine requiring less than 256MB of RAM
+- Lightweight, with a dedicated virtual machine requiring less than 256Mi of RAM
 
 - Secure through WireGuard's dual-key asymmetric [cryptography](https://www.wireguard.com/protocol/)
 
@@ -89,17 +89,17 @@ Persistent Keep Alive will send a dummy packet every 25 seconds to maintain a co
 
 ## Extremely useful Linux tools in debugging
 
-- tcpdump
+- tcpdump for packet inspection and capture
 
-- nmap
+- nmap for verifying a UDP port is open on a remote host
 
-- ss
+- ss for verifying the WireGuard service is bound to and listening on UDP port 51820
 
-- wg
+- wg for displaying the current interface and client configuration
 
-- ip
+- ip to display the current addressses of your physical and virutal interfaces
 
-- ping
+- ping for sending ICMP echo requests to verify client connectivity to the virtual WireGuard interface and local resources
 
 ## Extremely useful documentation