[khuyentran1401]

Why

Pages used Nebari's core terms in different ways than the glossary defines them. Readers now see each term used one way across the docs.

Reference Issues or PRs

Fixes #758. Part of #747. See also #777.

What does this implement/fix?

• All pages, including the Introduction, use the glossary's terms and capitalization.
• Terms a page doesn't explain link to the glossary, and the Introduction defines each term once.

Testing

• Did you test the pull request locally?

• Did you add new tests?

• Checked every glossary anchor the new links use.

[github-actions]

Docs preview for docs/align-docs-with-glossary:

• Nebari (via the nebari-docs Worker): https://docs-align-docs-with-glossary-nebari-docs.openteams-account.workers.dev
• Nebari Classic (via the nebari-docs-classic Worker): https://docs-align-docs-with-glossary-nebari-docs-classic.openteams-account.workers.dev

[jbouder]

The changes match the glossary and all new anchors resolve. A few pages still use the old terms, so #758 isn't fully closed yet. Two notes are inline. These files aren't in the diff:

• explanations/software-packs.mdx:54 says the pack appears on the landing page "as an available Capability." Per the glossary and this PR's nkp-architecture change, that should be "Service."
• how-tos/providers/hetzner.md:125 still says "foundational services."
• software-packs/build-your-own.md:10 and software-packs/deploy-a-pack.md:3 use lowercase "software pack."

The alternative is to narrow the "all pages" claim in the description.

[dcmcand]

Verdict: Request changes. The renames of "foundational software" and "Software Pack" are clean. But the Introduction replaces "Capability" with "tool", which isn't in the glossary, and uses it for packs, Services and Capabilities alike. So #758 isn't fixed yet. jbouder's notes already cover nkp-architecture.mdx:31, install.mdx:9, and the leftovers outside the diff.

---

Key: 🛑 Blocker (must fix before merge) · 💡 Suggestion (improvement, not blocking) · ❓ Question (needs author input) · ❤️ Kudos

[dcmcand]

🛑 Blocker: "These tools" points back to the Capabilities on :9, so this sentence says Capabilities are Software Packs.

Suggested change

	Developers publish these tools as [Software Packs](/docs/references/glossary/#software-pack). NKP wires in login, routing, TLS, and observability, so users just open the landing page and click in.
	Developers package the Services that provide them as [Software Packs](/docs/references/glossary/#software-pack). NKP wires in login, routing, TLS, and observability, so users just open the landing page and click in.

[dcmcand]

💡 Suggestion: Azure can already be deployed in NIC, so "two production providers" is wrong. "Providers" is also the unqualified form that the glossary splits into three kinds.
Say "Cluster Providers" here and in the description at :3. Then file a follow-up to replace the stub in azure.mdx and mark Azure Supported at :13.
NIC registers Azure in pkg/nic/registry.go. azure.Deploy runs tofu.Setup and Apply against the aks-cluster module, and CI has an Azure deployment-test job. GCP is still a stub.

[khuyentran1401]

Done. I also filed #777 for the Azure page and the Supported status.

[dcmcand]

Verdict: Approve. Every term the Introduction and the other pages use now matches the glossary. The suggestions inline are all small.

💡 Suggestion: references/glossary.md:10 still says "Different tools can provide the same Capability", so the glossary itself still uses "tool". The glossary isn't in this PR, so this could be a follow-up: change "tools" to "Services", since glossary.md:68 says Services provide Capabilities.

Reviewer	Item	Disposition
dcmcand	🛑 Introduction uses "tool" for packs, Services and Capabilities (:11, :26-28, :34)	Fixed in ec4535e8, a01d5dbb, 05f35405. The glossary's own "tools" is carried as a suggestion above.
dcmcand	🛑 nkp-architecture.mdx:11 says Capabilities are Software Packs	Fixed in 05f35405
dcmcand	🛑 Introduction :40 defines a pack by its GitHub hosting	Fixed in 05f35405, including software-packs/index.mdx:8
dcmcand	💡 Introduction :60 "NKP sets up"	Fixed
dcmcand	💡 Introduction :72 "catalog of Capabilities"	Fixed
dcmcand	💡 providers/index.md:6 "two production providers"	Fixed. Azure is deferred to #777.
dcmcand	💡 nkp-architecture.mdx:35 Operator "deploys" packs	Fixed
jbouder	nkp-architecture.mdx:31 "an installable Capability"	Fixed
jbouder	install.mdx:9 "platform essentials"	Fixed
jbouder	software-packs.mdx:54, hetzner.md:125, lowercase "software pack"	Fixed

---

Key: 🛑 Blocker (must fix before merge) · 💡 Suggestion (improvement, not blocking) · ❓ Question (needs author input) · ❤️ Kudos

[dcmcand]

💡 Suggestion: "ready-made packages" is a fourth name for a Software Pack, and the glossary doesn't define it.

Suggested change

	**Nebari is an open-source ecosystem for AI platforms.** Teams add AI [Capabilities](/docs/references/glossary/#capability), such as chat assistants, document analysis, image generation, and code review, by installing ready-made packages on a platform they control.
	**Nebari is an open-source ecosystem for AI platforms.** Teams add AI [Capabilities](/docs/references/glossary/#capability), such as chat assistants, document analysis, image generation, and code review, by installing [Software Packs](/docs/references/glossary/#software-pack) on a platform they control.

[dcmcand]

💡 Suggestion: This step says the pack is a Service, but a pack adds one or more Services (glossary.md:72).

Suggested change

	4. **The pack appears on the [landing page](https://github.com/nebari-dev/nebari-landing)** as an available Service.
	4. **The pack's Services appear on the [landing page](https://github.com/nebari-dev/nebari-landing).**

[dcmcand]

💡 Suggestion: "specific tools like JupyterLab" uses "tool" for a Service, which the Introduction no longer does.

Suggested change

	You can set up Software Packs (like the data science pack for specific tools like JupyterLab) on top of this layer.
	You can set up Software Packs (like the data science pack, which adds JupyterLab) on top of this layer.