Enhancements

Signed-off-by: Shivani Karikar <[email protected]>

src/courses/user/07.md

@@ -26,13 +26,13 @@ This profile uses InSpec Inputs to make the tests more flexible. You can provide
 **DO** create a separate file (often named `inputs.yml`) or pass values via the command line to overwrite default values to tailor the profile.
 :::
 
-The `inputs` configured in the `inspec.yml` file are **profile definitions and defaults for the profile** and not for the user. Automated InSpec scans are frequently run from a script, inside a pipeline, or some kind of task scheduler where the runner will often not have access to the `inspec.yml`. However, those scripts or pipelines can easily pass an inputs file or command line arguments to modify the default values defined in the `inspec.yml` file.
+The `inputs` configured in the `inspec.yml` file are **profile definitions and defaults for the profile** and not for tailoring. Automated InSpec scans are frequently run from a script, inside a pipeline, or some kind of task scheduler where the runner will often not have access to the `inspec.yml`. However, those scripts or pipelines can easily pass an inputs file or command line arguments to modify the default values defined in the `inspec.yml` file.
 
 To tailor the tested values for your deployment or organizationally defined values, **_you may update the inputs_**.
 
 More information about InSpec inputs can be found in the [InSpec Inputs Documentation](https://docs.chef.io/inspec/inputs/).
 
-## 7.2 Use an --input-file to tailor an InSpec profile
+## 7.2 Use an `--input-file` to tailor an InSpec profile
 
 For the NGINX example, we are going to add the following inputs. Make a new file called `inputs.yml` in your lab environment: