Update the container registry docs to promote the dependency proxy

doc/user/packages/container_registry/index.md

@@ -16,6 +16,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 > - The group-level Container Registry was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/23315) in GitLab 12.10.
 > - Searching by image repository name was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/31322) in GitLab 13.0.
 
+NOTE:
+If you pull container images from Docker Hub, you can also use the [GitLab Dependency Proxy](../dependency_proxy/index.md#use-the-dependency-proxy-for-docker-images) to avoid running into rate limits and speed up your pipelines.
+
 With the Docker Container Registry integrated into GitLab, every GitLab project can
 have its own space to store its Docker images.
 

doc/user/packages/dependency_proxy/index.md

@@ -209,6 +209,9 @@ the [Dependency Proxy API](../../../api/dependency_proxy.md).
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241639) in [GitLab Core](https://about.gitlab.com/pricing/) 13.7.
 
+<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
+Watch how to [use the Dependency Proxy to help avoid Docker Hub rate limits](https://youtu.be/Nc4nUo7Pq08).
+
 In November 2020, Docker introduced
 [rate limits on pull requests from Docker Hub](https://docs.docker.com/docker-hub/download-rate-limit/).
 If your GitLab [CI/CD configuration](../../../ci/README.md) uses