Apply docs suggestions from Sean's review

Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com>

Author: liamjpeters

docs/Cmdlets/New-ScriptAnalyzerSettingsFile.md

@@ -28,10 +28,10 @@ When **BaseOnPreset** is not provided, the generated file includes all current r
 `IncludeRules` list and populates the `Rules` section with all configurable properties, set to their
 default values. Both modes also include `CustomRulePath`, `RecurseCustomRulePath`, and
 `IncludeDefaultRules` keys with descriptive comments so the file is immediately ready for
-customisation.
+customization.
 
 If a settings file already exists at the target path, the cmdlet emits a terminating error unless
-the **Force** parameter is specified - in which case it is overwritten.
+the **Force** parameter is specified - in which case it's overwritten.
 
 ## EXAMPLES
 
@@ -175,7 +175,8 @@ The output file is always named `PSScriptAnalyzerSettings.psd1` so that the auto
 discovery in `Invoke-ScriptAnalyzer` picks it up when analysing scripts in the same directory.
 
 Note: Relative paths in `CustomRulePath` are resolved from the caller's current working directory,
-not from the location of the settings file. This matches `Invoke-ScriptAnalyzer` behaviour.
+Relative paths in `CustomRulePath` are resolved from the caller's current working directory,
+not from the location of the settings file. This matches `Invoke-ScriptAnalyzer` behavior.
 
 ## RELATED LINKS