Skip to content

Commit b062ae3

Browse files
committed
acrolynx fixes
1 parent a64641f commit b062ae3

File tree

2 files changed

+14
-14
lines changed

2 files changed

+14
-14
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ machine.
3333
The process of creating a Guest Configuration artifact, automated testing of the artifact,
3434
creating a policy definition, and publishing the policy,
3535
is entirely automatable using PowerShell.
36-
This module can be installed on a machine running Windows, MacOS, or Linux with
36+
This module can be installed on a machine running Windows, macOS, or Linux with
3737
PowerShell 6.2 or later running locally, or with [Azure Cloud Shell](https://shell.azure.com), or
3838
with the
3939
[Azure PowerShell Core Docker image](https://hub.docker.com/r/azuresdk/azure-powershell-core).
@@ -46,7 +46,7 @@ with the
4646
Operating Systems where the module can be installed:
4747

4848
- Linux
49-
- MacOS
49+
- macOS
5050
- Windows
5151

5252
The Guest Configuration resource module requires the following software:
@@ -79,8 +79,8 @@ To install the **GuestConfiguration** module in PowerShell:
7979

8080
Even in Linux environments, Guest Configuration utilizes Desired State Configuration as a language abstraction.
8181
The implementation is based in native code (C++) so it does not require loading PowerShell at this time.
82-
However, it does require a configuration MOF file describing basic details about the environment. DSC is acting as a "wrapper" for InSpec to standardize how it is executed, how parameters are provided from ARM, and how output is captured and returned to the service.
83-
Very little knowledge of DSC is required
82+
However, it does require a configuration MOF file describing basic details about the environment. DSC is acting as a "wrapper" for InSpec to standardize how it is executed, how parameters are provided from Azure Resource Manager, and how output is captured and returned to the service.
83+
Little knowledge of DSC is required
8484
when working with custom InSpec content.
8585

8686
#### Configuration requirements
@@ -146,7 +146,7 @@ Configuration AuditFilePathExists
146146
AuditFilePathExists -out ./Config
147147
```
148148

149-
Note that the `Node AuditFilePathExists` command is not 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.
149+
The `Node AuditFilePathExists` command is not 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.
150150

151151
You should now have a project structure as below:
152152

@@ -210,7 +210,7 @@ Test-GuestConfigurationPackage `
210210
> New-GuestConfigurationPackage -Name AuditFilePathExists -Configuration ./Config/AuditFilePathExists.mof -ChefProfilePath './' | Test-GuestConfigurationPackage
211211
> ```
212212
213-
The next step is to publish the file to blob storage. The script below contains a function you can use to automate this task. Note that the commands used in the `publish` function require the `Az.Storage` module.
213+
The next step is to publish the file to blob storage. The script below contains a function you can use to automate this task. The commands used in the `publish` function require the `Az.Storage` module.
214214
215215
```azurepowershell-interactive
216216
function publish {
@@ -343,8 +343,8 @@ override values are provided through Azure Policy and don't impact how the Confi
343343
authored or compiled.
344344
345345
With InSpec, parameters are typically handled as input either at runtime or as code using attributes.
346-
Guest Configuration obfuscates this process so input can be provided to ARM when policy is assigned.
347-
An attributes file is automatically created within the machine. It does not need to be included in your project.
346+
Guest Configuration obfuscates this process so input can be provided to Azure Resource Manager when policy is assigned.
347+
An attributes file is automatically created within the machine. You do not need to create and add a file in your project.
348348
There are two steps to adding parameters to your Linux audit project.
349349
350350
Define the input in the Ruby file where you script what to audit on the machine. An example is given below.

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ machine.
3333
The process of creating a Guest Configuration artifact, automated testing of the artifact,
3434
creating a policy definition, and publishing the policy,
3535
is entirely automatable using PowerShell.
36-
This module can be installed on a machine running Windows, MacOS, or Linux with
36+
This module can be installed on a machine running Windows, macOS, or Linux with
3737
PowerShell 6.2 or later running locally, or with [Azure Cloud Shell](https://shell.azure.com), or
3838
with the
3939
[Azure PowerShell Core Docker image](https://hub.docker.com/r/azuresdk/azure-powershell-core).
@@ -46,7 +46,7 @@ with the
4646
Operating Systems where the module can be installed:
4747

4848
- Linux
49-
- MacOS
49+
- macOS
5050
- Windows
5151

5252
The Guest Configuration resource module requires the following software:
@@ -80,7 +80,7 @@ To install the **GuestConfiguration** module in PowerShell:
8080
Guest Configuration utilizes PowerShell Desired State Configuration as a language abstraction
8181
for writing what audit in Windows and how the audits should be performed.
8282
An instance of PowerShell 6.2 is loaded and managed by the agent to host the environment,
83-
so there is no conflict wih usage of PowerShell DSC in Windows PowerShell 5.1, and there is no
83+
so there is no conflict with usage of PowerShell DSC in Windows PowerShell 5.1, and there is no
8484
requirement to pre-install PowerShell 6.2 or later.
8585

8686
For an overview of DSC concepts and terminology, see
@@ -183,7 +183,7 @@ and not communicating with the service.
183183

184184
Create a DSC configuration. The following PowerShell script example creates a configuration
185185
named **AuditBitLocker**, imports the **PsDscResources** resource module, and uses
186-
the `Service` resource to audit for a running service. This can be executed from a Windows or MacOS machine.
186+
the `Service` resource to audit for a running service. The configuration script can be executed from a Windows or macOS machine.
187187

188188
```powershell
189189
# Define the DSC configuration and import GuestConfiguration
@@ -205,7 +205,7 @@ Configuration AuditBitLocker
205205
AuditBitLocker -out ./Config
206206
```
207207

208-
Note that the `Node AuditBitlocker` command is not 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.
208+
The `Node AuditBitlocker` command is not 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.
209209

210210
Once the MOF is compiled, the supporting files must be packaged together. The completed package is
211211
used by Guest Configuration to create the Azure Policy definitions.
@@ -254,7 +254,7 @@ Test-GuestConfigurationPackage `
254254
> New-GuestConfigurationPackage -Name AuditBitlocker -Configuration ./Config/AuditBitlocker.mof | Test-GuestConfigurationPackage
255255
> ```
256256
257-
The next step is to publish the file to blob storage. The script below contains a function you can use to automate this task. Note that the commands used in the `publish` function require the `Az.Storage` module.
257+
The next step is to publish the file to blob storage. The script below contains a function you can use to automate this task. The commands used in the `publish` function require the `Az.Storage` module.
258258
259259
```azurepowershell-interactive
260260
function publish {

0 commit comments

Comments
 (0)