[docs-scanner] Inconsistent terminology for Gordon's free tier across pages
维护者通常 1 天内回复
评估
- 难度
- 1/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 92/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- markdown
调研方向
Issue 提到了 content/manuals/ai/gordon/usage-limits.md 和 content/manuals/ai/gordon/concepts/data-privacy.md。阅读两个标题和套餐引用，然后更新数据隐私标题，使其统一使用 Base 术语。完成标准是读者能在两个页面中识别出同一个免费套餐。
由索引模型根据 Issue 内容生成。
描述
Files:
content/manuals/ai/gordon/usage-limits.mdcontent/manuals/ai/gordon/concepts/data-privacy.md
Issue
The Gordon documentation uses inconsistent terminology to refer to the free tier across different pages.
In usage-limits.md, the free tier is consistently called "Base":
Gordon is included with every Docker account at the Base tier. Paid Gordon plans unlock higher usage limits.
And in the table:
| Base | Included with any Docker account |
However, in data-privacy.md, the same tier is called "Personal (free) subscription":
Personal (free) subscription
Anonymized conversation threads are stored for 5 days to help guarantee quality of service and fight abuse.
Why this matters
Readers trying to understand which tier they're on and what data retention policies apply to them will encounter two different names for the same tier. This creates confusion about whether "Base" and "Personal (free)" are the same thing or different tiers with different policies.
A reader on the free tier might:
- Read usage-limits.md and learn they're on "Base" tier
- Read data-privacy.md looking for "Base" tier data policies
- Find only "Personal (free) subscription" and wonder if it applies to them
Suggested fix
Use consistent terminology across both pages. Since "Base" is used throughout usage-limits.md and appears to be the primary term, update data-privacy.md to use "Base tier" or "Base (free) tier" instead of "Personal (free) subscription".
Change:
### Personal (free) subscription
To:
### Base tier (free)
Or add a clarification:
### Base tier (Personal free subscription)
Found by nightly documentation quality scanner
- 主要语言
- Markdown
- 星标
- 4.7k
- 派生
- 8.5k
- 平均合并
- 2 天 1 小时
- 30 天内合并 PR
- 139
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
docker/docs 的其他 Issue
-
[docs-scanner] SSO multi-IdP configuration placed after enforcement section可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
status/triage
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复
-
status/triage
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复
-
[docs-scanner] Example uses deprecated Flocker volume driver可能已有人在做 @aevesdocker 于 6 天前认领。 未关闭
难度 1/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 半天 新手友好度 82/100
维护者通常 1 天内回复
相似的 Issue
-
automated issue report
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 70/100
microsoft/playwright#43640 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 67/100
rust-bitcoin/rust-bitcoin#7089 · 1 条评论 · 1 个 reaction ·
维护者通常 2 天内回复
-
documentation from-review-extraction severity:nit
难度 1/5 1 小时以内 新手友好度 86/100
LearningCircuit/local-deep-research#7949 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
DouyinFE/semi-design#3632 ·
维护者通常 3 天内回复