Skip to content

docs(terminology): retire Edge Node, module, and add-on from current pages - #2618

Merged
bruno-andrade-azion merged 3 commits into
mainfrom
docs/mm-16249-retire-legacy-terms
Nov 11, 2026
Merged

bruno-andrade-azion merged 3 commits into
mainfrom
docs/mm-16249-retire-legacy-terms

Conversation

@bruno-andrade-azion

@bruno-andrade-azion bruno-andrade-azion commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

What & why

Related issue: MM-16249 (T37 of the October 2026 docs review, epic MM-16212)
Pages affected: 34 en pages and their 34 pt-br twins:

  • agent-setup/* (10 pages)
  • architectures/orch/infra-automation, architectures/orch/application-deliver-operation
  • main-menu/reference/services/integration-services/managed-configurations
  • main-menu/reference/ai-inference/lora-fine-tune, main-menu/reference/ai-inference/glossary
  • main-menu/reference/secure/api-v4-migration
  • guides/edge-application/ea-cache-post-options, ea-create-rules, ea-enforce-hls, ea-use-advanced-cache-key
  • guides/marketplace/integrations/ ab-testing-marketplace, hello-world, how-to-massive-redirection, marketplace-content-targeting, request-variation, send-messages-to-a-queue, signed-cookies, videoteca-player
  • main-menu/additional-resources/templates-and-integrations/understand-azion-integrations
  • main-menu/reference/marketplace/how-it-works, marketplace-reference, permissions-marketplace
  • main-menu/reference/secure/edge-firewall/web-application-firewall/custom-allowed-rule
  • secure/bot-manager/quickstart

This PR applies the style guide's terminology rules (style-guide/writing/terminology) to current pages. Those rules retire module and add-on as classifications of an Azion offering, and they remove the legacy Orchestrator names from prose. It changes wording, with no permalink or sample change. One definition changes with it: the Components list of the two Orchestrator architecture pages called nodes "distributed computing resources that process data closer to the source", and now defines a node as a device that runs the Orchestrator Agent, such as a server, a router, or a network switch, as the Orchestrator edge-node reference page does. The headings it renames, such as "Turn on the Functions module", have no inbound anchor links in the docs.

This is phase 1 of the ticket. It covers only the pages that no open pull request touched when it opened. Many of the pages with these terms are being rewritten, split, or retired by open PRs: #2574, #2584, and #2588 (Orchestrator), #2587 and #2586 (retired journeys), #2596 (Console paths), #2565, #2570, #2579, and #2580 (migration guides and Applications), and #2585 (compliance). #2612, which rewrote the other Marketplace integration guides, has since merged, so those guides move to phase 2. Phase 2 goes in a second PR once the rest merge.

Orchestrator names

  • An Orchestrator node is the customer's device that runs the Orchestrator Agent, so prose calls it a node and its services services, matching docs(orchestrator): consolidate duplicate guides and write How it works #2588. The style guide's "never node" rule covers Azion's own infrastructure, not this.
  • Edge Nodes and Edge Services stay only as bold Console labels. Both are the current menu labels in the Console bundle (label: Edge Nodes, to: /edge-node; label: Edge Services, to: /edge-services).
  • The architecture diagram infrastructure-arch.png still shows those labels in the image. They match the Console menu, so the image stays as it is.
  • The [email protected] support address on the Technical Support page is a real mailbox and stays.
  • The agent setup example prompt asks for the 5xx rate "by data center" instead of "by edge node". The style guide names the site a data center, and sourceLocPop is the GraphQL field behind it.

module

  • Pages name the Platform Resource instead of calling it a module, for example "turn on Application Accelerator" and "an application with Functions turned on". Modules and Default Modules stay where they are Console click paths.
  • The usage-cost line in the Marketplace and Bot Manager prerequisites now reads "Turning on a Platform Resource can generate usage costs."
  • Portuguese pages write the class as recurso da plataforma, the form of the pt-br terminology page: "Ligar um recurso da plataforma pode gerar custos de uso."
  • These stay as they are:
    • JavaScript, ES, Python, Terraform, and Azion Lib modules
    • API fields such as modules.application_accelerator and the attributes.modules object in azion.config.js
    • Verbatim API and CLI error messages, such as you must enable the Load Balancer module
    • Kafka-REST, which is third-party software

add-on

  • LoRA Fine-Tune is described as a Platform Resource of its own that extends AI Inference.
  • Managed Configurations is "available with Enterprise and Mission-Critical Support".
  • The API v4 migration page says Origin Shield on API v3 was "sold separately, with a Subscription".

Not in this PR

  • The sentences this PR edits keep their lowercase instances, such as "an application with Functions turned on" and "the firewall". Naming the instance by its Platform Resource (an Application, a Firewall) is a separate sweep of these pages. Changing only the edited sentences would leave each page with both spellings.
  • pt-br como-funciona keeps "um de dois Platform Resources", in a sentence this PR does not edit.

How it was checked

  • docs_gate.py --check on the 68 files, compared with the same files from origin/main: no new findings. The en infra-automation description is now within the length limit, and pt-br Managed Configurations has one finding fewer.
  • linkcheck.py on the 68 files: namespaces paired, no cross-language links. It reports two broken links, /en/docs-llms.txt and /pt-br/docs-llms.txt, at line 98 of agent-setup/claude-desktop. That line predates this PR and it does not touch it.
  • The branch merges the current main with no conflicts. That includes fix(applications): apply live test results and define each resource by its role #2626, which also edits ea-cache-post-options, and fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides #2612. fix(terminology): replace desempenho and aplicativo in pt-br pages #2621 edits three of the same pt-br files and also merges with this branch without conflicts.
  • A grep over the 68 files finds no "Edge Node", "Edge Services", "add-on", or "module" used as a classification, and no "Platform Resource" in the Portuguese text this PR adds. What remains is Console labels (Modules, Default Modules, Edge Nodes, Edge Services), API fields such as modules.cache, and Kafka-REST.
  • pnpm ci:ratchet slugcheck: 6, equal to the baseline.
  • pnpm ci:ratchet linkcheck, run after pnpm build:local: 159 broken links in the build, under the baseline of 221.
  • pnpm build:local on Node 26: the build and the frontmatter check pass.

Type of change

  • 🆕 New content (feat)
  • 🩹 Fix (fix) — typo, broken link, wrong information
  • ♻️ Content update (docs) — rewrite, expansion, upkeep
  • 🌐 Translation sync (i18n)
  • 🏗️ Platform / structure (refactor / chore) — reviewed by UXE, no content mixed in

Author checklist

  • PR title follows type(scope): summary (see GOVERNANCE.md §4)
  • Frontmatter complete: title, description, meta_tags, namespace, permalink, last_reviewed — none of the 68 pages had last_reviewed before this PR, and it changes wording only; the other fields are present
  • No legacy "edge-" product names in the copy — Edge Nodes and Edge Services remain only as Console menu labels
  • How-to/tutorial content includes at least one runnable, copy-paste-tested code block — no code block is added or changed
  • Screenshots (if any) have alt text and follow image standards — no screenshot is added or changed
  • Internal links are relative and resolve locally — no link is added; the two broken links linkcheck.py reports predate this PR
  • If any permalink changed or page moved: redirect added in this PR — no permalink changed and no page moved
  • i18n: pt-br updated in this PR or follow-up i18n issue created: pt-br updated in this PR
  • I ran pnpm build:local (build + frontmatter check) without errors

…pages

Apply the terminology rules of the style guide to the pages no open pull
request touches, in en and pt-br:

- Orchestrator architectures and Managed Configurations call the customer
  devices nodes and the services services. Edge Nodes and Edge Services
  stay only as Console menu labels.
- The agent setup prompts ask for the 5xx rate by data center.
- Application Accelerator guides, Marketplace integration guides and
  references, Bot Manager, and the WAF exception page name the Platform
  Resource instead of calling it a module. Modules stays in click paths.
- LoRA Fine-Tune, Managed Configurations, and the API v4 migration page
  drop add-on as a classification.

Co-Authored-By: Claude <[email protected]>
* origin/main:
  fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612)
  docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611)
  docs(guides): make the auth layer and vector search tutorials runnable (#2566)
  chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637)
  fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565)
  docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567)
  docs(terraform): rewrite the samples for provider v2.10.0 (#2557)
  chore(deploy): promote docs-v2.4.4 to production (#2631)
  chore(main): release docs 2.4.4 (#2627)
  chore(deploy): promote docs-v2.4.3 to production (#2617)
  fix(applications): apply live test results and define each resource by its role (#2626)
…hree sentences

- pt-br pages write the class as "recurso da plataforma" instead of the
  English "Platform Resource" (8 Marketplace guides, Bot Manager quickstart,
  AI Inference glossary, LoRA Fine-Tune, Marketplace permissions).
- LoRA Fine-Tune states the relation forward: a Platform Resource of its
  own that extends AI Inference.
- Managed Configurations names what the Modules section turns on.
- The pt-br Bot Manager quickstart calls the toggle a switch, as the
  Main Settings reference does, since "chave" reads as a key.
@bruno-andrade-azion
bruno-andrade-azion merged commit 5fcd8da into main Nov 11, 2026
9 checks passed
@bruno-andrade-azion
bruno-andrade-azion deleted the docs/mm-16249-retire-legacy-terms branch November 11, 2026 21:54
bruno-andrade-azion pushed a commit that referenced this pull request Nov 11, 2026
…-main

* origin/main: (21 commits)
  feat(nav): give every breadcrumb crumb a page and make CLI commands runnable (#2636)
  fix(cli): drop azion update workload-deployment, which the CLI does not expose (#2639)
  docs(terminology): retire Edge Node, module, and add-on from current pages (#2618)
  docs(migration): share the repeated migration-guide procedures as partials (#2619)
  fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612)
  docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611)
  docs(guides): make the auth layer and vector search tutorials runnable (#2566)
  chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637)
  fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565)
  docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567)
  docs(terraform): rewrite the samples for provider v2.10.0 (#2557)
  chore(deploy): promote docs-v2.4.4 to production (#2631)
  chore(main): release docs 2.4.4 (#2627)
  chore(deploy): promote docs-v2.4.3 to production (#2617)
  fix(applications): apply live test results and define each resource by its role (#2626)
  chore(main): release docs 2.4.3 (#2616)
  docs(applications): review the Applications section and apply the updated writing rules (#2615)
  chore(deps): bump npm and GitHub Actions dependencies (#2590)
  chore(deploy): promote docs-v2.4.2 to production (#2610)
  chore(main): release docs 2.4.2 (#2609)
  ...
bruno-andrade-azion pushed a commit that referenced this pull request Nov 11, 2026
* commit '7aa84b1d0': (22 commits)
  docs(nav): apply the review of the orphan-page triage
  feat(nav): give every breadcrumb crumb a page and make CLI commands runnable (#2636)
  fix(cli): drop azion update workload-deployment, which the CLI does not expose (#2639)
  docs(terminology): retire Edge Node, module, and add-on from current pages (#2618)
  docs(migration): share the repeated migration-guide procedures as partials (#2619)
  fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612)
  docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611)
  docs(guides): make the auth layer and vector search tutorials runnable (#2566)
  chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637)
  fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565)
  docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567)
  docs(terraform): rewrite the samples for provider v2.10.0 (#2557)
  chore(deploy): promote docs-v2.4.4 to production (#2631)
  chore(main): release docs 2.4.4 (#2627)
  chore(deploy): promote docs-v2.4.3 to production (#2617)
  fix(applications): apply live test results and define each resource by its role (#2626)
  chore(main): release docs 2.4.3 (#2616)
  docs(applications): review the Applications section and apply the updated writing rules (#2615)
  chore(deps): bump npm and GitHub Actions dependencies (#2590)
  chore(deploy): promote docs-v2.4.2 to production (#2610)
  ...
bruno-andrade-azion pushed a commit that referenced this pull request Nov 12, 2026
* origin/main: (24 commits)
  chore(nav): count only visible rows toward the navcheck soft max (#2640)
  docs(nav): triage the pages outside the navigation (#2593)
  fix(guides): match the QStash variable and the Functions usage response to the code (#2571)
  feat(nav): give every breadcrumb crumb a page and make CLI commands runnable (#2636)
  fix(cli): drop azion update workload-deployment, which the CLI does not expose (#2639)
  docs(terminology): retire Edge Node, module, and add-on from current pages (#2618)
  docs(migration): share the repeated migration-guide procedures as partials (#2619)
  fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612)
  docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611)
  docs(guides): make the auth layer and vector search tutorials runnable (#2566)
  chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637)
  fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565)
  docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567)
  docs(terraform): rewrite the samples for provider v2.10.0 (#2557)
  chore(deploy): promote docs-v2.4.4 to production (#2631)
  chore(main): release docs 2.4.4 (#2627)
  chore(deploy): promote docs-v2.4.3 to production (#2617)
  fix(applications): apply live test results and define each resource by its role (#2626)
  chore(main): release docs 2.4.3 (#2616)
  docs(applications): review the Applications section and apply the updated writing rules (#2615)
  ...
bruno-andrade-azion pushed a commit that referenced this pull request Nov 12, 2026
…y-filter-removal

* origin/main: (24 commits)
  chore(nav): count only visible rows toward the navcheck soft max (#2640)
  docs(nav): triage the pages outside the navigation (#2593)
  fix(guides): match the QStash variable and the Functions usage response to the code (#2571)
  feat(nav): give every breadcrumb crumb a page and make CLI commands runnable (#2636)
  fix(cli): drop azion update workload-deployment, which the CLI does not expose (#2639)
  docs(terminology): retire Edge Node, module, and add-on from current pages (#2618)
  docs(migration): share the repeated migration-guide procedures as partials (#2619)
  fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612)
  docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611)
  docs(guides): make the auth layer and vector search tutorials runnable (#2566)
  chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637)
  fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565)
  docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567)
  docs(terraform): rewrite the samples for provider v2.10.0 (#2557)
  chore(deploy): promote docs-v2.4.4 to production (#2631)
  chore(main): release docs 2.4.4 (#2627)
  chore(deploy): promote docs-v2.4.3 to production (#2617)
  fix(applications): apply live test results and define each resource by its role (#2626)
  chore(main): release docs 2.4.3 (#2616)
  docs(applications): review the Applications section and apply the updated writing rules (#2615)
  ...
bruno-andrade-azion pushed a commit that referenced this pull request Nov 12, 2026
* origin/main: (29 commits)
  fix(structure): tag bare code fences, fix heading skips, add pt-br meta_tags (#2629)
  docs(style-guide): drop the nonexistent GlossaryFilter from the glossary template (#2577)
  docs(release-notes): fix the October 14 anchor and merge the duplicate February 24 entry (#2572)
  fix(orchestrator): fix broken bind and create-service API samples (#2574)
  docs(readability): split the long sentences in the Runtime, CLI, Reference, and KV Store pages (#2635)
  chore(nav): count only visible rows toward the navcheck soft max (#2640)
  docs(nav): triage the pages outside the navigation (#2593)
  fix(guides): match the QStash variable and the Functions usage response to the code (#2571)
  feat(nav): give every breadcrumb crumb a page and make CLI commands runnable (#2636)
  fix(cli): drop azion update workload-deployment, which the CLI does not expose (#2639)
  docs(terminology): retire Edge Node, module, and add-on from current pages (#2618)
  docs(migration): share the repeated migration-guide procedures as partials (#2619)
  fix(marketplace): drop the Azion CLI prerequisite from firewall integration guides (#2612)
  docs(guides): replace the residual "These checks confirm" lines with use-case expect blocks (#2611)
  docs(guides): make the auth layer and vector search tutorials runnable (#2566)
  chore(scripts): add pnpm lint:terraform to validate Terraform samples (#2637)
  fix(firewall): correct the CLI binding, the WAF config sample, and the JWT paywall steps (#2565)
  docs(cli): document azion workload-deployment and fix pages that say the CLI cannot bind a deployment (#2567)
  docs(terraform): rewrite the samples for provider v2.10.0 (#2557)
  chore(deploy): promote docs-v2.4.4 to production (#2631)
  ...

# Conflicts:
#	apps/docs/src/content/docs/en/pages/observe/real-time-events/data-sources.mdx
#	apps/docs/src/content/docs/pt-br/pages/observe/real-time-events/fontes-de-dados.mdx
marcus-souza-azion added a commit that referenced this pull request Nov 12, 2026
…tion

Restore release-notes.mdx: its entries are records and are never
rewritten, per the changelog rules. Replace desempenho in the
infra-automation description, which #2618 kept when it merged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants