File: content/manuals/engine/security/trust/_index.md
Issue
The page contains two identical deprecation notices about Docker retiring DCT for Docker Official Images. The first appears in the "About Docker Content Trust (DCT)" section (lines ~30-37), and a second identical notice appears in the "Signing images with Docker Content Trust" section (lines ~110-117).
Both notices state:
Docker is retiring DCT for Docker Official Images (DOI). You should start planning to transition to a different image signing and verification solution (like Sigstore or Notation). Timelines for the complete deprecation of DCT are being finalized and will be published soon.
Why this matters
Readers encountering the same deprecation notice twice may be confused about whether:
- This represents two separate deprecations
- The feature is deprecated in two different contexts
- This is an editing error
The redundancy also makes the page feel less polished and may cause readers to doubt the currency of the documentation.
Suggested fix
Keep only one deprecation notice at the top of the "About Docker Content Trust (DCT)" section where it first appears. Remove the duplicate notice from the "Signing images with Docker Content Trust" section.
If the deprecation specifically affects the signing workflow differently than general DCT usage, clarify that distinction rather than repeating the identical notice.
Found by nightly documentation quality scanner
File:
content/manuals/engine/security/trust/_index.mdIssue
The page contains two identical deprecation notices about Docker retiring DCT for Docker Official Images. The first appears in the "About Docker Content Trust (DCT)" section (lines ~30-37), and a second identical notice appears in the "Signing images with Docker Content Trust" section (lines ~110-117).
Both notices state:
Why this matters
Readers encountering the same deprecation notice twice may be confused about whether:
The redundancy also makes the page feel less polished and may cause readers to doubt the currency of the documentation.
Suggested fix
Keep only one deprecation notice at the top of the "About Docker Content Trust (DCT)" section where it first appears. Remove the duplicate notice from the "Signing images with Docker Content Trust" section.
If the deprecation specifically affects the signing workflow differently than general DCT usage, clarify that distinction rather than repeating the identical notice.
Found by nightly documentation quality scanner