Clarify version strategy order in documentation

Updated the configuration documentation to specify that the order in which version strategies are specified does not matter.

Author: selfdocumentingcode

docs/input/docs/reference/mdsource/configuration.source.md

@@ -550,7 +550,9 @@ Example of invalid `Strict`, but valid `Loose`
 
 ### strategies
 
-Specifies which version strategy implementation (one ore more) will be used to determine the next version. Following values are supported and can be combined:
+Specifies which version strategy implementation (one or more) will be used to determine the next version.
+These strategies can be combined, and the order in which they are specified does not matter.
+The configuration accepts the following values:
 
 - Fallback
 - ConfiguredNextVersion