From: Jakub Wilk Date: Sun, 16 Apr 2017 06:47:09 +0000 (+0200) Subject: Fix incorrectly wrapped lines in readmes X-Git-Url: http://git.99rst.org/?a=commitdiff_plain;h=126be6e9ecb1faaaf699a4d0a3dbf1cdeeea1708;p=stevenblack-hosts.git 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 774f97c75..509e918b7 100644 --- 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 03c1cbac6..840b9e0b6 100644 --- 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 7dde2b2f2..d83310c21 100644 --- 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 739d07ed3..6fe6c215c 100644 --- 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 1709f3b30..b197daf47 100644 --- 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 1713ecf44..9a00fbd1f 100644 --- 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 f8d8c8ceb..917f5f460 100644 --- 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 4a59de635..0bbb5cba8 100644 --- 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 92eaeaca9..67ad29b5b 100644 --- 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 bcc24e8b1..8c3a3e776 100644 --- 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 9c7f2eedc..cfe525f86 100644 --- 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 5c1448001..e207fb725 100644 --- 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 08f499886..2f7fff758 100644 --- 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 c3907b7ed..78380e390 100644 --- 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 c4fbd2c98..393067435 100644 --- 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 152d009a9..c8406ef99 100644 --- 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 a3c9dd507..3f96b6625 100644 --- 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