diff --git a/Home.md b/Home.md
index 3aead9b..890599d 100644
--- a/Home.md
+++ b/Home.md
@@ -2,30 +2,30 @@
 	<img src="https://raw.githubusercontent.com/vmstan/gravity-sync/master/docs/gravity-header.svg" width="80%" alt="Gravity Sync">
 </p>
 
-What is better than a [Pi-hole](https://github.com/pi-hole/pi-hole) blocking ads via DNS on your network? That's right, two Pi-hole blocking ads on your network! 
+What is better than a [Pi-hole](https://github.com/pi-hole/pi-hole) blocking ads via DNS on your network? That's right, **two** Pi-hole blocking ads on your network! 
 
-- [Seriously, Why?](https://github.com/vmstan/gravity-sync/wiki/Frequent-Questions#why-do-i-need-more-than-one-pi-hole)
+- [Seriously. Why two Pi-hole?](https://github.com/vmstan/gravity-sync/wiki/Frequent-Questions#why-do-i-need-more-than-one-pi-hole)
 
 But if you have more than one Pi-hole in your network you'll want a simple way to keep the list configurations and local DNS settings identical between the two. That's Gravity Sync. With proper preparation it should only take a few minutes to install. Ideally you set up Gravity Sync and forget about it -- and in the long term, it would be awesome if the Pi-hole team made this entire script unnecessary.
 
 # Features
 
-Gravity Sync the `gravity.db` database which includes:
+Gravity Sync replicates the `gravity.db` database, which includes:
 - Blocklist settings with status and comments.
 - Domain whitelist and blacklist along with status with comments.
 - Custom RegEx whitelist and blacklists.
 - Clients and groups along with any list assignments.
-- The Local DNS Settings feature in Pi-hole (These are stored in a separate `custom.list` file and this can optionally be disabled.)
+- Local DNS Settings (These are stored in a separate `custom.list` file and can optionally be disabled.)
 
 ### Limitations
 
 Gravity Sync will **not**:
 
-- Overwrite or sync device specific Pi-hole settings such as the local network configuration.
-- Overwrite or sync the Pi-hole admin/API passwords, nor does not leverage these at all.
-- Overwrite or sync the upstream DNS resolvers, etc.
-- Overwrite or sync DHCP settings or device leases synchronized.
-- Overwrite or sync long term data, query logs, or statistics.
+- Overwrite device specific Pi-hole settings specific to the local network configuration.
+- Change the Pi-hole admin/API passwords, nor does not leverage these at all.
+- Modify the individual Pi-hole's upstream DNS resolvers.
+- Sync DHCP settings or monitor device leases.
+- Merge long term data, query logs, or statistics.
 
 # Setup Steps