(hub,scout,buildcloud,dhi):remove screenshots (#26114)

<!--Delete sections as needed -->

## Description

Removed unnecessary screenshots from the following:
- dhi
- hub
- scout
- build cloud

## Related issues or tickets


https://docker.slack.com/archives/C039ZM6GH4Z/p1789553587218539?thread_ts=1789552876.667069&cid=C039ZM6GH4Z

#26109

## Reviews

<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->

- [ ] Editorial review

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

content/manuals/build-cloud/usage.md

@@ -36,8 +36,6 @@ $ docker buildx use cloud-<ORG>-<BUILDER_NAME> --global
 2. Find the cloud builder under **Available builders**.
 3. Open the drop-down menu and select **Use**.
 
-   ![Selecting the cloud builder as default using the Docker Desktop GUI](/build/images/set-default-builder-gui.webp)
-
 {{< /tab >}}
 {{< /tabs >}}
 

content/manuals/docker-hub/repos/manage/builds/_index.md

@@ -22,8 +22,6 @@ aliases:
 Docker Hub can automatically build images from source code in an external
 repository and automatically push the built image to your Docker repositories.
 
-![An automated build dashboard](images/index-dashboard.png)
-
 When you set up automated builds, also called autobuilds, you create a list of
 branches and tags that you want to build into Docker images. When you push code
 to a source-code branch, for example in GitHub, for one of those listed image

content/manuals/docker-hub/repos/manage/builds/manage-builds.md

@@ -23,8 +23,6 @@ report link on the **General** tab and on the **Builds** tab. You can also selec
 **Cancel** on the **Build report** page, or from the **Timeline** tab's logs
 display for the build.
 
-![List of builds showing the cancel icon](images/build-cancelicon.png)
-
 ## Check your active builds
 
 A summary of a repository's builds appears both on the repository **General**
@@ -33,8 +31,6 @@ bar chart of the build queue times and durations. Both views display the
 pending, in progress, successful, and failed builds for any tag of the
 repository.
 
-![Active builds](images/index-active.png)
-
 From either location, you can select a build job to view its build report. The
 build report shows information about the build job. This includes the source
 repository and branch, or tag, the build logs, the build duration, creation time and location, and the user account the build occurred in.
@@ -43,8 +39,6 @@ repository and branch, or tag, the build logs, the build duration, creation time
 >
 > You can now view the progress of your builds every 30 seconds when you refresh the **Builds** page. With the in-progress build logs, you can debug your builds before they're finished.
 
-![Build report](./images/index-report.png)
-
 ## Disable an automated build
 
 Automated builds are enabled per branch or tag, and can be disabled and

content/manuals/docker-hub/repos/manage/builds/troubleshoot.md

@@ -23,8 +23,6 @@ aliases:
 If a build fails, a **Retry** icon appears next to the build report line on the
 **General** and **Builds** tabs. The **Build report** page and **Timeline logs** also display a **Retry** button.
 
-![Timeline view showing the retry build button](images/retry-build.png)
-
 > [!NOTE]
 >
 > If you are viewing the build details for a repository that belongs to an

content/manuals/docker-hub/repos/manage/hub-images/oci-artifacts.md

@@ -100,14 +100,10 @@ Steps:
 5. Go to the repository page on Docker Hub. The **Tags** section of the page
    shows the Helm chart tag.
 
-   ![List of repository tags](./images/oci-helm.png)
-
 6. Select the tag name to go to the page for that tag.
 
    The page lists a few useful commands for working with Helm charts.
 
-   ![Tag page of a Helm chart artifact](./images/oci-helm-tagview.png)
-
 ### Push a volume
 
 The following procedure shows how to push container volume as an OCI artifact to
@@ -146,8 +142,6 @@ Steps:
 4. Go to the repository page on Docker Hub. The **Tags** section on that page
    shows the volume tag.
 
-   ![Repository page showing a volume in the tag list](./images/oci-volume.png)
-
 ### Push a generic artifact file
 
 The following procedure shows how to push a generic OCI artifact to Docker Hub.
@@ -178,5 +172,3 @@ Steps:
 
 4. Go to the repository page on Docker Hub. The **Tags** section on that page
    shows the artifact tag.
-
-   ![Repository page showing an artifact in the tag list](./images/oci-artifact.png)

content/manuals/docker-hub/repos/manage/vulnerability-scanning.md

@@ -140,8 +140,6 @@ To view the vulnerability report:
    It may take a couple of minutes for the vulnerability report to appear in
    your repository.
 
-   ![Vulnerability scan report](images/vuln-scan-report.png)
-
 4. Select the **Tags** tab, then **Digest**, then **Vulnerabilities** to view the
    detailed scan report.
 
@@ -151,8 +149,6 @@ To view the vulnerability report:
    version in which it was introduced, and whether the vulnerability is fixed in
    a later version.
 
-   ![Vulnerability scan details](images/vuln-scan-details.png)
-
 For more information on this view, see
 [Image details view](/manuals/scout/explore/image-details-view.md).
 

content/manuals/scout/explore/dashboard.md

@@ -19,8 +19,6 @@ they need to focus on.
 
 ## Overview
 
-![A screenshot of the Docker Scout Dashboard overview](../images/dashboard-overview.webp?border=true)
-
 The **Overview** tab provides a summary for the repositories in the selected
 organization.
 
@@ -46,8 +44,6 @@ sections of the Docker Scout Dashboard:
 The **Images** view shows all images in Scout-enabled repositories for the selected environment.
 You can filter the list by selecting a different environment, or by repository name using the text filter.
 
-![Screenshot of the images view](../images/dashboard-images.webp)
-
 For each repository, the list displays the following details:
 
 - The repository name (image reference without the tag or digest)

content/manuals/scout/explore/exceptions.md

@@ -84,8 +84,6 @@ Vulnerability exceptions are highlighted in the CLI when you run `docker scout
 cves <image>`. If a CVE is suppressed by an exception, a `SUPPRESSED` label
 appears next to the CVE ID. Details about the exception are also displayed.
 
-![SUPPRESSED label in the CLI output](/scout/images/suppressed-cve-cli.png)
-
 > [!IMPORTANT]
 > In order to view exceptions in the CLI, you must configure the CLI to use
 > the same Docker organization that you used to create the exceptions.

content/manuals/scout/explore/image-details-view.md

@@ -14,8 +14,6 @@ access the image view from the Docker Scout Dashboard, the Docker Desktop
 show a breakdown of the image hierarchy (base images), image layers, packages,
 and vulnerabilities.
 
-![The image details view in Docker Desktop](../images/dd-image-view.png)
-
 Docker Desktop first analyzes images locally, where it generates a software bill of materials (SBOM).
 Docker Desktop, Docker Hub, and the Docker Scout Dashboard and CLI all use the [package URL (PURL) links](https://github.com/package-url/purl-spec)
 in this SBOM to query for matching Common Vulnerabilities and Exposures (CVEs) in [Docker Scout's advisory database](/manuals/scout/deep-dive/advisory-db-sources.md).
@@ -143,8 +141,6 @@ of `debian` to use. By providing more than one alternative to choose from, you
 can see for yourself how the options compare with each other, and decide which
 one to use.
 
-![Base image recommendations](../images/change-base-image.png)
-
 Select a tag recommendation to see further details of the recommendation.
 It shows the benefits and potential disadvantages of the tag, why it's a
 recommended, and how to update your Dockerfile to use this version.

content/manuals/scout/explore/metrics-exporter.md

@@ -158,17 +158,11 @@ The Prometheus server runs in a Docker container and is accessible on port 9090.
 After a few seconds, you should see the metrics endpoint as a target in the
 Prometheus UI at <http://localhost:9090/targets>.
 
-![Docker Scout metrics exporter Prometheus target](../images/scout-metrics-prom-target.png "Docker Scout metrics exporter Prometheus target")
-
 ### Viewing the metrics in Grafana
 
 To view the Grafana dashboards, go to <http://localhost:3000/dashboards>,
 and sign in using the credentials defined in the Docker Compose file (username: `admin`, password: `grafana`).
 
-![Vulnerability dashboard in Grafana](../images/scout-metrics-grafana-vulns.png "Vulnerability dashboard in Grafana")
-
-![Policy dashboard in Grafana](../images/scout-metrics-grafana-policy.png "Policy dashboard in Grafana")
-
 The dashboards are pre-configured to visualize the vulnerability and policy metrics scraped by Prometheus.
 
 ## Datadog

content/manuals/scout/integrations/ci/gha.md

@@ -150,11 +150,7 @@ showing only what's changed.
 The GitHub Action outputs the comparison results in a pull request comment by
 default.
 
-![A screenshot showing the results of Docker Scout output in a GitHub Action](../../images/gha-output.webp)
-
 Expand the **Policies** section to view the difference in policy compliance
 between the two images. Note that while the new image in this example isn't
 fully compliant, the output shows that the standing for the new image has
 improved compared to the baseline.
-
-![GHA policy evaluation output](../../images/gha-policy-eval.webp)

content/manuals/scout/release-notes/platform.md

@@ -305,8 +305,6 @@ Policy Evaluation is an early access feature that helps you ensure software
 integrity and track how your artifacts are doing over time. This release ships
 with four out-of-the-box policies, enabled by default for all organizations.
 
-![Policy overview in Dashboard](../images/release-notes/policy-ea.webp)
-
 - **Base images not up-to-date** evaluates whether the base images are out of
   date, and require updating. Up-to-date base images help you ensure that your
   environments are reliable and secure.