From da08a18e84c5555d2306d29b82dec34d422dd09e Mon Sep 17 00:00:00 2001 From: George Date: Mon, 27 Jan 2020 08:06:48 -0500 Subject: [PATCH] Fix typos --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index f1fc13b..9175317 100644 --- a/README.md +++ b/README.md @@ -8,15 +8,15 @@ Having a naming system is a common requirement for deploying preexisting decentralized applications. Protocols like e-mail, XMPP and ActivityPub require domain names for server to server communications. -Self-organized and trustless networks like CJDNS and Yggdrasil Network are -using public-key cryptography for IP address allocation. Every network node owns +Self-organized networks like CJDNS and Yggdrasil Network use public-key +cryptography for IP address allocation. Every network node owns a globally unique IPv6 address. Binary form of that address can be encoded with base32 notation for deriving a globally unique name space managed by that node. Since there is no need for a global authority or consensus, such a naming system will reliably work in any network split scenarios. -".mesh.arpa" is ment to be used by machines, not by humans. A human-readable +".mesh.arpa" is meant to be used by machines, not by humans. A human-readable naming system would require a lot more engineering effort. ## How .mesh.arpa domains work