File: content/manuals/docker-hub/repos/manage/trusted-content/official-images.md
Issue
The NOTE at the top of the page uses "soon" twice without any date context:
Docker will publish migration guides soon to help you in that effort. Timelines for the complete deprecation of DCT are being finalized and will be published soon.
Without a date on this notice, readers cannot tell:
- When this retirement was announced
- Whether "soon" means weeks, months, or if it already happened
- How urgent the migration actually is
- If the promised migration guides have already been published
Why this matters
Users reading this documentation cannot assess the urgency of migrating away from DCT. If this notice was added in 2022, "soon" has a very different meaning than if it was added last month. The lack of temporal context makes it impossible for readers to plan their migration timeline or know if they're already behind schedule.
This is particularly problematic for a deprecation notice, where timing is critical for users to plan their work.
Suggested fix
Add a date to the notice and either:
- Link to the published migration guides if they exist, or
- Provide a specific timeline if they don't exist yet
Example:
> [!NOTE]
>
> As of [DATE], Docker is retiring Docker Content Trust (DCT) for Docker Official Images (DOI).
> Migration guides are available at [LINK] / will be published by [DATE].
> DCT will be fully deprecated on [DATE].
If the migration guides have been published, remove "soon" and link directly to them.
Found by nightly documentation quality scanner
File:
content/manuals/docker-hub/repos/manage/trusted-content/official-images.mdIssue
The NOTE at the top of the page uses "soon" twice without any date context:
Without a date on this notice, readers cannot tell:
Why this matters
Users reading this documentation cannot assess the urgency of migrating away from DCT. If this notice was added in 2022, "soon" has a very different meaning than if it was added last month. The lack of temporal context makes it impossible for readers to plan their migration timeline or know if they're already behind schedule.
This is particularly problematic for a deprecation notice, where timing is critical for users to plan their work.
Suggested fix
Add a date to the notice and either:
Example:
If the migration guides have been published, remove "soon" and link directly to them.
Found by nightly documentation quality scanner