[TA-2697] Append documentation for mapping variables

Author: LaberionAjvazi

DOCUMENTATION.md

@@ -293,14 +293,17 @@ You can also use the `--spaceMappings` flag to provide a mapping of packages to
 content-cli import packages -p <profileName> --file <exportedPackagesFile> --spaceMappings <packageKey1>:<targetSpaceKey1> <packageKey2>:<targetSpaceKey2> ...
 ```
 
-By default, all variables are assigned to the imported packages as defined in the `manifest.yml` file of the exported packages. Alternatively, if you want to update only the dataModel variables, you can do so by using the --dataModelMappingsFile option and providing the output file from
-the data pool import command.
+By default, all variables are assigned to the imported packages as defined in the `manifest.yml` file of the exported packages. 
+Alternatively, if you want to update only the dataModel variables, you can do so by using the --dataModelMappingsFile option and 
+providing the output file from the data pool import command.
 
 ```
 // Example usage of dataModelMappingsFile
 content-cli import packages -p <profileName> --file <exportedPackagesFile> --dataModelMappingsFile <dataModelMappingsFile>
 ```
 
+**Note: The --dataModelMappingsFile option is deprecated and will be removed in future releases.**
+
 By default, you can not overwrite a package in the target team. To do this you can use the overwrite flag --overwrite
 
 ```