mirror of
https://github.com/StevenBlack/hosts.git
synced 2026-07-01 02:36:52 +00:00
Fix incorrectly wrapped lines in readmes
This commit is contained in:
Jakub Wilk
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
10
readme.md
10
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
|
||||
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user