Apply suggestions from review

Co-authored-by: Steve Lee <slee@microsoft.com>
Co-authored-by: Michael Greene <mgreenegit@users.noreply.github.com>

Author: 3 people

docs/concepts/configuration-documents/overview.md

@@ -152,7 +152,7 @@ When you use this command, DSC also:
 - Provides metadata about the operation as a whole and for each resource instance.
 
 ```sh
-dsc config test --file /example.config.dsc.yaml
+dsc config test --file ./example.config.dsc.yaml
 ```
 
 ```yaml

docs/concepts/output-accessibility.md

@@ -62,18 +62,6 @@ Invoke-Item .\myFile.csv
 
 The `Invoke-Item` command opens the file in the default application for CSV files.
 
-### HyperText Markup Language (HTML) format
-
-HTML files can be viewed by web browsers such as **Microsoft Edge**. The following example shows
-how to save the output of a command to an HTML file.
-
-```powershell
-dsc resource list | ConvertFrom-Json | ConvertTo-HTML | Out-File .\myFile.html
-Invoke-Item .\myFile.html
-```
-
-The `Invoke-Item` command opens the file in your default web browser.
-
 ## Reduce the amount of output
 
 One way to improve the accessibility of the output is to reduce the amount of output displayed in

docs/concepts/resources/anatomy.md

@@ -39,7 +39,7 @@ If the JSON file validates against the schema, DSC can use the DSC Resource.
 
 At a minimum, the manifest must define:
 
-- The version of the DSC resource manifest JSON schema it's compatible with.
+- The semantic version (semver) of the DSC resource manifest JSON schema it's compatible with.
 - The fully qualified name of the resource, like `Microsoft.Windows/Registry`. The fully qualified
   name syntax is `<owner>[.<group>][.<area>]/<name>`. The group and area components of the fully
   qualified name enable organizing resources into namespaces.

docs/concepts/resources/capabilities.md

@@ -75,7 +75,17 @@ resource. DSC performs the synthetic test by:
 
 1. Invoking the **Get** operation on the resource to retrieve the actual state of the instance.
 1. Synthetically testing each property for the desired state of an instance against the actual
-   state returned. The synthetic test uses strict, case-sensitive equivalence.
+   state returned. The synthetic test:
+   
+   - Uses strict, case-sensitive equivalence for strings.
+   - Uses simple equivalence for numerical, boolean, and null values.
+   - For arrays, item order doesn't matter. Arrays are considered equivalent if both the desired
+     state and actual state arrays have the same number of items and if each item in the desired
+     state is contained in the actual state array.
+   - For objects, property order doesn't matter. The actual state of the resource can be a superset
+     of the desired state. Objects are considered equivalent if each specified property for the
+     desired state is equal to the same property for the actual state. If an actual state property
+     isn't defined in the desired state, DSC ignores that property for the synthetic test.
 1. If the desired state for a property and the actual state aren't the same, DSC marks the property
    as out of the desired state.
 1. If any properties are out of the desired state, DSC reports the entire instance as not being in

docs/concepts/resources/properties.md

@@ -127,6 +127,9 @@ expectations. These reusable properties are called canonical resource properties
 Any resource that defines a canonical resource property in the instance schema must adhere to the
 requirements and behaviors defined for the canonical property.
 
+Canonical properties always begin with an underscore (`_`). Non-canonical property names should
+never begin with an underscore. The leading underscore is reserved for canonical property names.
+
 For more information about the available canonical properties, see
 [DSC canonical resource properties][02].