Rename official repos to official images

Author: Jeffrey Morgan

_data/toc.yaml

@@ -173,6 +173,8 @@ guides:
       path: /get-started/part4/
     - title: "Part 5: Stacks"
       path: /get-started/part5/
+    - title: "Part 6: Deploy your app"
+      path: /get-started/part6/
   - path: /engine/docker-overview/
     title: Docker overview
 - sectiontitle: Develop with Docker
@@ -3631,8 +3633,8 @@ manuals:
     title: Docker ID
   - path: /docker-hub/repos/
     title: Public Repositories
-  - path: /docker-hub/official_repos/
-    title: Official Repositories
+  - path: /docker-hub/official_images/
+    title: Official Images
   - path: /docker-hub/orgs/
     title: Teams & Organizations
   - path: /docker-hub/webhooks/

develop/develop-images/baseimages.md

@@ -119,4 +119,4 @@ There are lots more resources available to help you write your `Dockerfile`.
 * There's a [complete guide to all the instructions](/engine/reference/builder.md) available for use in a `Dockerfile` in the reference section.
 * To help you write a clear, readable, maintainable `Dockerfile`, we've also
 written a [`Dockerfile` best practices guide](dockerfile_best-practices.md).
-* If your goal is to create a new Official Repository, be sure to read up on Docker's [Official Repositories](/docker-hub/official_repos/).
+* If your goal is to create a new Official Image, be sure to read up on Docker's [Official Images](/docker-hub/official_images/).

develop/develop-images/dockerfile_best-practices.md

@@ -1,6 +1,6 @@
 ---
 description: Hints, tips and guidelines for writing clean, reliable Dockerfiles
-keywords: parent image, images, dockerfile, best practices, hub, official repo
+keywords: parent image, images, dockerfile, best practices, hub, official image
 redirect_from:
 - /articles/dockerfile_best-practices/
 - /engine/articles/dockerfile_best-practices/
@@ -291,7 +291,7 @@ maintainable `Dockerfile`.
 
 [Dockerfile reference for the FROM instruction](/engine/reference/builder.md#from)
 
-Whenever possible, use current official repositories as the basis for your
+Whenever possible, use current official images as the basis for your
 images. We recommend the [Alpine image](https://hub.docker.com/_/alpine/) as it
 is tightly controlled and small in size (currently under 5 MB), while still
 being a full Linux distribution.
@@ -766,9 +766,9 @@ fails catastrophically if the new build's context is missing the resource being
 added. Adding a separate tag, as recommended above, helps mitigate this by
 allowing the `Dockerfile` author to make a choice.
 
-## Examples for Official Repositories
+## Examples for Official Images
 
-These Official Repositories have exemplary `Dockerfile`s:
+These Official Images have exemplary `Dockerfile`s:
 
 * [Go](https://hub.docker.com/_/golang/)
 * [Perl](https://hub.docker.com/_/perl/)
@@ -780,4 +780,4 @@ These Official Repositories have exemplary `Dockerfile`s:
 * [Dockerfile Reference](/engine/reference/builder.md)
 * [More about Base Images](baseimages.md)
 * [More about Automated Builds](/docker-hub/builds/)
-* [Guidelines for Creating Official Repositories](/docker-hub/official_repos/)
+* [Guidelines for Creating Official Images](/docker-hub/official_images/)

docker-hub/builds/builds.md

@@ -207,7 +207,7 @@ To add a link:
 
 2. In the Repository Links section, enter an image repository name.
 
-    A remote repository name should be either an official repository name such as `ubuntu` or a public repository name `namespace/repoName`.
+    A remote repository name should be either an official image name such as `ubuntu` or a public repository name `namespace/repoName`.
 
 3. Press **Add**.
 

docker-hub/index.md

@@ -16,7 +16,7 @@ Docker Hub provides the following major features:
   repositories allow you to share container images with your team. Public
   repositories allow you to share them with anyone.
 * [Teams & Organizations](/docker-hub/orgs.md): Manage access to private repositories.
-* [Official Repositories](/docker-hub/official_repos.md): Pull & use high-quality container images provided by Docker.
+* [Official Images](/docker-hub/official_images.md): Pull & use high-quality container images provided by Docker.
 * [Publisher Images](/docker-hub/publish/customer_faq.md): Pull & use high-quality container
   images provided by external vendors. Certified images also include support and guarantee
   compatibility with Docker Enterprise.
@@ -32,17 +32,17 @@ Start by creating an [account](/docker-hub/accounts.md) at [https://hub.docker.c
 > **Note**: You can search for and pull Docker images from Hub without logging
 > in, however to push images or share them with your team, you must log in.
 
-## Find & Pull an Official Repositories
+## Find & Pull an Official Image
 
 Docker Hub contains a number of [Official
 Repositories](http://hub.docker.com/explore/). These are curated repositories from vendors and contributors to Docker. They contain Docker images from vendors like Canonical, Oracle, and Elastic that you can use as the basis to build your applications and services.
 
-With Official Repositories you know you're using an optimized and
+With Official Images you know you're using an optimized and
 up-to-date image that was built by experts to power your applications.
 
-> **Note**: If you would like to contribute an Official Repository for your
+> **Note**: If you would like to contribute an Official Image for your
 > organization or product, see the documentation on
-> [Official Repositories on Docker Hub](/docker-hub/official_repos.md) for more
+> [Official Images on Docker Hub](/docker-hub/official_images.md) for more
 > information.
 
 ## Create your first repository and push an image to it

docker-hub/official_repos.md

@@ -1,10 +1,10 @@
 ---
-description: Guidelines for Official Repositories on Docker Hub
+description: Guidelines for Official Images on Docker Hub
 keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, official,image, documentation
-title: Official repositories on Docker Hub
+title: Official Images on Docker Hub
 ---
 
-The Docker [Official Repositories](https://hub.docker.com/official/) are a
+The Docker [Official Images](https://hub.docker.com/search?q=&type=image&image_filter=official) are a
 curated set of Docker repositories hosted on Docker Hub. They are
 designed to:
 
@@ -22,29 +22,29 @@ designed to:
   authors.
 
 * Ensure that security updates are applied in a timely manner. This is
-  particularly important as many Official Repositories are some of the most
+  particularly important as many Official Images are some of the most
   popular on Docker Hub.
 
 Docker, Inc. sponsors a dedicated team that is responsible for reviewing and
-publishing all content in the official repositories. This team works in
+publishing all content in the Official Images. This team works in
 collaboration with upstream software maintainers, security experts, and the
 broader Docker community.
 
 While it is preferable to have upstream software authors maintaining their
-corresponding Official Repositories, this is not a strict requirement. Creating
-and maintaining images for Official Repositories is a public process. It takes
+corresponding Official Images, this is not a strict requirement. Creating
+and maintaining images for Official Images is a public process. It takes
 place openly on GitHub where participation is encouraged. Anyone can provide
 feedback, contribute code, suggest process changes, or even propose a new
-Official Repository.
+Official Image.
 
-## Should I use Official Repositories?
+## Should I use Official Images?
 
-New Docker users are encouraged to use the Official Repositories in their
+New Docker users are encouraged to use the Official Images in their
 projects. These repositories have clear documentation, promote best practices,
 and are designed for the most common use cases. Advanced users are encouraged to
-review the Official Repositories as part of their `Dockerfile` learning process.
+review the Official Images as part of their `Dockerfile` learning process.
 
-A common rationale for diverging from Official Repositories is to optimize for
+A common rationale for diverging from Official Images is to optimize for
 image size. For instance, many of the programming language stack images contain
 a complete build toolchain to support installation of modules that depend on
 optimized code. An advanced user could build a custom image with just the
@@ -54,13 +54,13 @@ A number of language stacks such as
 [python](https://hub.docker.com/_/python/) and
 [ruby](https://hub.docker.com/_/ruby/) have `-slim` tag variants
 designed to fill the need for optimization. Even when these "slim" variants are
-insufficient, it is still recommended to inherit from an Official Repository
+insufficient, it is still recommended to inherit from an Official Image
 base OS image to leverage the ongoing maintenance work, rather than duplicating
 these efforts.
 
-## How do I know the Official Repositories are secure?
+## How do I know the Official Images are secure?
 
-Each of the images in the Official Repositories is scanned for vulnerabilities. The results of
+Each of the images in the Official Images is scanned for vulnerabilities. The results of
 these security scans provide valuable information about which images contain
 security vulnerabilities, and allow you to choose images that align with your
 security standards.
@@ -69,7 +69,7 @@ To view the Docker Security Scanning results:
 
 1. Make sure you're logged in to Docker Hub.
     You can view Official Images even while logged out, however the scan results are only available once you log in.
-2. Navigate to the official repository whose security scan you want to view.
+2. Navigate to the repository of the Official Image whose security scan you want to view.
 3. Click the `Tags` tab to see a list of tags and their security scan summaries.
     ![Viewing CVEs from Docker images](images/scan-drilldown.gif)
 
@@ -80,37 +80,37 @@ when you click an individual vulnerable component.
 
 ## How can I get involved?
 
-All Official Repositories contain a **User Feedback** section in their
+All Official Images contain a **User Feedback** section in their
 documentation which covers the details for that specific repository. In most
 cases, the GitHub repository which contains the Dockerfiles for an Official
 Repository also has an active issue tracker. General feedback and support
 questions should be directed to `#docker-library` on Freenode IRC.
 
-## How do I create a new Official Repository?
+## How do I create a new Official Image?
 
-From a high level, an Official Repository starts out as a proposal in the form
+From a high level, an Official Image starts out as a proposal in the form
 of a set of GitHub pull requests. Detailed and objective proposal
 requirements are documented in the following GitHub repositories:
 
 * [docker-library/official-images](https://github.com/docker-library/official-images)
 
 * [docker-library/docs](https://github.com/docker-library/docs)
 
-The Official Repositories team, with help from community contributors, formally
+The Official Images team, with help from community contributors, formally
 review each proposal and provide feedback to the author. This initial review
 process may require a bit of back and forth before the proposal is accepted.
 
 There are also subjective considerations during the review process. These
 subjective concerns boil down to the basic question: "is this image generally
 useful?" For example, the [python](https://hub.docker.com/_/python/)
-Official Repository is "generally useful" to the large Python developer
+Official Image is "generally useful" to the large Python developer
 community, whereas an obscure text adventure game written in Python last week is
 not.
 
 Once a new proposal is accepted, the author is responsible for keeping
 their images up-to-date and responding to user feedback. The Official
 Repositories team becomes responsible for publishing the images and
-documentation on Docker Hub. Updates to the Official Repository follow the same
-pull request process, though with less review. The Official Repositories team
+documentation on Docker Hub. Updates to the Official Image follow the same
+pull request process, though with less review. The Official Images team
 ultimately acts as a gatekeeper for all changes, which helps mitigate the risk
 of quality and security issues from being introduced.

docker-hub/publish/certify-images.md

@@ -22,7 +22,7 @@ You must use the tool, `inspectDockerImage`, to certify your content for publica
 
 The `inspectDockerImage` tool does the following:
 
-- Verifies that the Docker image was built from an image in the [Docker Official Repository](https://github.com/docker-library/repo-info/tree/master/repos)
+- Verifies that the Docker image was built from an image in the [Docker Official Image](https://github.com/docker-library/repo-info/tree/master/repos)
 
 - Inspects the Docker image for a Health Check. Although a Health Check is not required, it is recommended.
 

docker-hub/publish/publish.md

@@ -62,7 +62,7 @@ and guidelines listed below to build and deliver great content:
 
 * [Best practices for writing Dockerfiles](/engine/userguide/eng-image/dockerfile_best-practices/)
 
-* [Official repositories on Docker Hub](/docker-hub/official_repos/)
+* [Official Images on Docker Hub](/docker-hub/official_images/)
 
 * [Docker Bench for Security](https://github.com/docker/docker-bench-security){: target="_blank"
 class="_"}

docker-hub/repos.md

@@ -34,7 +34,7 @@ There you can see two example results: `centos` and `ansible/centos7-ansible`.
 The second result shows that it comes from the public repository of a user,
 named `ansible/`, while the first result, `centos`, doesn't explicitly list a
 repository which means that it comes from the top-level namespace for [Official
-Repositories](official_repos.md). The `/` character separates a user's
+Images](/docker-hub/official_images.md). The `/` character separates a user's
 repository from the image name.
 
 Once you've found the image you want, you can download it with `docker pull <imagename>`: