docs: update VCS integration articles

Author: rohalskyy

src/content/docs/crowdin/integrations/azure-repos.mdx

@@ -91,6 +91,10 @@ When translations are finished and your languages are ready to go live, Crowdin
 
 By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it.
 
+<Aside type="tip">
+  We recommend deleting the `l10n_` branch from your repository after merging the pull request to prevent potential conflicts. Crowdin will automatically recreate the service branch when new translations are ready to be synced.
+</Aside>
+
 ### Synchronization Settings
 
 Configure the synchronization settings according to your needs and preferences.
@@ -108,6 +112,10 @@ To import existing translations from your repo, select one of the following opti
 
 By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo.
 
+<Aside type="tip">
+  We recommend importing existing translations from the repository only once during the integration setup. Afterward, treat Crowdin as the source of truth and manage translations exclusively in Crowdin to prevent overriding unapproved translations.
+</Aside>
+
 Click **Upload translations options** to access the following additional options:
 
 * **Allow target translation to match source**
@@ -209,7 +217,9 @@ By default, the translations stored on the repo are uploaded to Crowdin during t
 <Image src={uploadTranslations} alt="Integration Upload Translations" />
 
 <Aside type="caution" title="Limitations">
-  The *Sync Translations to Crowdin* option is available for file-based projects only.
+  * The **Sync Translations to Crowdin** option is available for file-based projects only.
+  * Use this feature with caution if translation is already in progress.<br/>
+  Manually uploading translations from the repo may override unapproved translations currently in the project, similar to the [**Always import new translations from the repository**](#import-existing-translations) option.
 </Aside>
 
 ## Q&A

src/content/docs/crowdin/integrations/bitbucket.mdx

@@ -85,6 +85,10 @@ When translations are finished and your languages are ready to go live, Crowdin
 
 By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it.
 
+<Aside type="tip">
+  We recommend deleting the `l10n_` branch from your repository after merging the pull request to prevent potential conflicts. Crowdin will automatically recreate the service branch when new translations are ready to be synced.
+</Aside>
+
 ### Synchronization Settings
 
 Configure the synchronization settings according to your needs and preferences.
@@ -102,6 +106,10 @@ To import existing translations from your repo, select one of the following opti
 
 By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo.
 
+<Aside type="tip">
+  We recommend importing existing translations from the repository only once during the integration setup. Afterward, treat Crowdin as the source of truth and manage translations exclusively in Crowdin to prevent overriding unapproved translations.
+</Aside>
+
 Click **Upload translations options** to access the following additional options:
 
 * **Allow target translation to match source**
@@ -203,7 +211,9 @@ By default, the translations stored on the repo are uploaded to Crowdin during t
 <Image src={uploadTranslations} alt="Bitbucket Upload Translations" />
 
 <Aside type="caution" title="Limitations">
-  The *Sync Translations to Crowdin* option is available for file-based projects only.
+  * The **Sync Translations to Crowdin** option is available for file-based projects only.
+  * Use this feature with caution if translation is already in progress.<br/>
+  Manually uploading translations from the repo may override unapproved translations currently in the project, similar to the [**Always import new translations from the repository**](#import-existing-translations) option.
 </Aside>
 
 ## Q&A

src/content/docs/crowdin/integrations/github.mdx

@@ -96,6 +96,10 @@ When translations are finished and your languages are ready to go live, Crowdin
 
 By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it.
 
+<Aside type="tip">
+  We recommend deleting the `l10n_` branch from your repository after merging the pull request to prevent potential conflicts. Crowdin will automatically recreate the service branch when new translations are ready to be synced.
+</Aside>
+
 ### Synchronization Settings
 
 Configure the synchronization settings according to your needs and preferences.
@@ -113,6 +117,10 @@ To import existing translations from your repo, select one of the following opti
 
 By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo.
 
+<Aside type="tip">
+  We recommend importing existing translations from the repository only once during the integration setup. Afterward, treat Crowdin as the source of truth and manage translations exclusively in Crowdin to prevent overriding unapproved translations.
+</Aside>
+
 Click **Upload translations options** to access the following additional options:
 
 * **Allow target translation to match source**
@@ -214,7 +222,9 @@ By default, the translations stored on the repo are uploaded to Crowdin during t
 <Image src={uploadTranslations} alt="GitHub Upload Translations" />
 
 <Aside type="caution" title="Limitations">
-  The *Sync Translations to Crowdin* option is available for file-based projects only.
+  * The **Sync Translations to Crowdin** option is available for file-based projects only.
+  * Use this feature with caution if translation is already in progress.<br/>
+  Manually uploading translations from the repo may override unapproved translations currently in the project, similar to the [**Always import new translations from the repository**](#import-existing-translations) option.
 </Aside>
 
 ## Q&A

src/content/docs/crowdin/integrations/gitlab.mdx

@@ -96,6 +96,10 @@ When translations are finished and your languages are ready to go live, Crowdin
 
 By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it.
 
+<Aside type="tip">
+  We recommend deleting the `l10n_` branch from your repository after merging the merge request to prevent potential conflicts. Crowdin will automatically recreate the service branch when new translations are ready to be synced.
+</Aside>
+
 ### Synchronization Settings
 
 Configure the synchronization settings according to your needs and preferences.
@@ -113,6 +117,10 @@ To import existing translations from your repo, select one of the following opti
 
 By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo.
 
+<Aside type="tip">
+  We recommend importing existing translations from the repository only once during the integration setup. Afterward, treat Crowdin as the source of truth and manage translations exclusively in Crowdin to prevent overriding unapproved translations.
+</Aside>
+
 Click **Upload translations options** to access the following additional options:
 
 * **Allow target translation to match source**
@@ -214,7 +222,9 @@ By default, the translations stored on the repo are uploaded to Crowdin during t
 <Image src={uploadTranslations} alt="GitLab Integration Upload Translations" />
 
 <Aside type="caution" title="Limitations">
-  The *Sync Translations to Crowdin* option is available for file-based projects only.
+  * The **Sync Translations to Crowdin** option is available for file-based projects only.
+  * Use this feature with caution if translation is already in progress.<br/>
+  Manually uploading translations from the repo may override unapproved translations currently in the project, similar to the [**Always import new translations from the repository**](#import-existing-translations) option.
 </Aside>
 
 ## Q&A

src/content/docs/enterprise/integrations/azure-repos.mdx

@@ -90,6 +90,10 @@ When translations are finished and your languages are ready to go live, Crowdin
 
 By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it.
 
+<Aside type="tip">
+  We recommend deleting the `l10n_` branch from your repository after merging the pull request to prevent potential conflicts. Crowdin Enterprise will automatically recreate the service branch when new translations are ready to be synced.
+</Aside>
+
 ### Synchronization Settings
 
 Configure the synchronization settings according to your needs and preferences.
@@ -107,6 +111,10 @@ To import existing translations from your repo, select one of the following opti
 
 By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo.
 
+<Aside type="tip">
+  We recommend importing existing translations from the repository only once during the integration setup. Afterward, treat Crowdin Enterprise as the source of truth and manage translations exclusively in Crowdin Enterprise to prevent overriding unapproved translations.
+</Aside>
+
 Click **Upload translations options** to access the following additional options:
 
 * **Allow target translation to match source**
@@ -206,7 +214,9 @@ Alternatively, if you need to sync only one branch separately, click <Icon name=
 By default, the translations stored on the repo are uploaded to Crowdin Enterprise during the first synchronization only. To upload translations to Crowdin Enterprise manually, click <Icon name="mdi:dots-vertical" class="inline-icon" /> icon next to the **Sync Now** button, and click **Sync Translations to Crowdin Enterprise**. The integration will upload existing translations to your Crowdin Enterprise project.
 
 <Aside type="caution" title="Limitations">
-  The *Sync Translations to Crowdin Enterprise* option is available for file-based projects only.
+  * The **Sync Translations to Crowdin Enterprise** option is available for file-based projects only.
+  * Use this feature with caution if translation is already in progress.<br/>
+  Manually uploading translations from the repo may override unapproved translations currently in the project, similar to the [**Always import new translations from the repository**](#import-existing-translations) option.
 </Aside>
 
 ## Q&A

src/content/docs/enterprise/integrations/bitbucket.mdx

@@ -84,6 +84,10 @@ When translations are finished and your languages are ready to go live, Crowdin
 
 By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it.
 
+<Aside type="tip">
+  We recommend deleting the `l10n_` branch from your repository after merging the pull request to prevent potential conflicts. Crowdin Enterprise will automatically recreate the service branch when new translations are ready to be synced.
+</Aside>
+
 ### Synchronization Settings
 
 Configure the synchronization settings according to your needs and preferences.
@@ -101,6 +105,10 @@ To import existing translations from your repo, select one of the following opti
 
 By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo.
 
+<Aside type="tip">
+  We recommend importing existing translations from the repository only once during the integration setup. Afterward, treat Crowdin Enterprise as the source of truth and manage translations exclusively in Crowdin Enterprise to prevent overriding unapproved translations.
+</Aside>
+
 Click **Upload translations options** to access the following additional options:
 
 * **Allow target translation to match source**
@@ -200,7 +208,9 @@ Alternatively, if you need to sync only one branch separately, click <Icon name=
 By default, the translations stored on the repo are uploaded to Crowdin Enterprise during the first synchronization only. To upload translations to Crowdin Enterprise manually, click <Icon name="mdi:dots-vertical" class="inline-icon" /> icon next to the **Sync Now** button, and click **Sync Translations to Crowdin Enterprise**. The integration will upload existing translations to your Crowdin Enterprise project.
 
 <Aside type="caution" title="Limitations">
-  The *Sync Translations to Crowdin Enterprise* option is available for file-based projects only.
+  * The **Sync Translations to Crowdin Enterprise** option is available for file-based projects only.
+  * Use this feature with caution if translation is already in progress.<br/>
+  Manually uploading translations from the repo may override unapproved translations currently in the project, similar to the [**Always import new translations from the repository**](#import-existing-translations) option.
 </Aside>
 
 ## Q&A

src/content/docs/enterprise/integrations/github.mdx

@@ -95,6 +95,10 @@ When translations are finished and your languages are ready to go live, Crowdin
 
 By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it.
 
+<Aside type="tip">
+  We recommend deleting the `l10n_` branch from your repository after merging the pull request to prevent potential conflicts. Crowdin Enterprise will automatically recreate the service branch when new translations are ready to be synced.
+</Aside>
+
 ### Synchronization Settings
 
 Configure the synchronization settings according to your needs and preferences.
@@ -112,6 +116,10 @@ To import existing translations from your repo, select one of the following opti
 
 By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo.
 
+<Aside type="tip">
+  We recommend importing existing translations from the repository only once during the integration setup. Afterward, treat Crowdin Enterprise as the source of truth and manage translations exclusively in Crowdin Enterprise to prevent overriding unapproved translations.
+</Aside>
+
 Click **Upload translations options** to access the following additional options:
 
 * **Allow target translation to match source**
@@ -211,7 +219,9 @@ Alternatively, if you need to sync only one branch separately, click <Icon name=
 By default, the translations stored on the repo are uploaded to Crowdin Enterprise during the first synchronization only. To upload translations to Crowdin Enterprise manually, click <Icon name="mdi:dots-vertical" class="inline-icon" /> icon next to the **Sync Now** button, and click **Sync Translations to Crowdin Enterprise**. The integration will upload existing translations to your Crowdin Enterprise project.
 
 <Aside type="caution" title="Limitations">
-  The *Sync Translations to Crowdin Enterprise* option is available for file-based projects only.
+  * The **Sync Translations to Crowdin Enterprise** option is available for file-based projects only.
+  * Use this feature with caution if translation is already in progress.<br/>
+  Manually uploading translations from the repo may override unapproved translations currently in the project, similar to the [**Always import new translations from the repository**](#import-existing-translations) option.
 </Aside>
 
 ## Q&A

src/content/docs/enterprise/integrations/gitlab.mdx

@@ -95,6 +95,10 @@ When translations are finished and your languages are ready to go live, Crowdin
 
 By default, `l10n_` is added to the created service branch name. If necessary, you can easily change it.
 
+<Aside type="tip">
+  We recommend deleting the `l10n_` branch from your repository after merging the merge request to prevent potential conflicts. Crowdin Enterprise will automatically recreate the service branch when new translations are ready to be synced.
+</Aside>
+
 ### Synchronization Settings
 
 Configure the synchronization settings according to your needs and preferences.
@@ -112,6 +116,10 @@ To import existing translations from your repo, select one of the following opti
 
 By default, the first option is selected to import translations only once. Alternatively, you can clear both options if you don’t want to import translations from your repo.
 
+<Aside type="tip">
+  We recommend importing existing translations from the repository only once during the integration setup. Afterward, treat Crowdin Enterprise as the source of truth and manage translations exclusively in Crowdin Enterprise to prevent overriding unapproved translations.
+</Aside>
+
 Click **Upload translations options** to access the following additional options:
 
 * **Allow target translation to match source**
@@ -211,7 +219,9 @@ Alternatively, if you need to sync only one branch separately, click <Icon name=
 By default, the translations stored on the repo are uploaded to Crowdin Enterprise during the first synchronization only. To upload translations to Crowdin Enterprise manually, click <Icon name="mdi:dots-vertical" class="inline-icon" /> icon next to the **Sync Now** button, and click **Sync Translations to Crowdin Enterprise**. The integration will upload existing translations to your Crowdin Enterprise project.
 
 <Aside type="caution" title="Limitations">
-  The *Sync Translations to Crowdin Enterprise* option is available for file-based projects only.
+  * The **Sync Translations to Crowdin Enterprise** option is available for file-based projects only.
+  * Use this feature with caution if translation is already in progress.<br/>
+  Manually uploading translations from the repo may override unapproved translations currently in the project, similar to the [**Always import new translations from the repository**](#import-existing-translations) option.
 </Aside>
 
 ## Q&A