Add 'Pruning' to all languages

_i18n/ar.yml

@@ -632,6 +632,7 @@ moneropedia:
     paperwallet: Paper Wallet
     paymentid: Payment ID
     pedersen-commitment: Pedersen Commitment
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Reseed
     ringCT: Ring CT

_i18n/ar/resources/moneropedia/pruning.md

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/de.yml

@@ -633,6 +633,7 @@ moneropedia:
     paperwallet: Paper-Wallet
     paymentid: Payment-ID
     pedersen-commitment: Pedersen-Commitment
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Reseed
     ringCT: vertrauliche Ringtransaktionen (Ring CT)

_i18n/de/resources/moneropedia/pruning.md

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/es.yml

@@ -633,6 +633,7 @@ moneropedia:
     paperwallet: Monedero en Papel
     paymentid: ID de Pago
     pedersen-commitment: Compromiso Pedersen
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Resembrar
     ringCT: Transacción Circular Confidencial

_i18n/es/resources/moneropedia/pruning.md

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/fr.yml

@@ -634,6 +634,7 @@ moneropedia:
     paperwallet: portefeuille Papier
     paymentid: ID de paiement
     pedersen-commitment: Engagement de Pedersen
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Réensemencement
     ringCT: Transactions confidentielles de cercle

_i18n/fr/resources/moneropedia/pruning.md

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/it.yml

@@ -631,6 +631,7 @@ moneropedia:
     paperwallet: Portafoglio cartaceo
     paymentid: ID Pagamento
     pedersen-commitment: Pedersen Commitment
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Reseed
     ringCT: Ring CT

_i18n/it/resources/moneropedia/pruning.md

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/nl.yml

@@ -634,6 +634,7 @@ moneropedia:
     paperwallet: Paper Wallet
     paymentid: Payment ID
     pedersen-commitment: Pedersen Commitment
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Reseed
     ringCT: Ring CT

_i18n/nl/resources/moneropedia/pruning.md

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/pl.yml

@@ -633,6 +633,7 @@ moneropedia:
     paperwallet: Papierowy portfel
     paymentid: Numer identyfikacyjny płatności
     pedersen-commitment: Zobowiązanie Pedersena
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Reseed
     ringCT: Poufne Transakcje Pierścieniowe

_i18n/pl/resources/moneropedia/pruning.md

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/pt-br.yml

@@ -634,6 +634,7 @@ moneropedia:
     paperwallet: Carteira em Papel
     paymentid: ID de Pagamento
     pedersen-commitment: Comprometimento de Pedersen
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Reseed
     ringCT: Ring CT

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

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/ru.yml

@@ -638,6 +638,7 @@ moneropedia:
     paperwallet: Бумажный кошелёк
     paymentid: Идентификатор платежа
     pedersen-commitment: Обязательство Педерсена
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Повторное заполнение
     ringCT: Ring CT

_i18n/ru/resources/moneropedia/pruning.md

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/tr.yml

@@ -633,6 +633,7 @@ moneropedia:
     paperwallet: Kâğıt Cüzdan
     paymentid: Ödeme ID
     pedersen-commitment: Pedersen Üstlenmesi
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Tekrar-tohum
     ringCT: Halka CT

_i18n/tr/resources/moneropedia/pruning.md

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/zh-cn.yml

@@ -632,6 +632,7 @@ moneropedia:
     paperwallet: 纸钱包
     paymentid: 付款ID
     pedersen-commitment: Pedersen Commitment 
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Reseed 
     ringCT: 环交易

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

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.

_i18n/zh-tw.yml

@@ -631,6 +631,7 @@ moneropedia:
     paperwallet: Paper Wallet
     paymentid: Payment ID
     pedersen-commitment: Pedersen Commitment
+    pruning: Pruning
     remote-node: Remote Node
     reseed: Reseed
     ringCT: Ring CT

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

@@ -0,0 +1,17 @@
+---
+terms: ["pruning"]
+summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
+---
+
+{% include untranslated.html %}
+'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node.
+
+There are three ways to prune:
+
+- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain.
+- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce.
+- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain.
+
+Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
+
+The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.