From 4e1d1a8c55dc86ae02e68b0b4d165cc94fbbf1c5 Mon Sep 17 00:00:00 2001
From: erciccione <erciccione@protonmail.com>
Date: Sat, 2 Oct 2021 10:26:42 +0200
Subject: [PATCH] moneropedia: uniform structure of pruning.md

---
 _i18n/ar/resources/moneropedia/pruning.md    | 33 +++++++++++++----
 _i18n/de/resources/moneropedia/pruning.md    | 38 +++++++++++++++-----
 _i18n/en/resources/moneropedia/pruning.md    |  3 ++
 _i18n/es/resources/moneropedia/pruning.md    | 33 +++++++++++++----
 _i18n/fr/resources/moneropedia/pruning.md    | 33 +++++++++++++----
 _i18n/it/resources/moneropedia/pruning.md    | 33 +++++++++++++----
 _i18n/nb-no/resources/moneropedia/pruning.md | 35 ++++++++++++++----
 _i18n/nl/resources/moneropedia/pruning.md    | 33 +++++++++++++----
 _i18n/pl/resources/moneropedia/pruning.md    | 33 +++++++++++++----
 _i18n/pt-br/resources/moneropedia/pruning.md | 33 +++++++++++++----
 _i18n/ru/resources/moneropedia/pruning.md    | 35 ++++++++++++++----
 _i18n/tr/resources/moneropedia/pruning.md    | 33 +++++++++++++----
 _i18n/zh-cn/resources/moneropedia/pruning.md | 33 +++++++++++++----
 _i18n/zh-tw/resources/moneropedia/pruning.md | 33 +++++++++++++----
 po/moneropedia/pruning.config                | 13 +++++++
 15 files changed, 362 insertions(+), 92 deletions(-)
 create mode 100644 po/moneropedia/pruning.config

diff --git a/_i18n/ar/resources/moneropedia/pruning.md b/_i18n/ar/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/ar/resources/moneropedia/pruning.md
+++ b/_i18n/ar/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/_i18n/de/resources/moneropedia/pruning.md b/_i18n/de/resources/moneropedia/pruning.md
index fe1547c3..00b7f533 100644
--- a/_i18n/de/resources/moneropedia/pruning.md
+++ b/_i18n/de/resources/moneropedia/pruning.md
@@ -1,17 +1,39 @@
 ---
-terms: ["pruning", Pruning"]
-summary: "Funktion, die es Node-Betreibern erlaubt, lediglich 1/3 der Blockchain herunterzuladen und zu synchronisieren"
+summary: 'Funktion, die es Node-Betreibern erlaubt, lediglich 1/3 der Blockchain herunterzuladen und zu synchronisieren'
+terms: ["pruning"]
 ---
 
 {% include disclaimer.html translated="yes" translationOutdated="no" %}
-"Pruning" (eng. für Stutzen) ermöglicht es Node-Betreibern, 2/3 des Speicherplatzes einzusparen, während der gesamte Transaktionsverlauf bestehen bleibt. Pruning funktioniert durch das Entfernen von 7/8 der unwichtigen Ringsignatur-Daten. Das verbleibende Achtel bleibt für andere Nodes verfügbar und wird zum Synchronisieren mit dem Netzwerk genutzt. Andere Pruned-Nodes verfügen über ein zufälliges Achtel der Daten und stellen dies dem Netzwerk zur Verfügung. Es gibt beim Gebrauch eines Pruned-Nodes keine Nachteile bezüglich der Privatsphäre oder Sicherheit.
+
+"Pruning" (eng. für Stutzen) ermöglicht es Node-Betreibern, 2/3 des
+Speicherplatzes einzusparen, während der gesamte Transaktionsverlauf
+bestehen bleibt. Pruning funktioniert durch das Entfernen von 7/8 der
+unwichtigen Ringsignatur-Daten. Das verbleibende Achtel bleibt für andere
+Nodes verfügbar und wird zum Synchronisieren mit dem Netzwerk
+genutzt. Andere Pruned-Nodes verfügen über ein zufälliges Achtel der Daten
+und stellen dies dem Netzwerk zur Verfügung. Es gibt beim Gebrauch eines
+Pruned-Nodes keine Nachteile bezüglich der Privatsphäre oder Sicherheit.
 
 Es gibt drei Möglichkeiten des Prunings:
 
-- *Synchronisieren eines Pruned-Nodes von Grund auf:* Du synchronisierst und lädst lediglich 1/3 der gesamten Blockchain herunter.
-- *Pruning eines bestehenden Nodes:* Die bereits bestehende Blockchain wird gestutzt. Dies resultiert nicht in einer kleineren Blockchain, sondern wird Teile der Datei als leer markieren. Zukünftige Daten werden diesen nun freien Platz nutzen, damit die Datei nicht wächst, bis der Speicherplatz knapp wird.
-- *Erstellung einer neuen, gestutzten Blockchain aus einer kompletten Blockchain:* Eine komplette Blockchain, die du schon hast, wird zur Erstellung einer neuen, gestutzten Blockchain verwendet.
+- *Synchronisieren eines Pruned-Nodes von Grund auf:* Du synchronisierst und
+lädst lediglich 1/3 der gesamten Blockchain herunter.
 
-Pruned-Nodes sind sehr nützlich und @Remote-Nodes vorzuziehen. Wenn es allerdings möglich ist, sollten Nutzer einen Full-Node betreiben und das Pruning nur im Falle der Notwendigkeit in Betracht ziehen.
+- *Pruning eines bestehenden Nodes:* Die bereits bestehende Blockchain wird
+gestutzt. Dies resultiert nicht in einer kleineren Blockchain, sondern wird
+Teile der Datei als leer markieren. Zukünftige Daten werden diesen nun
+freien Platz nutzen, damit die Datei nicht wächst, bis der Speicherplatz
+knapp wird.
 
-Die Funktion des Datenbank-Prunings wurde im Januar 2019 [hinzugefügt](https://github.com/monero-project/monero/pull/4843). Im [Blogpost]({{ site.baseurl }}/2019/02/01/pruning.html) finden sich weitere Informationen.
\ No newline at end of file
+- *Erstellung einer neuen, gestutzten Blockchain aus einer kompletten
+Blockchain:* Eine komplette Blockchain, die du schon hast, wird zur
+Erstellung einer neuen, gestutzten Blockchain verwendet.
+
+Pruned-Nodes sind sehr nützlich und @Remote-Nodes vorzuziehen. Wenn es
+allerdings möglich ist, sollten Nutzer einen Full-Node betreiben und das
+Pruning nur im Falle der Notwendigkeit in Betracht ziehen.
+
+Die Funktion des Datenbank-Prunings wurde im Januar 2019
+[hinzugefügt](https://github.com/monero-project/monero/pull/4843). Im
+[Blogpost]({{ site.baseurl }}/2019/02/01/pruning.html) finden sich weitere
+Informationen.
diff --git a/_i18n/en/resources/moneropedia/pruning.md b/_i18n/en/resources/moneropedia/pruning.md
index 581f827e..4fadb717 100644
--- a/_i18n/en/resources/moneropedia/pruning.md
+++ b/_i18n/en/resources/moneropedia/pruning.md
@@ -4,12 +4,15 @@ summary: "Feature that allows node operators to download and sync only 1/3 of th
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
+
 '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.
diff --git a/_i18n/es/resources/moneropedia/pruning.md b/_i18n/es/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/es/resources/moneropedia/pruning.md
+++ b/_i18n/es/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/_i18n/fr/resources/moneropedia/pruning.md b/_i18n/fr/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/fr/resources/moneropedia/pruning.md
+++ b/_i18n/fr/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/_i18n/it/resources/moneropedia/pruning.md b/_i18n/it/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/it/resources/moneropedia/pruning.md
+++ b/_i18n/it/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/_i18n/nb-no/resources/moneropedia/pruning.md b/_i18n/nb-no/resources/moneropedia/pruning.md
index 065915a6..8f14c130 100644
--- a/_i18n/nb-no/resources/moneropedia/pruning.md
+++ b/_i18n/nb-no/resources/moneropedia/pruning.md
@@ -1,17 +1,38 @@
 ---
+summary: 'En funksjon som lar nodeoperatører laste ned og synkronisere bare 1/3 av blokkjeden'
 terms: ["pruning", "utrensking"]
-summary: "En funksjon som lar nodeoperatører laste ned og synkronisere bare 1/3 av blokkjeden"
 ---
 
 {% include disclaimer.html translated="yes" translationOutdated="no" %}
-«Utrensking» lar nodeoperatører lagre 2/3 med lagringsplass mens de fremdeles har tilgang til hele transaksjonshistorikken. Utrensking fungerer ved å fjerne 7/8 av de unødvendige ringsignaturdataene. Den gjenstående 1/8 med data blir tilgjengelig for de andre nodene og vil brukes til å synkroniseres med nettverket. Andre utrenskede noder vil ha en tilfeldig 1/8 av dataene som de også gjør tilgjengelig til nettverket. Det finnes ingen ulemper hva gjelder personvern eller sikkerhet når man bruker en utrensket node.
+
+«Utrensking» lar nodeoperatører lagre 2/3 med lagringsplass mens de
+fremdeles har tilgang til hele transaksjonshistorikken. Utrensking fungerer
+ved å fjerne 7/8 av de unødvendige ringsignaturdataene. Den gjenstående 1/8
+med data blir tilgjengelig for de andre nodene og vil brukes til å
+synkroniseres med nettverket. Andre utrenskede noder vil ha en tilfeldig 1/8
+av dataene som de også gjør tilgjengelig til nettverket. Det finnes ingen
+ulemper hva gjelder personvern eller sikkerhet når man bruker en utrensket
+node.
 
 Det er tre måter å utrenske på:
 
-- *Synkronisere en utrensket node fra bunn:* Da laster du ned og synkroniserer kun 1/3 av hele blokkjeden.
-- *Utrenske en eksisterende node:* Blokkjeden som allerede eksisterer vil utrenskes, men dette vil ikke resultere i en mindre blokkjede. Den vil istedenfor markere deler av filen som ledig, slik at fremtidig data benytter den ledige lagringsplassen, noe som medfører at filen ikke vokser før den ledige lagringsplassen blir knapp.
-- *Opprette en ny, utrensket blokkjede fra en full en:* En full blokkjede som du allerede har vil brukes for å opprette en ny, utrensket blokkjede.
+- *Synkronisere en utrensket node fra bunn:* Da laster du ned og
+synkroniserer kun 1/3 av hele blokkjeden.
 
-Utrenskede noder er svært nyttige, og foretrekkes fremfor @eksterne noder, men brukere bør, hvis mulig, kjøre en fullstendig node og kun velge å utrenske hvis det er nødvendig.
+- *Utrenske en eksisterende node:* Blokkjeden som allerede eksisterer vil
+utrenskes, men dette vil ikke resultere i en mindre blokkjede. Den vil
+istedenfor markere deler av filen som ledig, slik at fremtidig data benytter
+den ledige lagringsplassen, noe som medfører at filen ikke vokser før den
+ledige lagringsplassen blir knapp.
 
-«Databaseutrensking»-funksjonen [ble lagt til](https://github.com/monero-project/monero/pull/4843) i januar 2019. Se [blogginnlegget]({{ site.baseurl }}/2019/02/01/pruning.html) for mer informasjon.
+- *Opprette en ny, utrensket blokkjede fra en full en:* En full blokkjede
+som du allerede har vil brukes for å opprette en ny, utrensket blokkjede.
+
+Utrenskede noder er svært nyttige, og foretrekkes fremfor @eksterne noder,
+men brukere bør, hvis mulig, kjøre en fullstendig node og kun velge å
+utrenske hvis det er nødvendig.
+
+«Databaseutrensking»-funksjonen [ble lagt
+til](https://github.com/monero-project/monero/pull/4843) i januar 2019. Se
+[blogginnlegget]({{ site.baseurl }}/2019/02/01/pruning.html) for mer
+informasjon.
diff --git a/_i18n/nl/resources/moneropedia/pruning.md b/_i18n/nl/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/nl/resources/moneropedia/pruning.md
+++ b/_i18n/nl/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/_i18n/pl/resources/moneropedia/pruning.md b/_i18n/pl/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/pl/resources/moneropedia/pruning.md
+++ b/_i18n/pl/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/_i18n/pt-br/resources/moneropedia/pruning.md b/_i18n/pt-br/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/pt-br/resources/moneropedia/pruning.md
+++ b/_i18n/pt-br/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/_i18n/ru/resources/moneropedia/pruning.md b/_i18n/ru/resources/moneropedia/pruning.md
index c6d5f12a..32ae31eb 100644
--- a/_i18n/ru/resources/moneropedia/pruning.md
+++ b/_i18n/ru/resources/moneropedia/pruning.md
@@ -1,17 +1,38 @@
 ---
+summary: 'Функция, которая позволяет операторам узлов загружать и синхронизировать только 1/3 блокчейна'
 terms: ["pruning", "обрезанием", "Обрезание", "обрезание", "обрезания"]
-summary: "Функция, которая позволяет операторам узлов загружать и синхронизировать только 1/3 блокчейна"
 ---
 
 {% include disclaimer.html translated="yes" translationOutdated="no" %}
-'Обрезание' позволяет операторам узлов сэкономить 2/3 объёма памяти при сохранении полной истории транзакций. Обрезание предполагает удаление 7/8 ненужных данных кольцевых подписей. Остающаяся 1/8 данных будет доступна остальным узлам и будет использоваться для синхронизации с сетью. Остальные «обрезанные» узлы будут иметь случайную 1/8 данных, которая также будет доступна сети. Такими обрезанными узлами можно пользоваться без какого-либо ущерба для анонимности или безопасности.
+
+'Обрезание' позволяет операторам узлов сэкономить 2/3 объёма памяти при
+сохранении полной истории транзакций. Обрезание предполагает удаление 7/8
+ненужных данных кольцевых подписей. Остающаяся 1/8 данных будет доступна
+остальным узлам и будет использоваться для синхронизации с сетью. Остальные
+«обрезанные» узлы будут иметь случайную 1/8 данных, которая также будет
+доступна сети. Такими обрезанными узлами можно пользоваться без какого-либо
+ущерба для анонимности или безопасности.
 
 Существует три способа обрезания:
 
-- *Синхронизация обрезанного узла с нуля.* Загружается и синхронизируется только 1/3 всего блокчейна.
-- *Обрезание существующего узла.* Обрезается уже существующий блокчейн, но в результате блокчейн не становится меньше. Вместо этого части файла помечаются как свободные, после чего данные будут использовать это свободное место, и файл не будет разрастаться до тех пор, пока свободного место будет достаточно.
-- *Создание нового обрезанного блокчейна на основе полного.* Имеющийся полный блокчейн будет использован для нового обрезанного блокчейна.
+- *Синхронизация обрезанного узла с нуля.* Загружается и синхронизируется
+только 1/3 всего блокчейна.
 
-Обрезанные узлы довольно полезны, и в качестве @удалённых-узлов лучше использовать именно их, но, по возможности, пользователям рекомендуется создавать полные узлы и прибегать к обрезанию только в случае разумной необходимости.
+- *Обрезание существующего узла.* Обрезается уже существующий блокчейн, но в
+результате блокчейн не становится меньше. Вместо этого части файла
+помечаются как свободные, после чего данные будут использовать это свободное
+место, и файл не будет разрастаться до тех пор, пока свободного место будет
+достаточно.
 
-Возможность 'обрезания базы данных' [добавлена](https://github.com/monero-project/monero/pull/4843) в январе 2019. Дополнительная информация содержится в соответствующем [посте]({{ site.baseurl }}/2019/02/01/pruning.html).
+- *Создание нового обрезанного блокчейна на основе полного.* Имеющийся
+полный блокчейн будет использован для нового обрезанного блокчейна.
+
+Обрезанные узлы довольно полезны, и в качестве @удалённых-узлов лучше
+использовать именно их, но, по возможности, пользователям рекомендуется
+создавать полные узлы и прибегать к обрезанию только в случае разумной
+необходимости.
+
+Возможность 'обрезания базы данных'
+[добавлена](https://github.com/monero-project/monero/pull/4843) в январе
+2019. Дополнительная информация содержится в соответствующем [посте]({{
+site.baseurl }}/2019/02/01/pruning.html).
diff --git a/_i18n/tr/resources/moneropedia/pruning.md b/_i18n/tr/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/tr/resources/moneropedia/pruning.md
+++ b/_i18n/tr/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/_i18n/zh-cn/resources/moneropedia/pruning.md b/_i18n/zh-cn/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/zh-cn/resources/moneropedia/pruning.md
+++ b/_i18n/zh-cn/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/_i18n/zh-tw/resources/moneropedia/pruning.md b/_i18n/zh-tw/resources/moneropedia/pruning.md
index 581f827e..472b07b1 100644
--- a/_i18n/zh-tw/resources/moneropedia/pruning.md
+++ b/_i18n/zh-tw/resources/moneropedia/pruning.md
@@ -1,17 +1,36 @@
 ---
+summary: 'Feature that allows node operators to download and sync only 1/3 of the blockchain'
 terms: ["pruning"]
-summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain"
 ---
 
 {% include disclaimer.html translated="no" translationOutdated="no" %}
-'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.
+
+'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.
+- *Synchronize a pruned node from scratch:* You will download and sync only
+1/3 of the full 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.
+- *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.
 
-The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
+- *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]({{ site.baseurl }}/2019/02/01/pruning.html) for
+more information.
diff --git a/po/moneropedia/pruning.config b/po/moneropedia/pruning.config
new file mode 100644
index 00000000..e640ef9c
--- /dev/null
+++ b/po/moneropedia/pruning.config
@@ -0,0 +1,13 @@
+[po4a_langs] es it pl fr ar ru de nl pt-br tr zh-cn zh-tw nb-no
+[po4a_paths] ../_i18n/en/resources/moneropedia/weblate/pruning.pot $lang:../_i18n/$lang/resources/moneropedia/weblate/pruning.po
+
+[options] opt:"--keep=0"
+[options] opt:"--localized-charset=UTF-8"
+[options] opt:"--master-charset=UTF-8"
+[options] opt:"--master-language=en_US"
+[options] opt:"--msgmerge-opt='--no-wrap'"
+[options] opt:"--wrap-po=newlines"
+
+[po4a_alias:markdown] text opt:"--option markdown"
+
+[type: markdown] ../_i18n/en/resources/moneropedia/pruning.md $lang:../_i18n/$lang/resources/moneropedia/pruning.md
\ No newline at end of file