fix: alphabetical order

docs/usage/configuration-options.md

@@ -448,6 +448,11 @@ Check out the default value for `commitMessage` to understand how this field is
 This is used to alter `commitMessage` and `prTitle` without needing to copy/paste the whole string.
 The "extra" is usually an identifier of the new version, e.g. "to v1.3.2" or "to tag 9.2".
 
+## commitMessageLowerCase
+
+With `semanticCommits` pr- and commit-titles will by default (`"auto"`) be converted to all-lowercase.
+Set this to `"never"` to leave the titles untouched, allowing uppercase characters in semantic commit titles.
+
 ## commitMessagePrefix
 
 This is used to alter `commitMessage` and `prTitle` without needing to copy/paste the whole string.
@@ -3310,11 +3315,6 @@ If configured to `enabled`, then the `semanticCommitScope` and `semanticCommitTy
 
 Renovate autodetects if your repository is already using semantic commits or not and follows suit, so you only need to configure this if you wish to _override_ Renovate's autodetected setting.
 
-## commitMessageLowerCase
-
-With `semanticCommits` pr- and commit-titles will by default (`"auto"`) be converted to all-lowercase. 
-Set this to `"never"` to leave the titles untouched, allowing uppercase characters in semantic commit titles.
-
 ## separateMajorMinor
 
 Renovate's default behavior is to create a separate branch/PR if both minor and major version updates exist (note that your choice of `rangeStrategy` value can influence which updates exist in the first place however).