Skip to content

Small edits for mispellings #1989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 2, 2018
Merged

Small edits for mispellings #1989

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions dsc/configData.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,7 +159,7 @@ For example, you could create a file named `MyData.psd1` with the following cont

## Compiling a configuration with configuration data

To compile a configuration for which you have defined configuration data, you pass the cofiguration data as the value of the **ConfigurationData** parameter.
To compile a configuration for which you have defined configuration data, you pass the configuration data as the value of the **ConfigurationData** parameter.

This will create a MOF file for each entry in the **AllNodes** array.
Each MOF file will be named with the `NodeName` property of the corresponding array entry.
Expand Down Expand Up @@ -196,8 +196,8 @@ DSC provides three special variables that can be used in a configuration script:
## Using non-node data

As we've seen in previous examples, the **ConfigurationData** hashtable can have one or more keys in addition to the required **AllNodes** key.
In the examples in this topic, we have used only a single addiontal node, and named it `NonNodeData`.
However, you can define any number of addiontal keys, and name them anything you want.
In the examples in this topic, we have used only a single additional node, and named it `NonNodeData`.
However, you can define any number of additional keys, and name them anything you want.

For an example of using non-node data, see [Separating configuration and environment data](separatingEnvData.md).

Expand Down