diff --git a/docs/administration/project_organization/project_organization.md b/docs/administration/project_organization/project_organization.md
index 0ab2682a4c..7ab13f823d 100644
--- a/docs/administration/project_organization/project_organization.md
+++ b/docs/administration/project_organization/project_organization.md
@@ -28,15 +28,6 @@ They can be referenced as relative to the root, for example `assets/js/script.j
 
 All project assets are accessible through the `assets` path.
 
-??? note "Removing `assets` manually"
-
-    If you ever remove the `assets` folder manually, you need to dump translations before performing
-    the `yarn encore <dev|prod>` command:
-    
-    ```
-    php bin/console bazinga:js-translation:dump assets --merge-domains
-    ```
-
 ## Configuration
 
 You project's configuration is placed in the respective files in `config/packages`.
diff --git a/docs/multisite/languages/back_office_translations.md b/docs/multisite/languages/back_office_translations.md
index 238bcf4c67..2bb13c845d 100644
--- a/docs/multisite/languages/back_office_translations.md
+++ b/docs/multisite/languages/back_office_translations.md
@@ -30,7 +30,7 @@ If your browser language is set to French, the Back Office will be displayed in
 
     `ibexa.system.<siteaccess>.user_preferences.additional_translations: ['pl_PL', 'fr_FR']`
 
-    Then, run `composer run post-update-cmd` and clear the cache.
+    Then, run `composer run post-update-cmd` which include a cache clear.
 
 ### Contributing Back Office translations
 
@@ -120,4 +120,4 @@ The language to display will then be selected automatically based on [user prefe
 
 !!! note
 
-    You may need to clear the cache after adding new translations, before they are available in the Back Office.
+    Run `composer run post-update-cmd` which install your translations to JavaScript through Bazinga, and also clear the cache.