aboutsummaryrefslogtreecommitdiff
path: root/doc/dnsseed-policy.md
diff options
context:
space:
mode:
authorJason Lewicki <lewicki.jason@gmail.com>2015-03-13 20:55:52 +0000
committerWladimir J. van der Laan <laanwj@gmail.com>2015-04-20 13:29:21 +0200
commit468aa3bf0a61f721302d98be4a21fb99d4bc7538 (patch)
tree89a02ed7537fe104cff33a0e77f93f8a2c3c4ec7 /doc/dnsseed-policy.md
parent71ad6bd38b0f3854a03d69c0bf3e83a1e4d95a56 (diff)
Re-wrote a passage of text that was difficult to understand.
Diffstat (limited to 'doc/dnsseed-policy.md')
-rw-r--r--doc/dnsseed-policy.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/dnsseed-policy.md b/doc/dnsseed-policy.md
index 66a1757ac5..f15ff44e5d 100644
--- a/doc/dnsseed-policy.md
+++ b/doc/dnsseed-policy.md
@@ -7,9 +7,8 @@ As such, DNS seeds must be run by entities which have some minimum
level of trust within the Bitcoin community.
Other implementations of Bitcoin software may also use the same
-seeds and may be more exposed. In light of this exposure this
-document establishes some basic expectations for the expectations
-for the operation of dnsseeds.
+seeds and may be more exposed. In light of this exposure, this
+document establishes some basic expectations for operating dnsseeds.
0. A DNS seed operating organization or person is expected
to follow good host security practices and maintain control of