[bruno-andrade-azion]

What & why

Related issue: MM-16262, in the epic MM-16212
Pages affected: 49 pages in en and pt-br:

• the dated Terms of Service and the Savings Plan (27), plus the pt-br Terms of Service of May 12, 2026 and the pt-br index;
• the OpenNext guide and the pt-br v3 Main Settings reference;
• the Functions quickstart, the browserless, serverless functions, test origin and WebAssembly guides, the Edge Node reference and the pt-br WebAssembly language guide;
• the style guide's bilingual pages and procedures pages.

The ticket's counts come from the October 29 review. I measured them again on main, parsing frontmatter with gray-matter and skipping code blocks, and most of them don't hold up:

Ticket item	In the ticket	On main	Fixed here	Left to
H1 in the body	41 pages	0	—	—
Skipped heading level	30 pages	32	30	#2624 (Edge Services), #2598 (MongoDB template)
Missing meta_tags	15 pt-br pages	15	14	the pt-br April 26, 2023 terms, after #2625
namespace written as >-	2 namespaces	4 files	0	#2625
Code block with no language	1,247	31	23	#2558 (6), #2597 (1), #2593 (1)

• H1 in the body. The 41 pages are exactly the ones with a # ... comment inside a code block or a <Code code={...}> template literal. No page has a real H1 in its body.
• Release notes and changelog. They look like they jump from the title to H3, but they don't: DocUpdate renders each entry's date as an <h2>. I left them as they are.

Code blocks. A fence with no language reaches CodeBlock with no lang, because astro-code-blocks.ts passes node.lang ?? undefined. The webkit highlighter then falls back to JavaScript, so output such as Hello World! was tokenized as JavaScript.

• Output blocks now carry text, the tag docs(fundamentals): apply the reader review and the style guide to the Fundamentals pages #2558 uses.
• The two blocks in procedures that show page source carry mdx, like the block next to them.
• In the WebAssembly language guide, only the pt-br page changes, because docs(nav): triage the pages outside the navigation (MM-16244) #2593 deletes the English one.

Heading levels. No legal text changes.

• In the agreements, #### Previous versions of this document: becomes ## Previous versions of this document. That's how the current Terms of Service already write it. The anchor doesn't change, and the section now shows in the page's table of contents, as it does on the current terms.
• The OpenNext guide started at ###, so every heading moves up one level.
• In the pt-br v3 Main Settings reference, "Lista de portas disponíveis" becomes an H3, as in English.

meta_tags. Fourteen pt-br Terms of Service pages get 'Termos de serviço, Termos de serviço Azion', with the same value and position as the other pt-br terms. The April 26, 2023 page keeps its heading fix but doesn't get the meta_tags line yet. #2625 rewrites the namespace line right below it, so adding it now would conflict. It's a one-line change once #2625 merges.

How I checked it:

• I ran the measurement again on the branch. All that's left are the four release-note and changelog false positives and the items that the PRs above already fix.
• I ran git merge-tree against every open PR that touches these files: docs(applications): Run Function needs only Functions; fix WEBP and CORS prerequisites #2580, docs(platform): retire the v3 build and deploy journey pages #2587, docs(orchestrator): consolidate duplicate guides and write How it works #2588, docs(style-guide): standardize Azion Console click paths (MM-16248) #2596, fix(terminology): replace desempenho and aplicativo in pt-br pages #2621, i18n(pt-br): label unlabelled asides and fix label casing #2622 and i18n(pt-br): pair three pages with their English versions by namespace #2625. Once the April 26 meta_tags line was out, this branch caused no conflict with any of them. docs(applications): Run Function needs only Functions; fix WEBP and CORS prerequisites #2580, docs(platform): retire the v3 build and deploy journey pages #2587 and docs(style-guide): standardize Azion Console click paths (MM-16248) #2596 already conflict with main, but only in files this PR doesn't touch.
• The docs writer gate (docs_gate.py --check) on the 49 files finds nothing new and reports 69 fewer findings than main. The ones that go away are the heading skips, the colons in headings and the missing meta_tags.
• linkcheck.py returns the same result as on main:
  • 5 broken links that already exist: four pt-br terms that link to /tds/29-agosto-2024/, and one in the pt-br v3 Main Settings reference;
  • 3 terms namespaces with only one language. i18n(pt-br): pair three pages with their English versions by namespace #2625 pairs April 26, 2023 with March 30, 2023; November 25, 2022 stays pt-br only on purpose.
• pnpm ci:ratchet slugcheck passes at baseline 6. pnpm ci:ratchet linkcheck passes on the build: 159 broken links against a baseline of 221. This PR changes no link, so it doesn't account for the drop. pnpm lint:navcheck passes.
• pnpm build:local passes with Node 26: 2,092 pages, plus the frontmatter test. In the built HTML:
  • the Functions quickstart output reaches CodeBlock with lang: "text" and renders as a single text token;
  • the en March 15, 2024 terms and the pt-br April 26, 2023 terms render "Previous versions" as an h2 with a table-of-contents link;
  • the OpenNext guide's headings start at h2;
  • the pt-br March 15, 2024 terms carry <meta name="keywords" content="Termos de serviço, Termos de serviço Azion">.
  • as a control, a fence this PR leaves alone (Host header, http-error-status-codes, fixed by docs(fundamentals): apply the reader review and the style guide to the Fundamentals pages #2558) still renders with no lang, and Host example.com splits into JavaScript type, function and punctuation tokens.
• Not verified: I read the built HTML but didn't click through the pages in a browser.
• Not covered: nothing stops new fences without a language. That's the scope of chore(lint): check the code samples on the pages a PR changes #2623 (T46), and this PR doesn't change tooling. Prettier ignores .mdx in this repository, so it checks nothing here.

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 — no page in the repository carries last_reviewed, and the pt-br April 26, 2023 terms get meta_tags only after i18n(pt-br): pair three pages with their English versions by namespace #2625 merges
• No legacy "edge-" product names in the copy — this PR adds no copy; the touched pages keep their wording
• How-to/tutorial content includes at least one runnable, copy-paste-tested code block — no code block is added; existing blocks only get a language tag
• 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 or changed, but the touched pages already have 5 broken links and the agreements use absolute URLs; the agreements links belong to MM-16265
• 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: both languages are in this PR; the WebAssembly language guide changes only in pt-br, because docs(nav): triage the pages outside the navigation (MM-16244) #2593 deletes the English page
• I ran pnpm build:local (build + frontmatter check) without errors