diff --git a/services/notifications/README.md b/services/notifications/README.md
index ddf6f8a03..2972ee119 100644
--- a/services/notifications/README.md
+++ b/services/notifications/README.md
@@ -51,6 +51,8 @@ The language code pattern is composed of `language[_territory]` where  `language
 
 For example, for the language `de`, one needs to place the corresponding translation files to `{NOTIFICATIONS_TRANSLATION_PATH}/de/LC_MESSAGES/translations.po`.
 
+<!-- also see the userlog readme -->
+
 Important: For the time being, the embedded ownCloud Web frontent only supports the main language-code but does not handle any territory. When strings are available in the language-code `language_territory`, the web frontend does not see it as it only requests `language`. As impact, any translations made must exist in the requested `language` to avoid a fallback to the default.
 
 ### Translation Rules
diff --git a/services/userlog/README.md b/services/userlog/README.md
index d2ae335c6..185f08ee5 100644
--- a/services/userlog/README.md
+++ b/services/userlog/README.md
@@ -46,6 +46,8 @@ The language code pattern is composed of `language[_territory]` where  `language
 
 For example, for the language `de`, one needs to place the corresponding translation files to `{USERLOG_TRANSLATION_PATH}/de_DE/LC_MESSAGES/userlog.po`.
 
+<!-- also see the notifications readme -->
+
 Important: For the time being, the embedded ownCloud Web frontent only supports the main language-code but does not handle any territory. When strings are available in the language-code `language_territory`, the web frontend does not see it as it only requests `language`. As impact, any translations made must exist in the requested `language` to avoid a fallback to the default.
 
 ### Translation Rules