Merge pull request #111779 from mgreenegit/patch-11

make compilation clear for new users

Author: PRMerger18

articles/governance/policy/how-to/guest-configuration-create-linux.md

@@ -119,8 +119,7 @@ end
 
 Save this file with name `linux-path.rb` in a new folder named `controls` inside the `linux-path` directory.
 
-Finally, create a configuration, import the **GuestConfiguration** resource module, and use the
-`ChefInSpecResource` resource to set the name of the InSpec profile.
+Finally, create a configuration, import the **PSDesiredStateConfiguration** resource module, and compile the configuration.
 
 ```powershell
 # Define the configuration and import GuestConfiguration
@@ -138,13 +137,19 @@ Configuration AuditFilePathExists
 }
 
 # Compile the configuration to create the MOF files
+import-module PSDesiredStateConfiguration
 AuditFilePathExists -out ./Config
 ```
 
+Save this file with name `config.ps1` in the project folder. Run it in PowerShell by executing `./config.ps1`
+in the terminal. A new mof file will be created.
+
 The `Node AuditFilePathExists` command isn't technically required but it produces a file named
 `AuditFilePathExists.mof` rather than the default, `localhost.mof`. Having the .mof file name follow
 the configuration makes it easy to organize many files when operating at scale.
 
+
+
 You should now have a project structure as below:
 
 ```file
@@ -175,8 +180,8 @@ Run the following command to create a package using the configuration given in t
 ```azurepowershell-interactive
 New-GuestConfigurationPackage `
   -Name 'AuditFilePathExists' `
-  -Configuration './Config/AuditFilePathExists.mof'
-  -ChefProfilePath './'
+  -Configuration './Config/AuditFilePathExists.mof' `
+  -ChefInSpecProfilePath './'
 ```
 
 After creating the Configuration package but before publishing it to Azure, you can test the package from your workstation or CI/CD environment. The GuestConfiguration cmdlet `Test-GuestConfigurationPackage` includes the same agent in your
@@ -196,7 +201,7 @@ Run the following command to test the package created by the previous step:
 
 ```azurepowershell-interactive
 Test-GuestConfigurationPackage `
-  -Path ./AuditFilePathExists.zip
+  -Path ./AuditFilePathExists/AuditFilePathExists.zip
 ```
 
 The cmdlet also supports input from the PowerShell pipeline. Pipe the output of

articles/governance/policy/how-to/guest-configuration-create.md

@@ -220,9 +220,12 @@ Configuration AuditBitLocker
 }
 
 # Compile the configuration to create the MOF files
-AuditBitLocker -out ./Config
+AuditBitLocker ./Config
 ```
 
+Save this file with name `config.ps1` in the project folder. Run it in PowerShell by executing `./config.ps1`
+in the terminal. A new mof file will be created.
+
 The `Node AuditBitlocker` command isn't technically required but it produces a file named
 `AuditBitlocker.mof` rather than the default, `localhost.mof`. Having the .mof file name follow the
 configuration makes it easy to organize many files when operating at scale.