validation.md: Fix position of skip validation section

At the moment it appears in the middle of validation section.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I2ced5de381b7dfbf96d57b915c3be530896eda68

resources/Documentation/validation.md

diff --git a/resources/Documentation/validation.md b/resources/Documentation/validation.md
index 1c660a5..61cf60d 100644
--- a/resources/Documentation/validation.md
+++ b/resources/Documentation/validation.md
@@ -55,22 +55,6 @@
   blocking all uploads, to reduce the risk of breaking the plugin configuration
   `code-owner.config` files are validated too)
 
-## <a id="skipCodeOwnerConfigValidationOnDemand">Skip code owner config validation on demand
-
-By setting the `--code-owners~skip-validation` push option it is possible to
-skip the code owner config validation on push.
-
-Using this push option requires the calling user to have to
-`Can Skip Code Owner Config Validation` global capability. Host administrators
-have this capability implicitly assigned via the `Administrate Server` global
-capability.
-
-**NOTE:** Using this option only makes sense if the [code owner config validation
-on submit](config.html#pluginCodeOwnersEnableValidationOnSubmit) is disabled, as
-otherwise it's not possible to submit the created change (using the push option
-only skips the validation for the push, but not for the submission of the
-change).
-
 ## <a id="howCodeOwnerConfigsCanGetIssuesAfterSubmit">
 In addition it is possible that [code owner config
 files](user-guide.hmtl#codeOwnerConfigFiles) get issues after they have been
@@ -109,6 +93,22 @@
 validation that was done on upload. This means, all visibility checks will be
 done from the perspective of the uploader.
 
+## <a id="skipCodeOwnerConfigValidationOnDemand">Skip code owner config validation on demand
+
+By setting the `--code-owners~skip-validation` push option it is possible to
+skip the code owner config validation on push.
+
+Using this push option requires the calling user to have to
+`Can Skip Code Owner Config Validation` global capability. Host administrators
+have this capability implicitly assigned via the `Administrate Server` global
+capability.
+
+**NOTE:** Using this option only makes sense if the [code owner config validation
+on submit](config.html#pluginCodeOwnersEnableValidationOnSubmit) is disabled, as
+otherwise it's not possible to submit the created change (using the push option
+only skips the validation for the push, but not for the submission of the
+change).
+
 ### <a id="codeOwnerConfigFileChecks">Validation checks for code owner config files
 
 For [code owner config files](user-guide.html#codeOwnerConfigFiles) the