Make usage of 2-word Address Book consistent across website, except preserve old blog posts as is
This commit is contained in:
@ -832,9 +832,9 @@ abstraction of TCP, with its sliding windows, congestion control algorithms
|
||||
SYN, FIN, RST, etc).
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h2 id="app.naming">{% trans %}Naming library and addressbook{% endtrans %}</h2>
|
||||
<h2 id="app.naming">{% trans %}Naming library and address book{% endtrans %}</h2>
|
||||
<p><i>{% trans naming=site_url('docs/naming') -%}
|
||||
For more information see the <a href="{{ naming }}">Naming and Addressbook</a> page.
|
||||
For more information see the <a href="{{ naming }}">Naming and Address Book</a> page.
|
||||
{%- endtrans %}</i></p>
|
||||
|
||||
<p><i>{% trans dev='mihi, Ragnarok' -%}Developed by: {{ dev }}{%- endtrans %}</i></p>
|
||||
@ -846,16 +846,16 @@ inherent demand for secure communication and decentralized operation, the
|
||||
traditional DNS-style naming system is clearly out, as are "majority rules"
|
||||
voting systems. Instead, I2P ships with a generic naming library and a base
|
||||
implementation designed to work off a local name to destination mapping, as
|
||||
well as an optional add-on application called the "addressbook". The addressbook
|
||||
well as an optional add-on application called the "Address Book". The address book
|
||||
is a web-of-trust-driven secure, distributed, and human readable naming system,
|
||||
sacrificing only the call for all human readable names to be globally unique
|
||||
by mandating only local uniqueness. While all messages in I2P are cryptographically
|
||||
addressed by their destination, different people can have local addressbook
|
||||
addressed by their destination, different people can have local address book
|
||||
entries for "Alice" which refer to different destinations. People can still
|
||||
discover new names by importing published addressbooks of peers specified
|
||||
discover new names by importing published address books of peers specified
|
||||
in their web of trust, by adding in the entries provided through a third party,
|
||||
or (if some people organize a series of published addressbooks using a first
|
||||
come first serve registration system) people can choose to treat these addressbooks
|
||||
or (if some people organize a series of published address books using a first
|
||||
come first serve registration system) people can choose to treat these address books
|
||||
as name servers, emulating traditional DNS.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
|
Reference in New Issue
Block a user