Add latest changes from gitlab-org/gitlab@16-5-stable-eev16.5.0-rc42

1 files changed, 4 insertions, 5 deletions

diff --git a/doc/development/build_test_package.md b/doc/development/build_test_package.md
index c4ae0ac5b71..bc8cebed3fc 100644
--- a/doc/development/build_test_package.md
+++ b/doc/development/build_test_package.md
@@ -8,15 +8,14 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 While developing a new feature or modifying an existing one, it is helpful if an
 installable package (or a Docker image) containing those changes is available
-for testing. For this very purpose, a manual job is provided in the GitLab CI/CD
+for testing. For this purpose, a manual job is provided in the GitLab CI/CD
 pipeline that can be used to trigger a pipeline in the Omnibus GitLab repository
 that will create:
 
 - A deb package for Ubuntu 16.04, available as a build artifact, and
-- A Docker image, which is pushed to the
-  [Omnibus GitLab container registry](https://gitlab.com/gitlab-org/omnibus-gitlab/container_registry)
-  (images titled `gitlab-ce` and `gitlab-ee` respectively and image tag is the
-  commit which triggered the pipeline).
+- A Docker image. The Docker image is pushed to the
+  [Omnibus GitLab container registry](https://gitlab.com/gitlab-org/omnibus-gitlab/container_registry). Images for the GitLab Enterprise Edition are named `gitlab-ee`. Images for the GitLab Community Edition are named `gitlab-ce`.
+- The image tag is the commit that triggered the pipeline.
 
 When you push a commit to either the GitLab CE or GitLab EE project, the
 pipeline for that commit will have a `trigger-omnibus` job in the `qa` stage you