@@ -108,7 +108,7 @@ Count Name
108108```
109109
110110The first command saves the output of ` dsc resource list ` to the ` $resources ` variable as an array
111- of PowerShell objects. WHen you first ran the ` dsc resource list ` command, the output in the
111+ of PowerShell objects. When you first ran the ` dsc resource list ` command, the output in the
112112terminal was a table view. By default, when DSC detects that its output is being redirected to a
113113file, variable, or another command in the pipeline, it emits JSON representing the output.
114114Converting the JSON into a PowerShell object with the ` ConvertFrom-Json ` cmdlet enables you to
@@ -164,7 +164,7 @@ For more information about the command, see [dsc resource list][03].
164164
165165## Invoke a resource
166166
167- You can use DSC to directly invoke a resource. When you invoke a resource, you are performing a
167+ You can use DSC to directly invoke a resource. When you invoke a resource, you're performing a
168168specific operation on an _ instance_ of the resource. A resource instance is a specific item the
169169resource represents. The following examples use the ` Microsoft.Windows/Registry ` resource to invoke
170170DSC operations.
@@ -212,8 +212,8 @@ For this example:
212212 want to manage. ` keyPath ` is a _ required_ property for the ` Registry ` resource - you always need
213213 to specify it.
214214- The ` valueName ` property identifies which registry value to manage for the registry key.
215- - The ` _exist ` canonical property indicates whether the registry value should exist. In this example,
216- it's set to ` true ` , indicating the instance should exist.
215+ - The ` _exist ` canonical property indicates whether the registry value should exist. In this
216+ example, it's set to ` true ` , indicating the instance should exist.
217217
218218Run the following command to get the current state of the registry key:
219219
@@ -300,7 +300,7 @@ The output indicates that the resource created the missing instance.
300300Invoking resources directly is useful, but tedious for defining the desired state of a system. You
301301can define a DSC configuration document to describe a set of resource instances together.
302302
303- Copy the following codeblock and save it in a file named `example.dsc.config.yaml`.
303+ Copy the following code block and save it in a file named `example.dsc.config.yaml`.
304304
305305` ` ` yaml
306306$schema: https://aka.ms/dsc/schemas/v3/bundled/config/document.json
0 commit comments