Changed requirements.yaml references to dependencies section references

Signed-off-by: Sebastien Plisson <sebastien.plisson@gmail.com>

docs/chart_best_practices/README.md

@@ -12,7 +12,7 @@ may find that their internal interests override our suggestions here.
 - [General Conventions](conventions.md): Learn about general chart conventions.
 - [Values Files](values.md): See the best practices for structuring `values.yaml`.
 - [Templates](templates.md): Learn some of the best techniques for writing templates.
-- [Requirements](requirements.md): Follow best practices for `requirements.yaml` files.
+- [Dependencies](requirements.md): Follow best practices for `dependencies` declared in `Chart.yaml`.
 - [Labels and Annotations](labels.md): Helm has a _heritage_ of labeling and annotating.
 - Kubernetes Resources:
 	- [Pods and Pod Specs](pods.md): See the best practices for working with pod specifications.

docs/chart_best_practices/requirements.md

@@ -1,6 +1,6 @@
-# Requirements Files
+# Dependencies 
 
-This section of the guide covers best practices for `requirements.yaml` files.
+This section of the guide covers best practices for `dependencies` declared in `Chart.yaml`.
 
 ## Versions
 
@@ -20,7 +20,7 @@ Where possible, use `https://` repository URLs, followed by `http://` URLs.
 
 If the repository has been added to the repository index file, the repository name can be used as an alias of URL. Use `alias:` or `@` followed by repository names.
 
-File URLs (`file://...`) are considered a "special case" for charts that are assembled by a fixed deployment pipeline. Charts that use `file://` in a `requirements.yaml` file are not allowed in the official Helm repository.
+File URLs (`file://...`) are considered a "special case" for charts that are assembled by a fixed deployment pipeline. Charts that use `file://` are not allowed in the official Helm repository.
 
 ## Conditions and Tags