Apply suggestions from code review

Co-authored-by: Magdalena Dziadosz <[email protected]>

docs/content_management/data_migration/exporting_data.md

@@ -136,9 +136,9 @@ Note that you should test your migrations. See [Importing data](importing_data.m
 
 !!! caution
 
-    `--siteaccess` option usage can be relevant on multi-languages repository.
-    You must export with the SiteAccess supporting all the languages, or migration skips translations in non-supported languages.
-    It is recommended to use the SiteAccess of the Back Office of the targeted repository.
+    The `--siteaccess` option usage can be relevant for a multi-language repository.
+    You must export with a SiteAccess that supports all languages, or the migration skips translations in non-supported languages. 
+    It is recommended to use the SiteAccess from the Back Office of the targeted repository.
 
 ## type
 

docs/content_management/data_migration/importing_data.md

@@ -22,10 +22,9 @@ Migrations store execution metadata in the `ibexa_migrations` database table.
 This allows incremental upgrades:
 the `ibexa:migrations:migrate` command ignores files that it had previously executed.
 
-Notice the `--siteaccess` option usage.
-This can be important, especially when several languages are used.
-You must import with the SiteAccess supporting all the languages, or migration skips translations in non-supported languages.
-It's recommended to use the SiteAccess of the Back Office of the targeted repository.
+Notice that `--siteaccess` option usage is important when several languages are used.
+You must import with a SiteAccess that supports all languages, or the migration skips translations in non-supported languages.
+It's recommended to use the SiteAccess from the Back Office of the targeted repository.
 
 ## Migration step