Fix incorrectly wrapped lines in readmes

diff --git a/alternates/fakenews-gambling-porn-social/readme.md b/alternates/fakenews-gambling-porn-social/readme.md
index 774f97c75abad153da9d3c5b47e168633528b4fe..509e918b7afa5305205d2c8ea98098fc962743bb 100644 (file)
--- a/alternates/fakenews-gambling-porn-social/readme.md
+++ b/alternates/fakenews-gambling-porn-social/readme.md
@@ -175,9 +175,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -311,8 +311,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/fakenews-gambling-porn/readme.md b/alternates/fakenews-gambling-porn/readme.md
index 03c1cbac630292adc18788ba5da4b77aa324a3e6..840b9e0b66c23dc286e08dbbf79c3cc5f3cfa555 100644 (file)
--- a/alternates/fakenews-gambling-porn/readme.md
+++ b/alternates/fakenews-gambling-porn/readme.md
@@ -174,9 +174,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -310,8 +310,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/fakenews-gambling-social/readme.md b/alternates/fakenews-gambling-social/readme.md
index 7dde2b2f233eab6fec9280778eecd471cadbe129..d83310c2101cd82d511490e12714aa10efbe3828 100644 (file)
--- a/alternates/fakenews-gambling-social/readme.md
+++ b/alternates/fakenews-gambling-social/readme.md
@@ -173,9 +173,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -309,8 +309,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/fakenews-gambling/readme.md b/alternates/fakenews-gambling/readme.md
index 739d07ed31e0663ddee4cf795fd972e5d85ab710..6fe6c215c56b0309d9e8cd99aa73cfa9f9998450 100644 (file)
--- a/alternates/fakenews-gambling/readme.md
+++ b/alternates/fakenews-gambling/readme.md
@@ -172,9 +172,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -308,8 +308,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/fakenews-porn-social/readme.md b/alternates/fakenews-porn-social/readme.md
index 1709f3b30afcae9fabf33a6bb1fdbb1d28a040e0..b197daf475f661a54b9388d43d9b5e349846af7a 100644 (file)
--- a/alternates/fakenews-porn-social/readme.md
+++ b/alternates/fakenews-porn-social/readme.md
@@ -174,9 +174,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -310,8 +310,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/fakenews-porn/readme.md b/alternates/fakenews-porn/readme.md
index 1713ecf4407e5383d62f012ec7077729772f4eb8..9a00fbd1fa833e57fa708900c05b11548c655fc3 100644 (file)
--- a/alternates/fakenews-porn/readme.md
+++ b/alternates/fakenews-porn/readme.md
@@ -173,9 +173,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -309,8 +309,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/fakenews-social/readme.md b/alternates/fakenews-social/readme.md
index f8d8c8cebfb05be829cece522ef4d131da65ab4a..917f5f4605fa6208783681cc020406190bfb76a4 100644 (file)
--- a/alternates/fakenews-social/readme.md
+++ b/alternates/fakenews-social/readme.md
@@ -172,9 +172,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -308,8 +308,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/fakenews/readme.md b/alternates/fakenews/readme.md
index 4a59de6355dad293bd150ba099be14e6146df1e0..0bbb5cba8f37146bbd0bf10094420152a1bf67e4 100644 (file)
--- a/alternates/fakenews/readme.md
+++ b/alternates/fakenews/readme.md
@@ -171,9 +171,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -307,8 +307,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/gambling-porn-social/readme.md b/alternates/gambling-porn-social/readme.md
index 92eaeaca955b0e38bb914e084b4f7d3b3309f167..67ad29b5bfcfda0aa87cc2bb8073d68d51bcb1ed 100644 (file)
--- a/alternates/gambling-porn-social/readme.md
+++ b/alternates/gambling-porn-social/readme.md
@@ -174,9 +174,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -310,8 +310,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/gambling-porn/readme.md b/alternates/gambling-porn/readme.md
index bcc24e8b1ae0fedbb54643f6eece23855649617e..8c3a3e7761e57acb7b70d8a5d61a810332bcc59f 100644 (file)
--- a/alternates/gambling-porn/readme.md
+++ b/alternates/gambling-porn/readme.md
@@ -173,9 +173,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -309,8 +309,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/gambling-social/readme.md b/alternates/gambling-social/readme.md
index 9c7f2eedc7d753f3df0e26f301d99bb78569d125..cfe525f86490ab0518a2ad91ee9f38cc886c8b89 100644 (file)
--- a/alternates/gambling-social/readme.md
+++ b/alternates/gambling-social/readme.md
@@ -172,9 +172,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -308,8 +308,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/gambling/readme.md b/alternates/gambling/readme.md
index 5c144800134e47a33a39e69aa9113ae9811086cf..e207fb7250d2266c6831c3164cfe34a4f870c2fb 100644 (file)
--- a/alternates/gambling/readme.md
+++ b/alternates/gambling/readme.md
@@ -171,9 +171,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -307,8 +307,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/porn-social/readme.md b/alternates/porn-social/readme.md
index 08f49988615504a09ee5bf922a7e91ef073c0daa..2f7fff75823edc8c82f9551605b139cfa4fdfc8a 100644 (file)
--- a/alternates/porn-social/readme.md
+++ b/alternates/porn-social/readme.md
@@ -173,9 +173,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -309,8 +309,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/porn/readme.md b/alternates/porn/readme.md
index c3907b7ed436f8b61afda0679373a64e93f59ce5..78380e390425e24c5a3e34b610d231d3d53a59f6 100644 (file)
--- a/alternates/porn/readme.md
+++ b/alternates/porn/readme.md
@@ -172,9 +172,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -308,8 +308,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/alternates/social/readme.md b/alternates/social/readme.md
index c4fbd2c98dd2f8f55e721eb0bfad87020b1ad1b8..3930674353332262e251b80d50b98e5b7705b332 100644 (file)
--- a/alternates/social/readme.md
+++ b/alternates/social/readme.md
@@ -171,9 +171,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -307,8 +307,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/readme.md b/readme.md
index 152d009a9a34414d1f6972ded10fe3550e6377ed..c8406ef9959a987079d505a0fd32d78d57cf239b 100644 (file)
--- a/readme.md
+++ b/readme.md
@@ -170,9 +170,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -306,8 +306,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile

diff --git a/readme_template.md b/readme_template.md
index a3c9dd507d786cfd5f9ae927ad3495eec7aa79e7..3f96b662501c06bc8a06c87bdcad7291f0a966be 100644 (file)
--- a/readme_template.md
+++ b/readme_template.md
@@ -139,9 +139,9 @@ overridden when you `git pull` this repo from `origin` in the future.
 The domains you list in the `whitelist` file are excluded from the final hosts
 file.
 
-The `whitelist` uses partial matching.  Therefore if you whitelist `google-
-analytics.com`, that domain and all its subdomains won't be merged into the
-final hosts file.
+The `whitelist` uses partial matching.  Therefore if you whitelist
+`google-analytics.com`, that domain and all its subdomains won't be merged
+into the final hosts file.
 
 The `whitelist` is not tracked by git, so any changes you make won't be
 overridden when you `git pull` this repo  from `origin` in the future.
@@ -275,8 +275,8 @@ hosts source should be frequently updated by its maintainers with both
 additions and removals.  The larger the hosts file, the higher the level of
 curation is expected.
 
-For example, the (huge) hosts file from [hosts-file.net](http://hosts-
-file.net) is **not** included here because it is very large (300,000+ entries)
+For example, the (huge) hosts file from [hosts-file.net](http://hosts-file.net)
+is **not** included here because it is very large (300,000+ entries)
 and doesn't currently display a corresponding high level of curation activity.
 
 It is expected that this unified hosts file will serve both desktop and mobile