MicrosoftDocs
diff --git a/‎dsc/configData.md
Lines changed: 3 additions & 3 deletions b/‎dsc/configData.md
Lines changed: 3 additions & 3 deletions
diff --git a/‎dsc/configurations.md
Lines changed: 1 addition & 1 deletion b/‎dsc/configurations.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎dsc/decisionMaker.md
Lines changed: 1 addition & 1 deletion b/‎dsc/decisionMaker.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎dsc/scriptResource.md
Lines changed: 3 additions & 3 deletions b/‎dsc/scriptResource.md
Lines changed: 3 additions & 3 deletions
diff --git a/‎reference/3.0/Microsoft.PowerShell.Core/About/about_Operator_Precedence.md
Lines changed: 1 addition & 1 deletion b/‎reference/3.0/Microsoft.PowerShell.Core/About/about_Operator_Precedence.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/3.0/Microsoft.PowerShell.Core/Get-Command.md
Lines changed: 1 addition & 1 deletion b/‎reference/3.0/Microsoft.PowerShell.Core/Get-Command.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/3.0/Microsoft.PowerShell.Core/Get-Help.md
Lines changed: 1 addition & 1 deletion b/‎reference/3.0/Microsoft.PowerShell.Core/Get-Help.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/3.0/Microsoft.PowerShell.Management/Get-Content.md
Lines changed: 1 addition & 1 deletion b/‎reference/3.0/Microsoft.PowerShell.Management/Get-Content.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/3.0/Microsoft.PowerShell.Management/Get-PSDrive.md
Lines changed: 1 addition & 1 deletion b/‎reference/3.0/Microsoft.PowerShell.Management/Get-PSDrive.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/3.0/Microsoft.PowerShell.Management/New-PSDrive.md
Lines changed: 1 addition & 1 deletion b/‎reference/3.0/Microsoft.PowerShell.Management/New-PSDrive.md
Lines changed: 1 addition & 1 deletion
@@ -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.
@@ -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).
 
 
@@ -65,7 +65,7 @@ MyDscConfiguration
 
 ```
 
-In this example, you specify the name of the node by passing it as the **ComputerName** parameter when you compile the configuraton. The name defaults to "localhost".
+In this example, you specify the name of the node by passing it as the **ComputerName** parameter when you compile the configuration. The name defaults to "localhost".
 
 ## Compiling the configuration
 
 
@@ -37,7 +37,7 @@ Configurations are also shareable via the [PowerShell Gallery](https://powershel
 ## Desired State Configuration and DevOps
 
 [DevOps](http://blogs.technet.com/b/ashleymcglone/archive/2015/11/20/devops-for-n00bs-ie-windows-people.aspx) is a combination of people, 
-technologies, and culture that allow for rapid deployment and iteration. 
+process, and tools that allow for rapid deployment and iteration focused on delivering value to end users whether internal or external. 
 DSC was designed with DevOps in mind. 
 Having a single configuration define an environment means that developers can encode their requirements into a configuration, 
 check that configuration into source control, and operations teams can easily deploy code without having to go through error-prone manual processes. 
 
@@ -79,13 +79,13 @@ Configuration ScriptTest
     {
         GetScript = { 
             $currentVersion = Get-Content (Join-Path -Path $env:SYSTEMDRIVE -ChildPath 'version.txt')
-            return @{ 'Version' = "$currentVersion" }
+            return @{ 'Result' = "$currentVersion" }
         }          
         TestScript = { 
             $state = $GetScript
-            if( $state['Version'] -eq $using:version )
+            if( $state['Result'] -eq $using:version )
             {
-                Write-Verbose -Message ('{0} -eq {1}' -f $state['Version'],$using:version)
+                Write-Verbose -Message ('{0} -eq {1}' -f $state['Result'],$using:version)
                 return $true
             }
             Write-Verbose -Message ('Version up-to-date: {0}' -f $using:version)
 
@@ -77,7 +77,7 @@ order:
 |OPERATOR                  |REFERENCE|
 |--------------------------|---------|
 |`-band -bor -bxor`        |[about_Arithmetic_Operators](about_Arithmetic_Operators.md)|
-|`-and -or -xor`           |[about_comparison_operators](about_comparison_operators.md)|
+|`-and -or -xor`           |[about_Logical_Operators](about_logical_operators.md)|
 |`.` (dot-source)          |[about_Scopes](about_Scopes.md)|
 |`&` (call)                |[about_Operators](about_Operators.md)|
 |&#124; (pipeline operator)|[about_Operators](about_Operators.md)|
 
@@ -232,7 +232,7 @@ To detect dynamic parameters that are available only when certain other paramete
 
 To detect the dynamic parameters that a provider adds to a cmdlet, set the value of the **ArgumentList** parameter to a path in the provider drive, such as "WSMan:", "HKLM:" or "Cert:". 
 When the command is a Windows PowerShell provider cmdlet, enter only one path in each command; the provider cmdlets return only the dynamic parameters for the first path the value of **ArgumentList**.
-For information about the provider cmdlets, see about_Providers (http://go.microsoft.com/fwlink/?LinkID=113250).
+For information about the provider cmdlets, see [about_Providers](About/about_Providers.md).
 
 ```yaml
 Type: Object[]
 
@@ -474,7 +474,7 @@ To see the custom cmdlet help for a provider path, go to the provider path locat
 You can also find custom cmdlet help online in the provider help section of the help topics.
 For example, you can find help for the **New-Item** cmdlet in the Wsman:\*\ClientCertificate path (http://go.microsoft.com/fwlink/?LinkID=158676).
 
-For more information about Windows PowerShell providers, see about_Providers (http://go.microsoft.com/fwlink/?LinkID=113250).
+For more information about Windows PowerShell providers, see [about_Providers](About/about_Providers.md).
 
 ```yaml
 Type: String
 
@@ -391,7 +391,7 @@ You cannot pipe input to **Get-Content**.
 **Get-Content** returns strings or bytes.
 The output type depends upon the content that it gets.
 ## NOTES
-* The **Get-Content** cmdlet is designed to work with the data exposed by any provider. To get the providers in your session, use the **Get-PsProvider** cmdlet. For more information, see about_Providers (http://go.microsoft.com/fwlink/?LinkID=113250).
+* The **Get-Content** cmdlet is designed to work with the data exposed by any provider. To get the providers in your session, use the **Get-PsProvider** cmdlet. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
 
 *
 ## RELATED LINKS
 
@@ -300,7 +300,7 @@ You cannot pipe objects to **Get-PSDrive**.
 ### System.Management.Automation.PSDriveInfo
 **Get-PSDrive** returns objects that represent the drives in the session.
 ## NOTES
-* The **Get-PSDrive** cmdlet is designed to work with the data exposed by any provider. To list the providers available in your session, use the Get-PSProvider cmdlet. For more information, see about_Providers (http://go.microsoft.com/fwlink/?LinkID=113250).
+* The **Get-PSDrive** cmdlet is designed to work with the data exposed by any provider. To list the providers available in your session, use the Get-PSProvider cmdlet. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
 * Mapped network drives that are created by using the **Persist** parameter of the New-PSDrive cmdlet are specific to a user account. Mapped network drives that you create in sessions that are started with the "Run as administrator" option or with the credentials of another user are not visible in sessions that are started without explicit credentials or with  the credentials of the current user.
 ## RELATED LINKS
 
 
@@ -366,7 +366,7 @@ You cannot pipe input to this cmdlet.
 ### System.Management.Automation.PSDriveInfo
 
 ## NOTES
-* The **New-PSDrive** cmdlet is designed to work with the data exposed by any provider. To list the providers available in your session, use the Get-PSProvider cmdlet. For more information about providers, see about_Providers (http://go.microsoft.com/fwlink/?LinkID=113250).
+* The **New-PSDrive** cmdlet is designed to work with the data exposed by any provider. To list the providers available in your session, use the Get-PSProvider cmdlet. For more information about providers, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
 * Mapped network drives are specific to a user account. Mapped network drives that you create in sessions that are started with the "Run as administrator" option or with the credential of another user are not visible in session that started without explicit credentials or with the credentials of the current user.
 ## RELATED LINKS
Original file line number	Diff line number	Diff line change
`@@ -79,13 +79,13 @@ Configuration ScriptTest`
`79`	`79`	`{`
`80`	`80`	`GetScript = {`
`81`	`81`	`$currentVersion = Get-Content (Join-Path -Path $env:SYSTEMDRIVE -ChildPath 'version.txt')`
`82`		`- return @{ 'Version' = "$currentVersion" }`
	`82`	`+ return @{ 'Result' = "$currentVersion" }`
`83`	`83`	`}`
`84`	`84`	`TestScript = {`
`85`	`85`	`$state = $GetScript`
`86`		`- if( $state['Version'] -eq $using:version )`
	`86`	`+ if( $state['Result'] -eq $using:version )`
`87`	`87`	`{`
`88`		`- Write-Verbose -Message ('{0} -eq {1}' -f $state['Version'],$using:version)`
	`88`	`+ Write-Verbose -Message ('{0} -eq {1}' -f $state['Result'],$using:version)`
`89`	`89`	`return $true`
`90`	`90`	`}`
`91`	`91`	`Write-Verbose -Message ('Version up-to-date: {0}' -f $using:version)`
Original file line number	Diff line number	Diff line change
`@@ -391,7 +391,7 @@ You cannot pipe input to Get-Content.`
`391`	`391`	`Get-Content returns strings or bytes.`
`392`	`392`	`The output type depends upon the content that it gets.`
`393`	`393`	`## NOTES`
`394`		`-* The Get-Content cmdlet is designed to work with the data exposed by any provider. To get the providers in your session, use the Get-PsProvider cmdlet. For more information, see about_Providers (http://go.microsoft.com/fwlink/?LinkID=113250).`
	`394`	`+* The Get-Content cmdlet is designed to work with the data exposed by any provider. To get the providers in your session, use the Get-PsProvider cmdlet. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).`
`395`	`395`
`396`	`396`	`*`
`397`	`397`	`## RELATED LINKS`