diff --git a/nodac/de/basis.json b/nodac/de/basis.json
index d2c4e38e..27f7c583 100644
--- a/nodac/de/basis.json
+++ b/nodac/de/basis.json
@@ -149,6 +149,10 @@
         "manipulate_relations": "Bez\u00fcge bearbeiten",
         "mark_as_always_of_current_type": " Den Namen des Eintrags als eindeutig dem derzeitigen Typ zugeh\u00f6rig markieren",
         "entry_is_marked_as_distinctly_of_type": "Der Name dieses Eintrags ist als eindeutig und exklusiv f\u00fcr Eintr\u00e4ge des gegebenen Typs markiert.",
-        "fetch_from_wikidata": "Zus\u00e4tzliche Informationen von Wikidata laden"
+        "fetch_from_wikidata": "Zus\u00e4tzliche Informationen von Wikidata laden",
+        "open_update_log": "\u00d6ffnet ein einfaches Log der Bearbeitungen des derzeitigen Eintrags und zeigt die jeweiligen Bearbeitenden an.",
+        "versioning": "Versionierung",
+        "versioning_explica": "\u00d6ffnet ein Overlay, dass die gesamte aufgezeichnete Versionsgeschichte des gegebenen Eintrags anzeigt.",
+        "ambiguous_names_explica": "Sonderseite f\u00fcr die Verwaltung \"zweideutiger Begriffe\". \"Frankfurt\" mag etwa \"Frankfurt am Main\" oder \"Frankfurt an der Oder\" bedeuten. Beide Begriffe sind valide, weshalb eine Autokorrektur in die eine oder andere Richtung nicht sinnvoll einzurichten ist. So ist nicht zu verhindern, dass zweideutige Begriffe regelm\u00e4\u00dfig in die kontrollierten Vokabulare gelangen. Umso wichtiger ist, sie schnell zu bereinigen und zu spezifizieren. Entsprechend bestehen Suchfunktionen f\u00fcr das finden als \"zweideutig\" markierter Begriffe."
     }
 }
\ No newline at end of file
diff --git a/nodac/en/basis.json b/nodac/en/basis.json
index 8eb40307..6f3c142e 100644
--- a/nodac/en/basis.json
+++ b/nodac/en/basis.json
@@ -149,6 +149,10 @@
         "manipulate_relations": "Manipulate relations",
         "mark_as_always_of_current_type": "Mark name of this entry as distinctly of the current type",
         "entry_is_marked_as_distinctly_of_type": "The name of this entry is marked as distinctly and exclusively in use for entries of the current type.",
-        "fetch_from_wikidata": "Fetch additional information from Wikidata"
+        "fetch_from_wikidata": "Fetch additional information from Wikidata",
+        "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.",
+        "versioning": "Versioning",
+        "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.",
+        "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again."
     }
 }
\ No newline at end of file
diff --git a/nodac/hu/basis.json b/nodac/hu/basis.json
index 50c4d45d..2e5d95c4 100644
--- a/nodac/hu/basis.json
+++ b/nodac/hu/basis.json
@@ -149,6 +149,10 @@
         "manipulate_relations": "Manipulate relations",
         "mark_as_always_of_current_type": "Mark name of this entry as distinctly of the current type",
         "entry_is_marked_as_distinctly_of_type": "The name of this entry is marked as distinctly and exclusively in use for entries of the current type.",
-        "fetch_from_wikidata": "Fetch additional information from Wikidata"
+        "fetch_from_wikidata": "Fetch additional information from Wikidata",
+        "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.",
+        "versioning": "Versioning",
+        "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.",
+        "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again."
     }
 }
\ No newline at end of file
diff --git a/nodac/id/basis.json b/nodac/id/basis.json
index eeade508..1f0a430f 100644
--- a/nodac/id/basis.json
+++ b/nodac/id/basis.json
@@ -149,6 +149,10 @@
         "manipulate_relations": "Manipulate relations",
         "mark_as_always_of_current_type": "Mark name of this entry as distinctly of the current type",
         "entry_is_marked_as_distinctly_of_type": "The name of this entry is marked as distinctly and exclusively in use for entries of the current type.",
-        "fetch_from_wikidata": "Fetch additional information from Wikidata"
+        "fetch_from_wikidata": "Fetch additional information from Wikidata",
+        "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.",
+        "versioning": "Versioning",
+        "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.",
+        "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again."
     }
 }
\ No newline at end of file
diff --git a/nodac/ro/basis.json b/nodac/ro/basis.json
index 8eb40307..6f3c142e 100644
--- a/nodac/ro/basis.json
+++ b/nodac/ro/basis.json
@@ -149,6 +149,10 @@
         "manipulate_relations": "Manipulate relations",
         "mark_as_always_of_current_type": "Mark name of this entry as distinctly of the current type",
         "entry_is_marked_as_distinctly_of_type": "The name of this entry is marked as distinctly and exclusively in use for entries of the current type.",
-        "fetch_from_wikidata": "Fetch additional information from Wikidata"
+        "fetch_from_wikidata": "Fetch additional information from Wikidata",
+        "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.",
+        "versioning": "Versioning",
+        "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.",
+        "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again."
     }
 }
\ No newline at end of file
diff --git a/nodac/ru/basis.json b/nodac/ru/basis.json
index da83616e..0934c02c 100644
--- a/nodac/ru/basis.json
+++ b/nodac/ru/basis.json
@@ -149,6 +149,10 @@
         "manipulate_relations": "Manipulate relations",
         "mark_as_always_of_current_type": "Mark name of this entry as distinctly of the current type",
         "entry_is_marked_as_distinctly_of_type": "The name of this entry is marked as distinctly and exclusively in use for entries of the current type.",
-        "fetch_from_wikidata": "Fetch additional information from Wikidata"
+        "fetch_from_wikidata": "Fetch additional information from Wikidata",
+        "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.",
+        "versioning": "Versioning",
+        "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.",
+        "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again."
     }
 }
\ No newline at end of file
diff --git a/nodac/uk/basis.json b/nodac/uk/basis.json
index 4426d2f8..7cd67380 100644
--- a/nodac/uk/basis.json
+++ b/nodac/uk/basis.json
@@ -149,6 +149,10 @@
         "manipulate_relations": "Manipulate relations",
         "mark_as_always_of_current_type": "Mark name of this entry as distinctly of the current type",
         "entry_is_marked_as_distinctly_of_type": "The name of this entry is marked as distinctly and exclusively in use for entries of the current type.",
-        "fetch_from_wikidata": "Fetch additional information from Wikidata"
+        "fetch_from_wikidata": "Fetch additional information from Wikidata",
+        "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.",
+        "versioning": "Versioning",
+        "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.",
+        "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again."
     }
 }
\ No newline at end of file