update docs

docs/sat.md

@@ -177,9 +177,9 @@ configurations:
 
 In the example above, we are telling manta we want Alps to use the ansible in repo `test_layer` based on git tag `1.0`. As a consequence, Manta will resolve the git tag to its commit id, set this value in the sat file configuration layer and submit the configuration craetion task to Alps management plane.
 
-### Send values in CLI
+### Expand SAT template file variables with CLI arguments
 
-Manta can expand the variables in the template file with a vars file or through CLI
+Manta can expand the variables in the template file with a vars file or through CLI. Users can submit values in both vars file and as CLI arguments, if a variable value exists in both (vars file and as a CLI argument) then the CLI argument will take preference and overwrite the value in the vars file.
 
 eg
 
@@ -191,9 +191,12 @@ manta a sat -t my_sat_file.yml -v "version=v1.2.0"
 
 eg
 
-Submit a sat template file and a vars file, the template file contains a `version` variable which also exists in the vars file and also send through CLI, the CLI argument value has priority therefore will overwrite the `varsion` value in the vars file.
+This second example shows an example where a user submits 2 different values for the `version` variable. CLI arguments take preference and the final value for the `version` variable is `v1.2.0`.
 
 ```bash
+cat my_sat_vars.yml
+version: 0.0.5
+
 manta a sat -t my_sat_file.yml -f my_sat_vars.yaml -v "version=v1.2.0"
 ```