Fix grammar

Author: johlju

.github/instructions/dsc-community-style-guidelines-integration-tests.instructions.md

@@ -19,7 +19,7 @@ This helper is provided in the build pipeline and is not required locally.
 
 All integration tests must use the code block below before the first
 `Describe` block. The following code sets up the integration test
-environment and it will make sure the module being tested is available:
+environment and ensures the module under test is available:
 
 ```powershell
 [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSUseDeclaredVarsMoreThanAssignments', '', Justification = 'Suppressing this rule because Script Analyzer does not understand Pester syntax.')]

.github/instructions/dsc-community-style-guidelines-powershell.instructions.md

@@ -39,7 +39,8 @@ applyTo: "**/*.psm1,**/*.psd1,**/*.ps1"
 
 - Single line: `@('one', 'two', 'three')`
 - Multi-line: each element on separate line with proper indentation
-- Return statement should not use comma operator to cast to array
+- Do not use the unary comma operator (`,`) in return statements to force
+  an array
 
 ### Hashtables
 

.github/instructions/dsc-community-style-guidelines.instructions.md

@@ -57,7 +57,7 @@ reusable.
 
 ## Private functions
 
-Before creating a private function, check if it there is an available command in
+Before creating a private function, check if there is an available command in
 the module [DscResource.Common](https://raw.githubusercontent.com/wiki/dsccommunity/DscResource.Common/_Sidebar.md) that can be used.
 
 Private functions (helper functions) must each have their own script file,
@@ -78,6 +78,6 @@ Place unit tests for class-based resources in tests/Unit/Classes,
 for public commands in tests/Unit/Public, and
 for private functions in tests/Unit/Private.
 
-### Integration tests
+## Integration tests
 
 All public commands must have an integration test in tests/Integration/Commands.