File: content/manuals/enterprise/security/enforce-sign-in/_index.md
Issue
The "How sign-in enforcement works" section lists only three configuration methods:
When Docker Desktop detects a registry key, .plist file, or
registry.json file:
However, the page introduces four methods at the top:
- Registry key method (Windows only)
- Configuration profiles method (Mac only) ← missing from explanation
.plist method (Mac only)
registry.json method (All)
Configuration profiles are the recommended method for Mac (as stated in methods.md: "Configuration profiles provide the most secure enforcement method for Mac"), but they're not mentioned in the explanation of how enforcement works.
Why this matters
Readers using configuration profiles may be confused about whether the enforcement behavior described applies to their setup. The explanation should cover all four methods consistently.
Suggested fix
Update the opening sentence to include all four methods:
When Docker Desktop detects a registry key, configuration profile, `.plist` file, or
`registry.json` file:
Found by nightly documentation quality scanner
File:
content/manuals/enterprise/security/enforce-sign-in/_index.mdIssue
The "How sign-in enforcement works" section lists only three configuration methods:
However, the page introduces four methods at the top:
.plistmethod (Mac only)registry.jsonmethod (All)Configuration profiles are the recommended method for Mac (as stated in methods.md: "Configuration profiles provide the most secure enforcement method for Mac"), but they're not mentioned in the explanation of how enforcement works.
Why this matters
Readers using configuration profiles may be confused about whether the enforcement behavior described applies to their setup. The explanation should cover all four methods consistently.
Suggested fix
Update the opening sentence to include all four methods:
Found by nightly documentation quality scanner