File: content/manuals/dhi/explore/build-process.md
Issue
The tier badge and prose text are inconsistent about whether DHI Select AND Enterprise are both required, or if EITHER tier provides customization features.
The heading uses:
{tier="DHI Select and Enterprise"}
But the prose throughout the section uses:
"With DHI Select or DHI Enterprise subscriptions..."
"When you customize a DHI image with DHI Select or DHI Enterprise..."
Why this matters
Readers trying to understand subscription requirements will be confused about whether they need both DHI Select AND DHI Enterprise (as the tier badge suggests with "and"), or whether either subscription tier works (as the prose suggests with "or").
This affects purchasing decisions and feature availability understanding.
Suggested fix
Make the tier badge and prose consistent. If either tier provides the feature, change the tier badge to:
{tier="DHI Select or Enterprise"}
Or if both are required, change all prose instances to use "and" instead of "or".
Based on the context and other similar tier badges in the DHI docs, it appears "or" is correct (either tier works), so the tier badge should be updated.
Found by nightly documentation quality scanner
File:
content/manuals/dhi/explore/build-process.mdIssue
The tier badge and prose text are inconsistent about whether DHI Select AND Enterprise are both required, or if EITHER tier provides customization features.
The heading uses:
But the prose throughout the section uses:
Why this matters
Readers trying to understand subscription requirements will be confused about whether they need both DHI Select AND DHI Enterprise (as the tier badge suggests with "and"), or whether either subscription tier works (as the prose suggests with "or").
This affects purchasing decisions and feature availability understanding.
Suggested fix
Make the tier badge and prose consistent. If either tier provides the feature, change the tier badge to:
Or if both are required, change all prose instances to use "and" instead of "or".
Based on the context and other similar tier badges in the DHI docs, it appears "or" is correct (either tier works), so the tier badge should be updated.
Found by nightly documentation quality scanner