Normalize spelling behaviour -> behavior

Documentation/Changelog.md

@@ -101,7 +101,7 @@ coverlet.collector 6.0.0
 
 ### Breaking changes
 - New parameter `ExcludeAssembliesWithoutSources` to control automatic assembly exclusion [1164](https://github.com/coverlet-coverage/coverlet/issues/1164). The parameter `InstrumentModulesWithoutLocalSources` has been removed. since it can be handled by setting `ExcludeAssembliesWithoutSources` to `None`.
-- The default heuristics for determining whether to instrument an assembly has been changed. In previous versions any missing source file was taken as a signal that it was a third-party project that shouldn't be instrumented, with exceptions for some common file name patterns for source generators. Now only assemblies where no source files at all can be found are excluded from instrumentation, and the code for detecting source generator files have been removed. To get back to the behaviour that at least one missing file is sufficient to exclude an assembly, set `ExcludeAssembliesWithoutSources` to `MissingAny`, or use assembly exclusion filters for more fine-grained control.
+- The default heuristics for determining whether to instrument an assembly has been changed. In previous versions any missing source file was taken as a signal that it was a third-party project that shouldn't be instrumented, with exceptions for some common file name patterns for source generators. Now only assemblies where no source files at all can be found are excluded from instrumentation, and the code for detecting source generator files have been removed. To get back to the behavior that at least one missing file is sufficient to exclude an assembly, set `ExcludeAssembliesWithoutSources` to `MissingAny`, or use assembly exclusion filters for more fine-grained control.
 
 ## Release date 2022-10-29
 ### Packages

Documentation/DriversFeatures.md

@@ -2,7 +2,7 @@
 
 All Coverlet drivers share the same coverage engine. Since version 3.0.0, we've consolidated versioning across drivers, so for every new release, all drivers will have the same version number.
 
-We think that keeping the versions in sync better expresses the set of features every release will have. This does not mean that all drivers will support every functionality/feature or have the same behaviours, since they are limited by the context they're running in.
+We think that keeping the versions in sync better expresses the set of features every release will have. This does not mean that all drivers will support every functionality/feature or have the same behaviors, since they are limited by the context they're running in.
 
 In the table below we keep track of main differences:
 

Documentation/GlobalTool.md

@@ -176,7 +176,7 @@ You can specify the `--threshold-type` option multiple times. Valid values inclu
 coverlet <ASSEMBLY> --target <TARGET> --targetargs <TARGETARGS> --threshold 80 --threshold-type line --threshold-type method
 ```
 
-By default, Coverlet will validate the threshold value against the coverage result of each module. The `--threshold-stat` option allows you to change this behaviour and can have any of the following values:
+By default, Coverlet will validate the threshold value against the coverage result of each module. The `--threshold-stat` option allows you to change this behavior and can have any of the following values:
 
 * Minimum (Default): Ensures the coverage result of each module isn't less than the threshold
 * Total: Ensures the total combined coverage result of all modules isn't less than the threshold

Documentation/KnownIssues.md

@@ -155,7 +155,7 @@ or by adding the property `<CopyLocalLockFileAssemblies>` to the project file
 
 NB. This **DOESN'T ALWAYS WORK**, for example in case of the shared framework <https://github.com/dotnet/cli/issues/12705#issuecomment-536686785>
 
-We can do nothing at the moment as this is a build behaviour out of our control.
+We can do nothing at the moment as this is a build behavior out of our control.
 
 For .NET runtime version >= 3.0 the new default behavior is to copy all assets to the build output (CopyLocalLockFileAssemblies=true) <https://github.com/dotnet/cli/issues/12705#issuecomment-535150372>, unfortunately the issue could still arise.
 

Documentation/MSBuildIntegration.md

@@ -120,7 +120,7 @@ You can do the same for `Threshold` as well.
 dotnet test /p:CollectCoverage=true /p:Threshold=\"80,100,70\" /p:ThresholdType=\"line,branch,method\"
 ```
 
-By default, Coverlet will validate the threshold value against the coverage result of each module. The `/p:ThresholdStat` option allows you to change this behaviour and can have any of the following values:
+By default, Coverlet will validate the threshold value against the coverage result of each module. The `/p:ThresholdStat` option allows you to change this behavior and can have any of the following values:
 
 * Minimum (Default): Ensures the coverage result of each module isn't less than the threshold
 * Total: Ensures the total combined coverage result of all modules isn't less than the threshold