Update document to use ci_validates_dependencies

doc/ci/yaml/README.md

@@ -1153,22 +1153,16 @@ deploy:
   script: make deploy
 ```
 
-### Validations for `dependencies` keyword
-
+>**Note:**
 > Introduced in GitLab 10.3
+> This is the user documentation. For the administration guide see
+  [administration/job_artifacts](../../../administration/job_artifacts.md#validation_for_dependency).
 
-`dependencies` keyword doesn't check the depended `artifacts` strictly. Therefore
-they do not fail even though it falls into the following conditions.
+If a depended job doesn't have artifacts by the following reason, the depending job will fail.
 
 1. A depended `artifacts` has been [erased](https://docs.gitlab.com/ee/api/jobs.html#erase-a-job).
 1. A depended `artifacts` has been [expired](https://docs.gitlab.com/ee/ci/yaml/#artifacts-expire_in).
 
-To validate those conditions, you can flip the feature flag from a rails console:
-
-```
-Feature.enable('ci_validates_dependencies')
-```
-
 ### before_script and after_script
 
 It's possible to overwrite the globally defined `before_script` and `after_script`:

doc/user/project/pipelines/job_artifacts.md

@@ -163,6 +163,14 @@ information in the UI.
 
 ![Latest artifacts button](img/job_latest_artifacts_browser.png)
 
+## Validation for `dependency` keyword
+
+To disable [the validation for dependency], you can flip the feature flag from a rails console:
+
+```
+Feature.enable('ci_disable_validates_dependencies')
+```
 
 [expiry date]: ../../../ci/yaml/README.md#artifacts-expire_in
+[the validation for dependency]: ../../../ci/yaml/README.md#dependencies
 [ce-14399]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14399