diff --git a/de/quality_web.php b/de/quality_web.php
index 7792ab1..1e7bea9 100644
--- a/de/quality_web.php
+++ b/de/quality_web.php
@@ -70,4 +70,5 @@ Zum Zwecke des Importierens von Daten (sei es zur Migration der Daten für die I
 Die Importer-Module zur Definition der Datentypen und zum Auslesen der Daten aus verschiedenen Eingabeformaten werden in museum-digital:qa nachgenutzt. So kann museum-digital:qa mit wenigen Anpassungen alle Importformate, die auch der Importer von museum-digital unterstützt, unterstützen (bei museumsspezifischen Importformaten lohnt es sich allerdings nicht, diese Anpassungen zu unternehmen). Ohne relevanten eigenen Code für das Auslesen der eingehenden Daten bleibt museum-digital:qa somit zudem sehr wartungsarm. Umgekehrt bedeutet die Nachnutzung des Auslese-Teils des Importers auch, dass alle Daten, die mit museum-digital:qa auf ihre Qualität überprüft werden können, ohne weitere Anpassungen in museum-digital importiert werden können.
 
 Die eingelesenen Daten liegen in der Folge in einer strukturierten Form vor und können verhältnismäßig einfach weiter verarbeitet werden, indem sie - leicht umformuliert - an die Funktionen zur Überprüfung der Datenqualität weitergegeben werden. Diese Funktionen wurden im Zuge der Arbeit an museum-digital:qa aus museum-digital:musdb in eine eigene Open-Source-Bibliothek ausgelagert.',
+  'go_back' => 'Go back',
 );
diff --git a/en/quality_web.php b/en/quality_web.php
index d754c0b..bf2156d 100644
--- a/en/quality_web.php
+++ b/en/quality_web.php
@@ -69,4 +69,5 @@ For the purpose of importing data (be it for data migration or simply for public
 The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
 
 The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
 );
diff --git a/hu/quality_web.php b/hu/quality_web.php
index d754c0b..bf2156d 100644
--- a/hu/quality_web.php
+++ b/hu/quality_web.php
@@ -69,4 +69,5 @@ For the purpose of importing data (be it for data migration or simply for public
 The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
 
 The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
 );
diff --git a/ru/quality_web.php b/ru/quality_web.php
index d754c0b..bf2156d 100644
--- a/ru/quality_web.php
+++ b/ru/quality_web.php
@@ -69,4 +69,5 @@ For the purpose of importing data (be it for data migration or simply for public
 The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
 
 The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
 );
diff --git a/uk/quality_web.php b/uk/quality_web.php
index d754c0b..bf2156d 100644
--- a/uk/quality_web.php
+++ b/uk/quality_web.php
@@ -69,4 +69,5 @@ For the purpose of importing data (be it for data migration or simply for public
 The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
 
 The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
 );