[TASK] Explain string approval in Crowdin better (#6209)

* [TASK] Explain string approval in Crowdin better

* Update Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst

Co-authored-by: David Bruchmann <[email protected]>

* Update Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst

Co-authored-by: David Bruchmann <[email protected]>

* Update Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst

Co-authored-by: Chris Müller <[email protected]>

* Update Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst

Co-authored-by: Chris Müller <[email protected]>

---------

Co-authored-by: David Bruchmann <[email protected]>
Co-authored-by: Chris Müller <[email protected]>

Author: 3 people

Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst

@@ -178,8 +178,11 @@ Why is translated content not available in TYPO3?
 -------------------------------------------------
 
 *   The translated strings are not approved. As an owner of the Crowdin project
-    you can approve them yourself. With the next run of the Crowdin Bridge
-    the translations should be available.
+    (for example, if you're the extension owner) or as proofreader you can approve
+    strings by yourself. Otherwise please ask in the Slack channel
+    `#typo3-localization-team <https://typo3.slack.com/app_redirect?channel=CR75200FL>`__
+    for approval. With the next run of the Crowdin Bridge the translations
+    should be available (approx. every two hours).
 
 *   Only translations provided from the following default branches in your
     repository are used: `main`, `master`, `release`, `develop`, `dev`,