Merge pull request #1220

Remove all I2P-related entries from zh-tw and zh-cn languages + Remove links to deleted Moneropedia entries from other resources

_i18n/ar/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/ar/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
 
 These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
 
-Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
 
-- @Kovri does not use exit nodes when connecting to an @eepsite
+- @Kovri does not use exit nodes when connecting to an eepsite
-- Your traffic never need to leave the @I2P network
+- Your traffic never need to leave the I2P network
-- You do not need HTTPS to use @Kovri (with the exception of @reseed)
+- You do not need HTTPS to use @Kovri (with the exception of reseed)

_i18n/ar/resources/moneropedia/encryption.md

@@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
 @Kovri implements various types of encryption in *at least* 4 essential capacities:
 
 - @Reseed for bootstrapping
-- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
-- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
-- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
 
-For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
+For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)

_i18n/ar/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
 
 You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
 
-Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/de/resources/moneropedia/canonically-unique-host.md

@@ -19,4 +19,4 @@ Ein kanonisch einzigartiger Host wird durch rechnerferne, maßgebende Quellen de
 ### Anmerkungen
 
 - Monero nutzt primär die Auflösung des kanonisch einzigartigen Hosts, während I2P ausschließlich die Auflösung des @Lokal-einzigartigen-Hosts verwendet.
-- Die an I2P und @Kovri zugewiesene Top-Level-Domain ist derzeit `.i2p`; @Kovri beabsichtigt, einzig die `.i2p`-[Top-Level-Domain](https://de.wikipedia.org/wiki/Top-Level-Domain) zu nutzen und zu verarbeiten.
+- Die an I2P und @Kovri zugewiesene Top-Level-Domain ist derzeit `.i2p`; @Kovri beabsichtigt, einzig die `.i2p`-[Top-Level-Domain](https://de.wikipedia.org/wiki/Top-Level-Domain) zu nutzen und zu verarbeiten.

_i18n/de/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
 
 You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
 
-Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/en/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/en/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
 
 These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
 
-Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
 
-- @Kovri does not use exit nodes when connecting to an @eepsite
+- @Kovri does not use exit nodes when connecting to an eepsite
-- Your traffic never need to leave the @I2P network
+- Your traffic never need to leave the I2P network
-- You do not need HTTPS to use @Kovri (with the exception of @reseed)
+- You do not need HTTPS to use @Kovri (with the exception of reseed)

_i18n/en/resources/moneropedia/encryption.md

@@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
 @Kovri implements various types of encryption in *at least* 4 essential capacities:
 
 - @Reseed for bootstrapping
-- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
-- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
-- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
 
-For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
+For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)

_i18n/en/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
 
 You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
 
-Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/es/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/es/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
 
 These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
 
-Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
 
-- @Kovri does not use exit nodes when connecting to an @eepsite
+- @Kovri does not use exit nodes when connecting to an eepsite
-- Your traffic never need to leave the @I2P network
+- Your traffic never need to leave the I2P network
-- You do not need HTTPS to use @Kovri (with the exception of @reseed)
+- You do not need HTTPS to use @Kovri (with the exception of reseed)

_i18n/es/resources/moneropedia/encryption.md

@@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
 @Kovri implements various types of encryption in *at least* 4 essential capacities:
 
 - @Reseed for bootstrapping
-- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
-- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
-- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
 
-For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
+For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)

_i18n/es/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
 
 You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
 
-Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/fr/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ Un hôte canonique unique est défini par des sources autoritaires distantes, co
 
 ### Remarques
 
-- Monero utilise en premier lieu la résolution de @hôte-canonique-unique alors que @I2P utilise uniquement la résolution d'@hôte-unique-localement.
+- Monero utilise en premier lieu la résolution de @hôte-canonique-unique alors que I2P utilise uniquement la résolution d'@hôte-unique-localement.
-- le domaine de premier niveau auto-attribué de @I2P et @Kovri est actuellement `.i2p` et @Kovri se destine à n'utiliser et ne traiter que le [domaine de premier niveau](https://fr.wikipedia.org/wiki/Top_level_domain) `.i2p`.
+- le domaine de premier niveau auto-attribué de I2P et @Kovri est actuellement `.i2p` et @Kovri se destine à n'utiliser et ne traiter que le [domaine de premier niveau](https://fr.wikipedia.org/wiki/Top_level_domain) `.i2p`.

_i18n/fr/resources/moneropedia/clearnet.md

@@ -20,13 +20,13 @@ et même si vous utilisez [HTTPS](https://fr.wikipedia.org/wiki/HyperText_Transf
 Comme un [VPN](https://fr.wikipedia.org/wiki/R%C3%A9seau_priv%C3%A9_virtuel) traditionnel ne peut pas vous épargner du réseau en clair (comme vous utilisez toujours le réseau en clair (bien que vous soyez mieux mandaté que sans un VPN)), vous devriez utiliser une *surcouche réseau anonyme* pour éviter d'utiliser le réseau en clair directement :
 
 - @Kovri
-- @I2P-Java
+- I2P-Java
 - [Tor](https://torproject.org/)
 
 Ces technologies vous protègent du réseau en clair en construisant un réseau anonyme **par dessus** le réseau en clair pour garder vos transmissions à la fois chiffrées **et** anonymes.
 
-Voici un [diagramme interactif](https://www.eff.org/pages/tor-and-https) précis fournit par l'[EFF](https://www.eff.org/) qui décrit comment **Tor** se relie au *réseau en clair*. Le principe est également applicable (en partie) à @Kovri et @I2P en termes d'anonymat, à l'exception des points suivants :
+Voici un [diagramme interactif](https://www.eff.org/pages/tor-and-https) précis fournit par l'[EFF](https://www.eff.org/) qui décrit comment **Tor** se relie au *réseau en clair*. Le principe est également applicable (en partie) à @Kovri et I2P en termes d'anonymat, à l'exception des points suivants :
 
 - @Kovri n'utilise pas de nœud de sortie lors d'une connexion à un @site-eep
-- Votre trafic ne quite jamais le réseau @I2P
+- Votre trafic ne quite jamais le réseau I2P
 - Vous n'avez pas besoin de HTTPS pour utiliser @Kovri (à l'exception du @réensemencement)

_i18n/fr/resources/moneropedia/encryption.md

@@ -27,8 +27,8 @@ La sécurité d'un système de chiffrement doit reposer sur le secret de la clé
 @Kovri implémente différents types de chiffrements pour *au moins* 4 capacités essentielles :
 
 - @réensemencement pour amorce
-- @Routage-en-ail : trois niveau de chiffrement (@chiffrement-en-ail) sont utilisé pour vérifier la distribution sécurisée des @messages au destinataire ou homologue de @destination
+- @Routage-en-ail : trois niveau de chiffrement (@chiffrement-en-ail) sont utilisé pour vérifier la distribution sécurisée des messages au destinataire ou homologue de destination
-- Chiffrement de @Tunnel : les messages en ail sont envoyés à travers un @tunnel et chiffrés par la passerelle de ce @tunnel vers le point de terminaison du @tunnel
+- Chiffrement de @Tunnel : les messages en ail sont envoyés à travers un tunnel et chiffrés par la passerelle de ce tunnel vers le point de terminaison du tunnel
-- Une couche de @Transport chiffrée empêche la capacité à déchiffrer un @messages sur la [couche liaison](https://fr.wikipedia.org/wiki/Mod%C3%A8le_OSI)
+- Une couche de @Transport chiffrée empêche la capacité à déchiffrer un messages sur la [couche liaison](https://fr.wikipedia.org/wiki/Mod%C3%A8le_OSI)
 
-Pour plus de détails sur les types de chiffrement et les @signatures cryptographiques utilisez dans @Kovri et @I2P, consultez la page [Cryptographie](https://geti2p.net/spec/cryptography) d'@I2P-Java.
+Pour plus de détails sur les types de chiffrement et les @signatures cryptographiques utilisez dans @Kovri et I2P, consultez la page [Cryptographie](https://geti2p.net/spec/cryptography) d'I2P-Java.

_i18n/fr/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ Un hôte unique localement est un [FQDN](https://fr.wikipedia.org/wiki/FQDN) que
 
 Vous avez la possibilité de partager votre interprétation du mécanisme de résolution d'un hôte (p.ex. `localhost` est toujours résolu en `127.0.0.1`) mais la résolution n'est pas appliquée de manière canonique (p.ex. quelqu'un d'autre pourrait faire correspondre `localhost` à une adresse IP arbitraire).
 
-Les hôtes des souscriptions publiques peuvent être considérés comme des @hôtes-canoniques-uniques au sein du réseau @I2P, mais finalement vous êtes libre de les redéfinir selon vos désirs.
+Les hôtes des souscriptions publiques peuvent être considérés comme des @hôtes-canoniques-uniques au sein du réseau I2P, mais finalement vous êtes libre de les redéfinir selon vos désirs.
 
 ### Remarques
 
-- Monero utilise principalement la résolution d'@hôtes-canoniques-uniques alors que @I2P utilise uniquement la résolution d'@hôte-unique-localement.
+- Monero utilise principalement la résolution d'@hôtes-canoniques-uniques alors que I2P utilise uniquement la résolution d'@hôte-unique-localement.
-- Le domaine de premier niveau actuel d'@I2P et @Kovri est `.i2p` et @Kovri se destine à traiter / utiliser uniquement le [domaine de premier niveau](https://fr.wikipedia.org/wiki/Domaine_de_premier_niveau) `.i2p`.
+- Le domaine de premier niveau actuel d'I2P et @Kovri est `.i2p` et @Kovri se destine à traiter / utiliser uniquement le [domaine de premier niveau](https://fr.wikipedia.org/wiki/Domaine_de_premier_niveau) `.i2p`.

_i18n/it/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/it/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
 
 These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
 
-Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
 
-- @Kovri does not use exit nodes when connecting to an @eepsite
+- @Kovri does not use exit nodes when connecting to an eepsite
-- Your traffic never need to leave the @I2P network
+- Your traffic never need to leave the I2P network
-- You do not need HTTPS to use @Kovri (with the exception of @reseed)
+- You do not need HTTPS to use @Kovri (with the exception of reseed)

_i18n/it/resources/moneropedia/encryption.md

@@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
 @Kovri implements various types of encryption in *at least* 4 essential capacities:
 
 - @Reseed for bootstrapping
-- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
-- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
-- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
 
-For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
+For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)

_i18n/it/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
 
 You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
 
-Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/nl/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/nl/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
 
 These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
 
-Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
 
-- @Kovri does not use exit nodes when connecting to an @eepsite
+- @Kovri does not use exit nodes when connecting to an eepsite
-- Your traffic never need to leave the @I2P network
+- Your traffic never need to leave the I2P network
-- You do not need HTTPS to use @Kovri (with the exception of @reseed)
+- You do not need HTTPS to use @Kovri (with the exception of reseed)

_i18n/nl/resources/moneropedia/encryption.md

@@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
 @Kovri implements various types of encryption in *at least* 4 essential capacities:
 
 - @Reseed for bootstrapping
-- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
-- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
-- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
 
-For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
+For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)

_i18n/nl/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
 
 You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
 
-Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/pl/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ Zasadniczy unikalny host jest definiowany przez zdalne autorytatywne źródła,
 
 ### Adnotacje
 
-- Monero głównie używa zasadniczego unikalnego hosta, podczas gdy @I2P korzysta jedynie z @lokalnego-unikalnego-hosta.
+- Monero głównie używa zasadniczego unikalnego hosta, podczas gdy I2P korzysta jedynie z @lokalnego-unikalnego-hosta.
 - Własną przypisaną domeną najwyższego poziomu sieci I2P i Kovri jest obecnie `.i2p`, a Kovri planuje używać jedynie [domeny najwyższego poziomu] `.i2p`(https://en.wikipedia.org/wiki/Top_level_domain).

_i18n/pl/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ Ponieważ tradycyjna [VPN](https://en.wikipedia.org/wiki/VPN) nie uchroni cię o
 
 Powyższe technologie chronią przed clearnetem poprzez tworzenie anonimowej sieci **ponad** clearnetem, aby twoje transmisje były zaszyfrowane **i** anonimowe.
 
-Tutaj znajdziesz dokładny, [interaktywny diagram](https://www.eff.org/pages/tor-and-https) stworzony przez [EFF](https://www.eff.org/), który opisuje *clearnet* w porównaniu z siecią **Tor**. Pojęcie to odnosi się po części do sieci @Kovri i @I2P pod względem anonimowości, z poniższymi różnicami:
+Tutaj znajdziesz dokładny, [interaktywny diagram](https://www.eff.org/pages/tor-and-https) stworzony przez [EFF](https://www.eff.org/), który opisuje *clearnet* w porównaniu z siecią **Tor**. Pojęcie to odnosi się po części do sieci @Kovri i I2P pod względem anonimowości, z poniższymi różnicami:
 
-- @Kovri nie korzysta z węzłów wyjściowych przy połączeniu z @eepsite
+- @Kovri nie korzysta z węzłów wyjściowych przy połączeniu z eepsite
 - twoje obciążenie nigdy nie musi opuszczać sieć I2P
-- nie potrzebujesz HTTPS, aby używać Kovri (za wyjątkiem @reseeda).
+- nie potrzebujesz HTTPS, aby używać Kovri (za wyjątkiem reseeda).

_i18n/pl/resources/moneropedia/encryption.md

@@ -32,4 +32,4 @@ Celem szyfrowania jest zapewnienie, że jedynie osoba upoważniona do dostępu d
 - szyfrowanie @tunelowe: wiadomości "czosnkowe" są przesyłane przez @tunel i szyfrowane przez furtkę @tunelu aż do punktu końcowego @tunelu
 - szyfrowanie warstwy @transportowej zapobiega rozszyfrowaniu wiadomości w [warstwie medialnej](https://en.wikipedia.org/wiki/OSI_model)
 
-Aby dowiedzieć się więcej na temat rodzajów szyfrowania oraz @podpisów kryptograficznych używanych w @Kovri i @I2P, odwiedź stronę o  [kryptografii] @Java-I2P (https://geti2p.net/spec/cryptography).
+Aby dowiedzieć się więcej na temat rodzajów szyfrowania oraz @podpisów kryptograficznych używanych w @Kovri i I2P, odwiedź stronę o  [kryptografii] @Java-I2P (https://geti2p.net/spec/cryptography).

_i18n/pl/resources/moneropedia/locally-unique-host.md

@@ -13,7 +13,7 @@ Lokalnie unikalny host jest [Pełną, Jendoznaczną Nazwą Domenową](https://en
 
 Możesz podzielić się swoją interpretacją tego, jak ustalany jest host, np. `localhost` zawsze jest ustalony jako `127.0.0.1`, ale to ustalenie nie jest ogólnie egzekwowane (np. ktoś może przypisać `localhost` do dowolnego adresu IP).
 
-Hosty w publicznej subskrypcji mogą być uważane za @zasadnicze-unikalne-hosty wewnątrz sieci @I2P, jednak ostatecznie to od ciebie zależy, jak je zdefiniujesz.
+Hosty w publicznej subskrypcji mogą być uważane za @zasadnicze-unikalne-hosty wewnątrz sieci I2P, jednak ostatecznie to od ciebie zależy, jak je zdefiniujesz.
 
 ### Adnotacje
 

_i18n/pt-br/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/pt-br/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
 
 These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
 
-Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
 
-- @Kovri does not use exit nodes when connecting to an @eepsite
+- @Kovri does not use exit nodes when connecting to an eepsite
-- Your traffic never need to leave the @I2P network
+- Your traffic never need to leave the I2P network
-- You do not need HTTPS to use @Kovri (with the exception of @reseed)
+- You do not need HTTPS to use @Kovri (with the exception of reseed)

_i18n/pt-br/resources/moneropedia/encryption.md

@@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
 @Kovri implements various types of encryption in *at least* 4 essential capacities:
 
 - @Reseed for bootstrapping
-- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
-- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
-- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
 
-For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
+For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)

_i18n/pt-br/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
 
 You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
 
-Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/ru/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ summary: "Хост, который канонически разрешен к а
 
 ### Примечания
 
-- Monero в первую очередь использует принятие решение по @канонически-уникальному-хосту, в то время как @I2P использует только решение по @локально-уникальному-хосту.
+- Monero в первую очередь использует принятие решение по @канонически-уникальному-хосту, в то время как I2P использует только решение по @локально-уникальному-хосту.
-- Назначившим самого себя доменом @I2P и @Kovri верхнего уровня на данный момент является `.i2p`, @Kovri отвечает только за обработку / использование [домена верхнего уровня](https://en.wikipedia.org/wiki/Top_level_domain) `.i2p`.
+- Назначившим самого себя доменом I2P и @Kovri верхнего уровня на данный момент является `.i2p`, @Kovri отвечает только за обработку / использование [домена верхнего уровня](https://en.wikipedia.org/wiki/Top_level_domain) `.i2p`.

_i18n/ru/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ summary: "Интернет, в котором построены сети ано
 
 Эти технологии защитят вас от клирнета путём построения анонимной сети **поверх** самого клирнета, в результате чего передаваемые вами данные будут как зашифрованными, так **и** анонимными.
 
-Здесь вы можете увидеть [интерактивную диаграмму](https://www.eff.org/pages/tor-and-https), предоставленную [EFF](https://www.eff.org/) и описывающую, как работает *клирнет* и Tor. Эта концепция также (некоторым образом) применима к @Kovri и @I2P с точки зрения анонимности за исключением следующего:
+Здесь вы можете увидеть [интерактивную диаграмму](https://www.eff.org/pages/tor-and-https), предоставленную [EFF](https://www.eff.org/) и описывающую, как работает *клирнет* и Tor. Эта концепция также (некоторым образом) применима к @Kovri и I2P с точки зрения анонимности за исключением следующего:
 
-- @Kovri не использует выходных узлов при соединении с @eepsite
+- @Kovri не использует выходных узлов при соединении с eepsite
-- Ваш трафик никогда не выходит за пределы сети @I2P;
+- Ваш трафик никогда не выходит за пределы сети I2P;
 - Вам не нужен HTTPS, чтобы использовать @Kovri (за исключением Reseed).

_i18n/ru/resources/moneropedia/encryption.md

@@ -31,4 +31,4 @@ summary: "Процесс кодирования сообщений или инф
 - @туннельное шифрование - "чесночные" сообщения проходят через @туннель и шифруются @туннельным шлюзом до прибытия в конечную точку;
 - @шифрование-транспортного-уровня не позволяет расшифровать сообщения на [медийном уровне](https://en.wikipedia.org/wiki/OSI_model)
 
-Подробная информация по типам шифрования и криптографическим @подписям, используемым @Kovri и @I2P, содержится в разделе [Криптография](https://geti2p.net/spec/cryptography) на @Java-I2P.
+Подробная информация по типам шифрования и криптографическим @подписям, используемым @Kovri и I2P, содержится в разделе [Криптография](https://geti2p.net/spec/cryptography) на @Java-I2P.

_i18n/ru/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ summary: "Хост, определенный вами и разрешенный
 
 Вы можете поделиться собственной интерпретацией разрешения хоста (например, `localhost` всегда будет иметь разрешение `127.0.0.1`), но разрешение не является канонически принудительным (например, кто-то может присвоить значение `localhost` любому произвольному IP-адресу).
 
-В сети @I2P хосты в публичной подписке могут рассматриваться как канонически уникальные, однако в конечном счёте вы можете определять их так, как вам будет угодно.
+В сети I2P хосты в публичной подписке могут рассматриваться как канонически уникальные, однако в конечном счёте вы можете определять их так, как вам будет угодно.
 
 ### Примечания
 
-- Monero в первую очередь использует разрешение @канонически-уникального-хоста, в то время как @I2P использует только разрешение @локально-уникального-хоста.
+- Monero в первую очередь использует разрешение @канонически-уникального-хоста, в то время как I2P использует только разрешение @локально-уникального-хоста.
-- В настоящее время доменом верхнего уровня для @I2P's и @Kovri является `.i2p`, и @Kovri в перспективе будет только обрабатывать данные/использовать только [домена верхнего уровня](https://en.wikipedia.org/wiki/Top_level_domain) `.i2p`
+- В настоящее время доменом верхнего уровня для I2P's и @Kovri является `.i2p`, и @Kovri в перспективе будет только обрабатывать данные/использовать только [домена верхнего уровня](https://en.wikipedia.org/wiki/Top_level_domain) `.i2p`

_i18n/tr/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/tr/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
 
 These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
 
-Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
 
-- @Kovri does not use exit nodes when connecting to an @eepsite
+- @Kovri does not use exit nodes when connecting to an eepsite
-- Your traffic never need to leave the @I2P network
+- Your traffic never need to leave the I2P network
-- You do not need HTTPS to use @Kovri (with the exception of @reseed)
+- You do not need HTTPS to use @Kovri (with the exception of reseed)

_i18n/tr/resources/moneropedia/encryption.md

@@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
 @Kovri implements various types of encryption in *at least* 4 essential capacities:
 
 - @Reseed for bootstrapping
-- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
-- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
-- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
 
-For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
+For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)

_i18n/tr/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
 
 You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
 
-Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/zh-cn/resources/moneropedia/base32-address.md

@@ -6,7 +6,7 @@ summary: "Base32 encoded hash of a Base64 address"
 
 ### 基础知识
 
-Base32地址是一个@I2P地址的截短编码版本，Base32地址是 `.b32.i2p` 主机名的第一部分。
+Base32地址是一个I2P地址的截短编码版本，Base32地址是 `.b32.i2p` 主机名的第一部分。
 
 例如:
 
@@ -18,7 +18,7 @@ Base32地址是一个@I2P地址的截短编码版本，Base32地址是 `.b32.i2p
 
 ### 深度信息
 
-基本上，Base32地址是52个字符长的，@I2P网络@Base64地址的完整SHA-256哈希的 [Base32编码表示](https://en.wikipedia.org/wiki/Base32)。
+基本上，Base32地址是52个字符长的，I2P网络@Base64地址的完整SHA-256哈希的 [Base32编码表示](https://en.wikipedia.org/wiki/Base32)。
 
 ### 备注
 

_i18n/zh-cn/resources/moneropedia/base64-address.md

@@ -6,7 +6,7 @@ summary: "Base64 encoded I2P destination"
 
 ### 基础知识
 
-@Base64地址是由516个字符组成的 [Base64编码](https://en.wikipedia.org/wiki/Base64) @I2P @目标。@base64地址主要用于@地址薄、@跳转服务以及内部。
+@Base64地址是由516个字符组成的 [Base64编码](https://en.wikipedia.org/wiki/Base64) I2P @目标。base64地址主要用于@地址薄、@跳转服务以及内部。
 
 例如:
 
@@ -17,4 +17,4 @@ AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLE
 
 ### 深度信息
 
-有关@base64地址的更多详细信息，请参见@目标
+有关base64地址的更多详细信息，请参见@目标

_i18n/zh-cn/resources/moneropedia/canonically-unique-host.md

@@ -19,5 +19,5 @@ summary: "A host that is canonically resolved to an address or set of addresses"
 
 ### 备注
 
-- 门罗币主要使用@标准唯一主机解析，而@I2P只使用@本地唯一主机解析。
+- 门罗币主要使用@标准唯一主机解析，而I2P只使用@本地唯一主机解析。
-- @I2P和@Kovri的自定义顶级域名当前为`.i2p`，@Kovri只打算处理/使用 `.i2p` [顶级域名](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P和@Kovri的自定义顶级域名当前为`.i2p`，@Kovri只打算处理/使用 `.i2p` [顶级域名](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/zh-cn/resources/moneropedia/clearnet.md

@@ -25,9 +25,9 @@ summary: "The Internet in which anonymous overlay networks are built upon"
 
 这些技术通过在明网上建立一个匿名网络，从而使您的传输经过加密**并**匿名，以从明网中保护你，
 
-这是一个由[EFF](https://www.eff.org/pages/tor&https)提供的准确的[交互式图表](https://www.eff.org/)，它描述了*明网*与**洋葱路由器**的关系。这个概念也(在一定程度上)适用于@Kovri和@I2P的匿名性，除了:
+这是一个由[EFF](https://www.eff.org/pages/tor&https)提供的准确的[交互式图表](https://www.eff.org/)，它描述了*明网*与**洋葱路由器**的关系。这个概念也(在一定程度上)适用于@Kovri和I2P的匿名性，除了:
 
 - @Kovri在连接到@eep站点时不使用出口节点
-- 您的流量永远不需要离开@I2P网络
+- 您的流量永远不需要离开I2P网络
 - 不需要HTTPS来使用@Kovri (@补种的情况除外)
 

_i18n/zh-cn/resources/moneropedia/eepsite.md

@@ -1,30 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"]
-summary: "A website or service hosted within the I2P network"
----
-
-### 基础知识
-
-EEP到底是对网站的内容的表示惊讶的一声惊叫，或 **端到端协议**，或其他完全不同的东西?
-
-虽然eep站点的原始定义已经随着时间的推移而丢失，但它的用例仍然存在：eep站点是托管在@I2P网络内（且仅能通过@I2P网络访问）的网站或服务。
-
-### 深度信息
-
-
-别名包括：
-
-1. *隐藏服务*
-  - 因为站点/服务隐藏在@I2P网络中，只能在网络中访问
-2. *大蒜网站*
-  - 因为本网站利用@I2P的@大蒜路由技术作为与客户沟通的一种方式
-  - 因为该服务是作为网站托管的，而不是任何其他类型的服务
-3. *大蒜服务*
-  - 因为该服务使用@I2P的@大蒜路由技术作为与客户端通信的一种方式
-  - 因为该服务是特定的服务，如IRC，电子邮件，或一个门罗币端（但也可能包括网站）
-
-
-### 备注
-
-要了解如何设置Eep站点（隐藏服务、大蒜站点、大蒜服务），请访问@Kovri[用户指南](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md)。

_i18n/zh-cn/resources/moneropedia/encryption.md

@@ -33,4 +33,4 @@ summary: "The process of encoding messages or information in a way that only aut
 - @隧道加密：大蒜消息通过@隧道传递，并由@隧道网关加密到@隧道端点
 - @传输层加密防止在[媒体层](https://en.wikipedia.org/wiki/OSI_model)解密@消息
 
-有关@Kovri和@I2P中使用的各类型的加密和加密@签名的详细信息，请访问@Java-I2P的[密码学](https://geti2p.net/spec/cryptography)。
+有关@Kovri和I2P中使用的各类型的加密和加密@签名的详细信息，请访问@Java-I2P的[密码学](https://geti2p.net/spec/cryptography)。

_i18n/zh-cn/resources/moneropedia/floodfill.md

@@ -1,13 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Floodfill"]
-summary: "An I2P router which maintains a distributed network-database"
----
-
-### 基础知识
-
-通过积极管理分布式网络数据库，具有*泛洪填充*功能的路由器能够帮助维护网络的稳定性和弹性，同时也具有去中心化和去信任的特性。
-
-### 深度信息
-
-虽然泛洪填充本身是一个简单的存储系统，但是泛洪填充与@网络数据库和@I2P网络中的其他协议之间的技术基础要复杂得多。请访问[网络数据库](https://geti2p.net/en/docs/how/networkdatabase)页面了解详细信息。

_i18n/zh-cn/resources/moneropedia/garlic-encryption.md

@@ -1,24 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Garlic-Encryption", "Layered-Encryption"]
-summary: "Layered encryption as implemented in Kovri / I2P"
----
-
-### 基础知识
-
-@大蒜加密是@I2P实现的基于@消息的@分层加密（类似于基于流的[洋葱路由](https://en.wikipedia.org/wiki/Onion_routing)）。
-
-通过分层@加密@消息，这允许@消息通过一系列代理路由，而不允许代理（或任何中介）读取@信息的内容。@分层加密是@Kovri、@I2P和[Tor](https://torproject.org)中的一个基本特性，也是在这些覆盖网络中保护匿名性的基石。
-
-### 深度信息
-
-对于@大蒜加密，@Kovri/@I2P与Tor的主要区别是:
-
-- @Kovri/@I2P将多条@消息捆绑在一起，形成大蒜“蒜瓣”
-  - 一个“蒜瓣”中可以包含任意数量的消息，而不是*只有*一条消息
-- @Kovri/@I2P使用[ElGamal](https://en.wikipedia.org/wiki/ElGamal)/[AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) @加密@消息并@传输
-
-
-### 备注
-
-有关详细信息，请参见@大蒜路由。

_i18n/zh-cn/resources/moneropedia/garlic-routing.md

@@ -1,47 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Garlic-Routing"]
-summary: "Routing technology as implemented in Kovri"
----
-
-### 基础知识
-
-术语*@大蒜路由*有复杂的历史有不同的解读。按照目前的情况，门罗币将*@大蒜路由*定义为@Kovri和@I2P创建的基于@消息的互联网对等节点匿名覆盖网络的方法。
-
-@大蒜路由的@大蒜加密类似于[洋葱路由](https://en.wikipedia.org/wiki/Onion_routing)的@分层加密，它有效地隐藏了发送方的IP地址，并确保从发送方发送到@目标的信息是安全的（反之亦然）。
-
-### 历史
-
-早在2000年6月，Roger Dingledine的[自由港硕士论文](http://www.freehaven.net/papers.html)（第8.1.1节）就以书面形式提出了*@大蒜路由*一词，该词源于“洋葱路由”一词。
-
-就在2016年10月，[#tor-开发人员](https://oftc.net/WebChat/)对术语*@大蒜路由*的创建提供了一些见解:
-
-[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc):
-
->我认为曾经试想过一种植物，其结构类似于'漏水管'拓扑结构，但我不认为我们曾经确定了一种。
-
-[Roger Dingledine](https://en.wikipedia.org/wiki/Roger_Dingledine):
-
->在自由港的头脑风暴中，有一瞬间我们描述了一个路由机制，有人说“大蒜路由!”，大家都笑了。
-所以我们肯定这个名字是我们在那个时候发明的。
-
-*注:尼克·马修森（Nick Mathewson）和罗杰·丁格尔丁（Roger Dingledine）同意使用上述引用*
-
-
-### 深度信息
-
-在技术术语中，对于@Kovri和@I2P， *@大蒜路由*可以解释为以下任何/所有内容:
-
-- @分层加密（类似于洋葱路由中的@分层加密）
-- 将多个@消息捆绑在一起（大蒜瓣）
-- ElGamal/ AES @加密
-
-*注意:虽然[Tor](https://torproject.org/)使用@分层加密，但是Tor不使用ElGamal，也不是基于消息的。*
-
-**阅读更多信息，请查看@大蒜加密**
-
-### 备注
-
--在洋葱/大蒜路由方面，分层@加密的另一种设想是用一个[俄罗斯套娃](https://en.wikipedia.org/wiki/Matryoshka_doll)替换洋葱/大蒜-每个外部/内部套娃都有一个锁和下一个/前一个套娃的公钥
-
--有关大蒜路由的更多技术细节，请阅读[大蒜路由](https://geti2p.net/en/docs/how/garlic-routing)上的@Java-I2P条目。

_i18n/zh-cn/resources/moneropedia/i2np.md

@@ -1,27 +0,0 @@
----
-tags: ["kovri"]
-terms: ["I2NP"]
-summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network"
----
-
-### 基础知识
-
-来自 @Java-I2P:
-
->
-@I2NP管理路由器之间的路由以及消息混合，并且在与支持多种公共传输的对等节点通信时，选择使用什么方式传输。
-
-### 深度信息
-
-来自 @Java-I2P:
-
->
-@I2NP （@I2P网络协议）@消息可以用于单跳、路由器到路由器、点对点@消息。通过@加密和在其他@消息中包裹@消息，可以通过多个跳转以安全的方式将它们发送到最终的@目标。@I2NP不指定也不要求任何特定的@传输层，但要求至少使用一次@传输。
-
-
->
-无论何时@目标想要将消息发送到另一个@目标，它都会为其本地路由器提供@目标结构和要发送的消息的原始字节。然后路由器决定将它发送到哪里，通过出站@隧道交付它，指示端点将它传递到适当的入站@隧道，在那里它再次传递到该@隧道的端点，并提供给目标以供接收。
-
-### 备注
-
-阅读更多关于@I2NP[协议](https://geti2p.net/en/docs/protocol/i2np)和[规范](https://geti2p.net/spec/i2np)的信息。

_i18n/zh-cn/resources/moneropedia/i2p.md

@@ -1,29 +0,0 @@
----
-tags: ["kovri"]
-terms: ["I2P"]
-summary: "The Invisible Internet Project: an anonymizing overlay network"
----
-
-### 门罗币
-
-关于门罗币的@I2P实现，请参见@Kovri。要查看@I2P和[Tor洋葱网络](https://torproject.org/)的比较，请阅读[比较](https://geti2p.net/en/comparison/tor)页面。
-
-### 基础知识
-
-来自@Java-I2P:
-
->I2P网络为互联网上的通信提供了强大的隐私保护。许多在公共互联网上可能会危及您隐私的活动，都可以在I2P中匿名进行。
-
-### 深度信息
-
-来自@Java-I2P:
-
->I2P是一个匿名覆盖网络——一个网络中的网络。它的目的是保护通信免受互联网服务提供商等第三方的监视。
-
->I2P被许多关心隐私的人使用：活动家、受压迫的人、记者和告密者，以及普通人。
-
->没有网络可以是“完全匿名的”。I2P的持续目标是使攻击越来越难以进行。随着网络规模的扩大和不断的学术审查，它的匿名性将会越来越强。
-
-### 备注
-
-@I2P的文档以及规范请看[这里](https://geti2p.net/docs/).

_i18n/zh-cn/resources/moneropedia/i2pcontrol.md

@@ -1,15 +0,0 @@
----
-tags: ["kovri"]
-terms: ["I2PControl"]
-summary: "An API inteface for Kovri and Java-I2P that allows simple remote control"
----
-
-### 基础知识
-
-@I2Pcontrol是一个用于@Kovri和@Java-I2P的[JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface)，它允许@I2Pcontrol客户端远程控制/监视正在运行的实例。
-
-两个可用的@I2PControl客户端分别是:[qtoopie](https://github.com/EinMByte/qtoopie) （c++客户端）和[itoopie](https://github.com/i2p/i2p.itoopie) （Java客户端）。读取 `kovri.conf` 为@Kovri配置@I2PControl。
-
-### 深度信息
-
-[I2PControl](https://geti2p.net/en/docs/api/i2pcontrol)页面提供了详细信息和规范。

_i18n/zh-cn/resources/moneropedia/in-net.md

@@ -1,13 +0,0 @@
----
-tags: ["kovri"]
-terms: ["In-net"]
-summary: "Within the I2P network"
----
-
-### 基础知识
-
-**网内**是一个[口语](https://en.wikipedia.org/wiki/Colloquial)术语，它描述*只*存在于@I2P网络中的活动、协议或功能。
-
-### 深度信息
-
-例如:*网内下载*被定义为*只*存在于@I2P网络中的下载。

_i18n/zh-cn/resources/moneropedia/java-i2p.md

@@ -1,13 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Java-I2P"]
-summary: "The original implementation of I2P - written in Java"
----
-
-### 基础知识
-
-术语“Java I2P”经常被用来描述目前已知和使用最多的原始@I2P实现。其实，还有其他各种@I2P实现，包括@Kovri;所有这些都依赖于最初的Java实现。
-
-### 备注
-
-要下载/了解更多关于Java的实现，请访问他们的[网站](https://geti2p.net/)。

_i18n/zh-cn/resources/moneropedia/jump-service.md

@@ -1,33 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Jump-Service"]
-summary: "An I2P website service that adds addresses to your address book"
----
-
-### 基础知识
-
-在您配置的@I2P网页浏览器中，您可以使用*跳转*服务来跳转到您的@地址薄中没有的@I2P地址。一旦您*跳转*到该地址，该地址将保存到您的@地址薄中。
-
-### 深度信息
-
-在@I2P配置的浏览器中，访问:http://stats.i2p/i2p/lookup.html（由@Java-I2P的首席开发人员*zzz*提供）
-
-然后，你有两个选择:
-
-1. *主机名查找*您希望访问的地址，然后手动复制/粘贴结果
-2. *输入@I2P主机名（**推荐**）跳转到@I2P网站
-
-
-### 使用主机名查找
-
-例如，输入 `pinkpaste.i2p` 进入*主机名查找*框（然后提交）将返回以下内容:
-
-```
-pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA==
-```
-
-复制/粘贴这个主机=@base64地址对到您的**私有** @订阅中。
-
-### 直接跳转
-
-例如，输入 `pinkpaste.i2p` 进入*跳转*框（然后提交）将自动重定向到网站**和**插入@本地唯一主机到@地址薄。

_i18n/zh-cn/resources/moneropedia/lease.md

@@ -1,13 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Lease", "Leases"]
-summary: "Authorizes an I2P tunnel to receive messages targeting a destination"
----
-
-### 基础知识
-
-一个租约定义了一个特定@I2P网络@隧道的授权，用于接收对准一个@目标的@消息。
-
-### 深度信息
-
-要了解更多细节，请阅读@Java-I2P的[租约](https://geti2p.net/spec/common-structures#lease)

_i18n/zh-cn/resources/moneropedia/locally-unique-host.md

@@ -12,9 +12,9 @@ summary: "A host defined by you and resolved only by you"
 
 您可以选择共享您对主机解析方式的诠释（例如，“本地主机”总是解析为“127.0.0.1”），但是解析被不正规的执行（例如，其他人可以将“本地主机”映射到任意IP地址）。
 
-在@I2P网络中，公共订阅中的主机可以被认为是@标准唯一主机，但最终，您可以自由地重新定义它们。
+在I2P网络中，公共订阅中的主机可以被认为是@标准唯一主机，但最终，您可以自由地重新定义它们。
 
 ### 备注
 
-- 门罗币主要使用@标准唯一主机解析，而@I2P只使用@本地唯一主机解析。
+- 门罗币主要使用@标准唯一主机解析，而I2P只使用@本地唯一主机解析。
-- @I2P和@Kovri的自定义顶级域名当前为 `.i2p` ，@Kovri只打算处理/使用 `.i2p` [顶级域名](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P和@Kovri的自定义顶级域名当前为 `.i2p` ，@Kovri只打算处理/使用 `.i2p` [顶级域名](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/zh-cn/resources/moneropedia/message.md

@@ -1,32 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Message", "Messages"]
-summary: "The mechanisms in which information travels within I2P"
----
-
-### 基础知识
-
-*消息*（存在于@传输层之上）包含网络所需的各种类型的信息，但最重要的是，您看到的、做的、发送的或接收的所有内容都将以*消息*的形式来来回回。
-
-在@I2P中有两种基本类型的*消息*:
-
-- @隧道消息
-- @I2NP消息
-
-
-本质上:*@隧道消息* **包含** @I2NP **消息片段**，然后在@隧道路径中的某些点[重新组装](https://geti2p.net/en/docs/tunnels/implementation)。
-
-### 深度信息
-
-@I2NP消息与@隧道@消息关系密切，因此在阅读@Java-I2P规范时，很容易混淆术语*消息*:
->
-1. 首先，隧道网关积累了大量的I2NP消息，并将它们预处理成隧道消息进行传输。
-2. 接下来，网关对预处理数据进行加密，然后将其转发到第一个跃点。
-3. 该对等节点和随后的隧道参与者打开加密层，验证它不是副本，然后将其转发给下一个对等节点。
-4. 最终，隧道消息到达端点，在此端点，按请求重新组装和转发最初由网关绑定的I2NP消息。
-
-### 备注
-
--@I2NP@消息需要被分割，因为它们的大小是可变的（从0到几乎64 KB），而@隧道@消息的大小是固定的（大约1 KB）。
-
--有关详细信息和规范，请访问[I2NP规范](https://geti2p.net/spec/i2np)和[隧道消息规范](https://geti2p.net/spec/tunnel-message)

_i18n/zh-cn/resources/moneropedia/network-database.md

@@ -1,25 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Network-Database"]
-summary: "A distributed database which contains needed router information so the network can stay intact"
----
-
-### 基础知识
-
-@网络数据库是一个[分布式数据库](https://en.wikipedia.org/wiki/Distributed_database)，其中包含对等节点必须使用的路由器信息，这样网络才能保持完整。
-
-### 深度信息
-
-来自 @Java-I2P:
-
->
-@I2P的@网络数据库是一个专门的分布式数据库，只包含两种类型的数据—路由器联系信息(@路由器信息)和@目标联系信息(@租约集)。每一段数据都由适当的一方签署，并由使用或存储它的任何人验证。此外，数据中还包含活跃的信息，允许删除不相关的条目，更新的条目替换旧的条目，以及抵御某些类型的攻击。
-
->
-@网络数据库使用一种称为“@泛洪填充”的简单技术进行分布式，其中所有路由器的一个子集（称之为“@泛洪填充路由器”）维护分布式数据库。
-
-
-
-### 备注
-
-详情请阅读[网络数据库](https://geti2p.net/en/docs/how/network-database)。

_i18n/zh-cn/resources/moneropedia/ntcp.md

@@ -1,33 +0,0 @@
----
-tags: ["kovri"]
-terms: ["NTCP"]
-summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports"
----
-
-### 基础知识
-
-*基于NIO（非阻塞I/O）的TCP（传输控制协议）*是@Kovri的两种加密@传输之一。
-
-与@SSU类似，@NTCP的*主要*目的是通过@隧道安全地传输@网内@I2NP消息，但与@SSU不同，@NTCP的功能仅通过加密的[TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol)。
-
-### 深度信息
-
- - 传递个别@I2NP消息（标准及时间同步）后:
-   - TCP已经建立
-   - 建立顺序已完成
- - 使用以下@加密:
-   - 2048位 [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman)
-   - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation)
- - 建立序列有以下*状态*:
-   - 准备建立
-   - 建立
-   - 已建立或“建立完成”
- - 使用以下来自@网络数据库:
-   - 传输名称:NTCP
-   - 主机:IP （IPv4或IPv6）或主机名（缩写IPv6地址（带“::”）是允许的）
-   - 端口:1024 - 65535
-
-
-### 备注
-
-更多详细信息，请阅读@Java-I2P的[NTCP](https://geti2p.net/en/docs/transport/ntcp)

_i18n/zh-cn/resources/moneropedia/reseed.md

@@ -1,15 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Reseed"]
-summary: "The method of which Kovri uses to bootstrap into the I2P network"
----
-
-### 基础知识
-
-当您第一次启动@Kovri（或者它已经离线很长时间了）时，@Kovri将需要一个对等节点列表来连接，以便[引导](https://en.wikipedia.org/wiki/Bootstrap)进入@I2P网络。@Kovri从存储在补种服务器上的特殊文件中获取这些节点。在这个文件里是@Kovri为了与@I2P对等节点连接而需要的各种各样的信息。
-
-### 深度信息
-
-@Kovri有一个[硬编码](https://en.wikipedia.org/wiki/Hard-coded)补种服务器列表可以用于获取。这些服务器使用[HTTPS](https://en.wikipedia.org/wiki/HTTPS)在@明网上安全地提供一个[SU3](https://geti2p.net/spec/updates#su3)文件(通过加密@签名来签署)。这个SU3文件包含用于验证文件及其内容完整性的信息。
-
-除了验证和处理该文件所需的技术元素之外，该文件的主要内容还包括一系列@路由器信息文件，@Kovri和@I2P路由器使用这些文件来定位并与其他@I2P对等节点通信。然后将这些对等节点存储到@网络数据库中。

_i18n/zh-cn/resources/moneropedia/router-info.md

@@ -1,66 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Router-Info", "Router-infos"]
-summary: "A data structure or file which contains an I2P peer's needed network information"
----
-
-### 基础知识
-
-@路由器信息是一个数据结构（定期写入[二进制文件](https://en.wikipedia.org/wiki/Binary_file)），其中包含定位、标识和与@I2P对等节点通信所需的所有信息。@路由器信息包括IP地址、路由器标识和其他各种各样的技术细节;用于@网络数据库，并发布到@泛洪填充路由器。
-
-### 深度信息
-
-以人类可读的形式表现，路由器信息可能是这样的：
-
-```
-Identity: [RouterIdentity:
-Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=
-Certificate: [Certificate: type: Key certificate
-Crypto type: 0
-Sig type: 7 (EdDSA_SHA512_Ed25519)]
-PublicKey: [PublicKey: size: 256]
-SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32]
-Padding: 96 bytes]
-Signature: [Signature EdDSA_SHA512_Ed25519: size: 64]
-Published: Sun Oct 09 01:34:59 UTC 2016
-Options (5):
-        [caps] = [LfR]
-        [netId] = [2]
-        [netdb.knownLeaseSets] = [37]
-        [netdb.knownRouters] = [2435]
-        [router.version] = [0.9.26]
-Addresses (4):
-[RouterAddress:
-Type: SSU
-Cost: 4
-Options (5):
-        [caps] = [BC]
-        [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
-        [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
-        [mtu] = [1472]
-        [port] = [22244]]
-[RouterAddress:
-Type: NTCP
-Cost: 9
-Options (2):
-        [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
-        [port] = [22244]]
-[RouterAddress:
-Type: SSU
-Cost: 6
-Options (4):
-        [caps] = [BC]
-        [host] = [88.181.203.36]
-        [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
-        [port] = [22244]]
-[RouterAddress:
-Type: NTCP
-Cost: 11
-Options (2):
-        [host] = [88.181.203.36]
-        [port] = [22244]]]
-```
-
-### 备注
-
-有关详细信息和规范，请访问@Java-I2P [网络数据库](https://geti2p.net/en/docs/how/networkdatabase)页面。

_i18n/zh-cn/resources/moneropedia/ssu.md

@@ -1,26 +0,0 @@
----
-tags: ["kovri"]
-terms: ["SSU"]
-summary: "Secure Semi-reliable UDP: one of two Kovri transports"
----
-
-### 基础知识
-
-*安全半可靠UDP（用户数据报协议）*是@Kovri的两种加密@传输方式之一。
-
-
-与@NTCP类似，@SSU的*主要*目的是通过@隧道安全地传输@网内@I2NP消息，但与@NTCP不同，@SSU功能仅通过加密的[UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol)。
-
-### 深度信息
-
-- 与@NTCP一样，@SSU也是面向连接的点对点数据传输
-- 称为“半可靠”，因为@SSU将重复转发“未确认的”消息（达到最大数量则丢弃）。
-- @SSU还提供了几个独特的服务（除了它作为@传输层的功能）:
-  - IP检测（本地检测或使用[对等节点测试](https://geti2p.net/en/docs/transport/ssu#peerTesting)）
-  - [网络地址转换](https://en.wikipedia.org/wiki/Network_address_translation)遍历  （使用[介绍人](https://geti2p.net/en/docs/transport/ssu#introduction)）
-  - [防火墙](https://en.wikipedia.org/wiki/Firewall_%28computing%29)状态，如果执行，@SSU可以通知@NTCP如果外部地址或防火墙状态发生变化
-
-
-### 备注
-
-更多细节，请阅读@Java-I2P的[SSU](https://geti2p.net/en/docs/transport/ssu)

_i18n/zh-cn/resources/moneropedia/subscription.md

@@ -1,52 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Subscription"]
-summary: "A file used by address book which contains I2P hosts paired with I2P destinations"
----
-
-### 基础知识
-
-订阅是一个包含 `.i2p` 主机列表与各自的@目标配对的文件。订阅由@地址薄使用。
-
-### 深度信息
-
-类似于[域名解析文件](https://en.wikipedia.org/wiki/Hosts_(file))可以将互联网主机名映射到指定的地址，订阅匹配一个 `.i2p` 地址到@base64地址，使用以下格式（不允许空格）： `host=address`
-
-更具体地说，订阅将配对一个@本地唯一主机到@base64地址。
-
-例如:
-
-```
-anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA==
-```
-
-1. `anonimal.i2p` 是@本地唯一主机
-2. `=` 是分隔符
-3. 剩下的就是@base64地址
-
-### 订阅类型
-
-
-对于@Kovri，有两种类型的订阅文件：*公开*和*私有*。
-
-*公共*订阅:
-
--用于启动时使用基本服务（IRC，电子邮件，门罗币等）
-
--是静态的，每12小时从门罗币的@地址薄服务器刷新一次
-
--允许您安全地与所有人共享订阅，因为它是公开可用的 （任何共享相同公共订阅的人，也可以将相同的主机名解析到与您相同的目标）
-
-*私有*订阅:
-
--仅供您使用，除非您明确选择共享文件，否则不会与他人共享
-
--默认文件是 `private_hosts.txt` 在你的@数据目录中
-
-### 更新私有订阅
-
-您可以使用@跳转服务，手动更新您的私有订阅。更新后的订阅将被送入@地址薄供您使用。
-
-### 备注
-
-要了解如何订阅多个订阅，请参见[用户指南](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md)。

_i18n/zh-cn/resources/moneropedia/transports.md

@@ -1,19 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Transports", "Transport"]
-summary: "The two encrypted transport layers for Kovri"
----
-
-### 基础知识
-
-@I2P提供了两种加密传输层技术，允许@Kovri安全地使用[TCP/IP](https://en.wikipedia.org/wiki/Tcp/ip)连接。这些技术(@SSU和@NTCP)被称为*@传输*。
-
-### 深度信息
-
-@SSU加密了[UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol)， @NTCP加密了[TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol)。它们在[传输层](https://en.wikipedia.org/wiki/Transport_layer)提供@加密，因此更高级别的@消息可以通过@I2P网络上的@隧道被发送。
-
-### 备注
-
-- 阅读关于@I2P的传输的内容在 [传输](https://geti2p.net/en/docs/transport) 页面
-- 了解 [OSI模型](https://en.wikipedia.org/wiki/OSI_model) 中的传输层
-

_i18n/zh-cn/resources/moneropedia/tunnel.md

@@ -1,35 +0,0 @@
----
-tags: ["kovri"]
-terms: ["Tunnel", "Tunnels"]
-summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers"
----
-
-### 基础知识
-
-当您通过@I2P进行通信时（访问@eep站点 /使用@大蒜服务），首先需要使用@传输连接到对等节点，然后构建虚拟的“隧道”。这些虚拟隧道是临时的单向路径，通过定义的@I2P路由器序列将信息传递到您的@目标。隧道是通过分层的@大蒜加密构建并使用的，它是用于传输所有@I2NP @消息的通用机制。
-
-每个对等节点至少构建*两个*单向隧道：一个用于**出站流量**，另一个用于**入站流量**。这些隧道分为**入站隧道** （其中@消息朝隧道创建者而来）和 **出站隧道** （其中隧道创建者向外发送@消息）。因此，一个往返@消息和对@目标的回复，需要*4条*隧道 （两个用于您的@消息，两个用于您的目标）。
-
-### 深度信息
-
-来自 @Java-I2P:
-
->
-在I2P中，@消息通过对等节点的虚拟隧道在一个方向上传递，使用任何可用的方法将@消息传递到下一跃点。消息到达隧道的网关,捆绑起来和/或分散成固定大小@隧道 @消息,然后转发到下一跃点的隧道, 处理和验证@消息的有效性并将其发送到下一跃点,依此类推,直到它到达@隧道端点。该端点接收由网关打包的消息，并按照指示将其转发到另一个路由器、或另一个路由器上的另一条隧道或本地。
-
->
-隧道的工作原理都是一样的，但可以分为两种——入站隧道和出站隧道。入站隧道有一个不受信任的网关，该网关将消息向下传递给隧道创建者，后者作为隧道端点。对于出站隧道，隧道创建者充当网关，将消息传递到远程端点。
-
->
-隧道的创建者精确地选择哪些对等节点将参与隧道，并为每个对等节点提供必要的配置数据。它们可能有任意数量的跃点。它的意图是让参与者或第三方很难确定隧道的长度,甚至勾结参与者以确定他们是不是相同的隧道的一部分（除非勾结的对等节点他们在隧道中彼此相邻）。
-
-### 备注
-
-来自 @Java-I2P:
-
->
-@I2P本质上是一个包交换网络，即使有了这些隧道，它也可以利用多个并行运行的隧道，提高弹性和平衡负载。尽管I2P内的隧道与电路交换网络相似，但I2P内的所有内容都严格基于消息——隧道仅仅是帮助组织消息传递的会计技巧。对于消息的可靠性或顺序没有做任何假设，重传留给更高的层级（例如I2P的客户端层流媒体库）。
-
-### 文件
-
-有关规范和详细文档，请访问 [隧道-路由](https://geti2p.net/en/docs/how/tunnel-routing) 和 [隧道-实现](https://geti2p.net/en/docs/tunnels/implementation) 页面。

_i18n/zh-tw/resources/moneropedia/canonically-unique-host.md

@@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)

_i18n/zh-tw/resources/moneropedia/clearnet.md

@@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
 
 These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
 
-Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
 
-- @Kovri does not use exit nodes when connecting to an @eepsite
+- @Kovri does not use exit nodes when connecting to an eepsite
-- Your traffic never need to leave the @I2P network
+- Your traffic never need to leave the I2P network
-- You do not need HTTPS to use @Kovri (with the exception of @reseed)
+- You do not need HTTPS to use @Kovri (with the exception of reseed)

_i18n/zh-tw/resources/moneropedia/encryption.md

@@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
 @Kovri implements various types of encryption in *at least* 4 essential capacities:
 
 - @Reseed for bootstrapping
-- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
-- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
-- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
 
-For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
+For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)

_i18n/zh-tw/resources/moneropedia/locally-unique-host.md

@@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
 
 You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
 
-Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
 
 ### Notes
 
-- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
-- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
+- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)