Explain branches in detail for GitHub workflow for Crowdin

Author: brotkrueml

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

@@ -197,6 +197,13 @@ Step-by-step instructions for GitHub
                         ``<source>`` and ``<target>`` elements. If the ``<source>`` elements are missing,
                         Crowdin will not be able to match the translations with the original English labels.
 
+    ..  important::
+        Using the recommended GitHub workflow the GitHub default branch can be
+        mapped to the Crowdin branch name via the attribute :yaml:`crowdin_branch_name`.
+        It is recommended that you always use `main` as the Crowdin branch name.
+        **More than one Crowdin branch (for example via different
+        GitHub branches) is not supported by the Crowdin Bridge!**
+
 Happy translating!
 
 ..  tip::

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

@@ -177,14 +177,26 @@ checkbox.
 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.
-
-*   Only translations provided from the following default branches in your
-    repository are used: `main`, `master`, `release`, `develop`, `dev`,
-    `development`. If you use other branches, the translations are not
-    available — even if they are translated in Crowdin.
+Approval is missing
+~~~~~~~~~~~~~~~~~~~
+
+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.
+
+Integration branch is not recognized
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If the legacy Crowdin <> GitHub integration is used, only translations
+provided from the following default branches in your repository are used:
+`main`, `master`, `release`, `develop`, `dev`, `development`. If you use
+other branches, the translations are not available — even if they are
+translated in Crowdin.
+
+It is recommended to configure the
+:ref:`GitHub workflow as integration for Crowdin <crowdin-extension-integration-github>`,
+this way you define the `crowdin_branch_name` which can be set to
+`main` — independently of your GitHub default branch.
 
 ..  index:: Crowdin; Reconnect your project
 ..  _reconnect-your-project: