Repository navigation
i18n(pt-br): resync the drifted release notes, punctuation, and Edge Services pairs - #2624
Merged
Merged
Conversation
This was referenced Nov 10, 2026
…Services pairs - pt-br release notes: resync the February 24, 2026 entry with English, add the missing WebSocket Proxy heading to July 2, 2025, merge the split March 15, 2024 entry, and fix the Janeiro 2022 label. - pt-br punctuation: move the dash rules into a closing section that mirrors the English page. - en Edge Services reference: turn the stray Uninstall heading into the third trigger item, as the pt-br page already has it. MM-16256
… dash rules of the punctuation pair
marcus-souza-azion
force-pushed
the
i18n/mm-16256-resync-drifted-pairs
branch
from
November 12, 2026 15:38
188d766 to
c81569f
Compare
6 of 14 tasks
bruno-andrade-azion
pushed a commit
that referenced
this pull request
Nov 12, 2026
* origin/main: (39 commits) fix(terminology): replace desempenho and aplicativo in pt-br pages (#2621) docs(observe): fix dataset name, Data Stream filter, and Grafana Data path (#2573) fix(fundamentals): rewrite the Load Balancer steps in minimize-downtime from the reference (#2578) i18n(pt-br): label unlabelled asides and fix label casing (#2622) fix(links): point pt-br links to their existing pt-br pages (#2620) i18n(pt-br): resync the drifted release notes, punctuation, and Edge Services pairs (#2624) i18n(pt-br): pair three pages with their English versions by namespace (#2625) docs(style-guide): adopt the jsonl tag for JSON Lines samples (#2642) chore(lint): check the changelog entries a PR adds (#2634) [NO-ISSUE] ci: replace technote-space/assign-author (SO-5131) (#2591) 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) ... # Conflicts: # apps/docs/src/content/docs/en/pages/store/sql-database/glossary.mdx # apps/docs/src/content/docs/pt-br/pages/store/sql-database/glossario.mdx
bruno-andrade-azion
pushed a commit
that referenced
this pull request
Nov 12, 2026
* origin/main: (53 commits) docs(style-guide): standardize Azion Console click paths (#2596) docs(store): name the SQL and Storage libraries by their scoped packages (#2575) fix(terminology): replace desempenho and aplicativo in pt-br pages (#2621) docs(observe): fix dataset name, Data Stream filter, and Grafana Data path (#2573) fix(fundamentals): rewrite the Load Balancer steps in minimize-downtime from the reference (#2578) i18n(pt-br): label unlabelled asides and fix label casing (#2622) fix(links): point pt-br links to their existing pt-br pages (#2620) i18n(pt-br): resync the drifted release notes, punctuation, and Edge Services pairs (#2624) i18n(pt-br): pair three pages with their English versions by namespace (#2625) docs(style-guide): adopt the jsonl tag for JSON Lines samples (#2642) chore(lint): check the changelog entries a PR adds (#2634) [NO-ISSUE] ci: replace technote-space/assign-author (SO-5131) (#2591) 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) ... # Conflicts: # apps/docs/src/content/docs/en/pages/main-menu/reference/accounts/personal-tokens.mdx # apps/docs/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx # apps/docs/src/content/docs/pt-br/pages/menu-principal/referencia/contas/personal-tokens.mdx
bruno-andrade-azion
pushed a commit
that referenced
this pull request
Nov 12, 2026
* origin/main: (48 commits) docs(templates): list the Astro templates that only the showcase covered (#2595) docs(orchestrator): consolidate duplicate guides and write How it works (#2588) docs(secure): retire the pre-Workloads security journey and guide pages (#2586) docs(applications): Run Function needs only Functions; fix WEBP and CORS prerequisites (#2580) docs(fundamentals): apply the reader review and the style guide to the Fundamentals pages (#2558) fix(observe): name the query editor list instead of its position in the Grafana guides (#2643) docs(templates): migrate the legacy template guides to the current guide pattern (#2597) docs(style-guide): standardize Azion Console click paths (#2596) docs(store): name the SQL and Storage libraries by their scoped packages (#2575) fix(terminology): replace desempenho and aplicativo in pt-br pages (#2621) docs(observe): fix dataset name, Data Stream filter, and Grafana Data path (#2573) fix(fundamentals): rewrite the Load Balancer steps in minimize-downtime from the reference (#2578) i18n(pt-br): label unlabelled asides and fix label casing (#2622) fix(links): point pt-br links to their existing pt-br pages (#2620) i18n(pt-br): resync the drifted release notes, punctuation, and Edge Services pairs (#2624) i18n(pt-br): pair three pages with their English versions by namespace (#2625) docs(style-guide): adopt the jsonl tag for JSON Lines samples (#2642) chore(lint): check the changelog entries a PR adds (#2634) [NO-ISSUE] ci: replace technote-space/assign-author (SO-5131) (#2591) fix(structure): tag bare code fences, fix heading skips, add pt-br meta_tags (#2629) ... # Conflicts: # apps/docs/src/content/docs/en/pages/main-menu/reference/accounts/billing.mdx # apps/docs/src/content/docs/en/pages/main-menu/reference/accounts/teams-permissions.mdx # apps/docs/src/content/docs/pt-br/pages/menu-principal/referencia/contas/faturamento.mdx # apps/docs/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Related issue: MM-16256
Pages affected:
/pt-br/documentacao/changelog/(pt-br/pages/menu-principal/release-notes/release-notes.mdx),/pt-br/documentacao/guia-de-estilo/formatacao/pontuacao/(pt-br/pages/guia-de-estilo/formatacao/pontuacao.mdx),/en/documentation/style-guide/formatting/punctuation/(en/pages/style-guide/formatting/punctuation.mdx),/en/documentation/platform/orchestrator/edge-services/(en/pages/main-menu/reference/deploy/edge-orchestrator/edge-services.mdx)The October docs review listed 14 en/pt-br pairs whose structure diverged, plus
http-error-status-codes. I re-measured every pair on currentmain(headings, code blocks, word count, and<DocUpdate>entries) and checked each against the open PRs. Three pairs still drift with no open PR resyncing them. This PR fixes those three. The other pairs are listed further down.pt-br release notes. Four entries no longer matched English:
Recursossection. It also had two bug-fix items that English never had: a second copy of the country-code fix, and an internalverifyTabguard. The entry now matches the single English entry that docs(release-notes): fix the October 14 anchor and merge the duplicate February 24 entry #2572 left onmainwhen it merged the two English February 24 entries.### WebSocket Proxyheading was missing.Azion Integrationstag. They are now one entry, as in English: tagMarketplace, anchor15-de-marco-2024, heading### Integrações da Azion. The#15-de-marco-2024-azion-integrationsfragment goes away, and no internal link points to it.Janeeiro, and now readsJaneiro. The anchor changes with it, fromjaneeiro-2022tojaneiro-2022, because the changelog lint from chore(lint): check the changelog entries a PR adds #2634 requires an anchor to start with its label's date. No internal link points to the old anchor. An external link to#janeeiro-2022now opens the top of the page.pt-br punctuation style guide. English closes with a
Brazilian Portuguese differs on dashessection. The pt-br page had folded that text intoPrefira um ponto ao travessão. The bilingual-pages convention has the pt-br structure follow English, so the two paragraphs move to a closingO português do Brasil difere no travessãosection. The travessão section keeps one sentence for the US English rule, with the same condition as English: the dash takes no space when it is genuinely the right mark.en punctuation style guide. The English closing section said the page holds in both languages apart from the dash and the serial comma. The hyphen differs too: pt-br follows the Acordo Ortográfico, which the pt-br page already states. The English sentence now names the hyphen, so both closing sections say the same thing.
en Edge Services reference. The third trigger was a stray
#### Uninstallheading, a jump from h2 to h4, where pt-br already lists it as**3) Uninstall:**after1) Installand2) Reload. English now matches pt-br. Resyncing pt-br from English would have copied the defect. The#uninstallfragment goes away, and no internal link points to it.Pairs this PR leaves alone, on purpose:
pricing: the pt-br page doubles its headings on purpose. It has a Dólar tab and a Real tab, and the Dólar tab has the same structure as English. The live page's outline (PricingTableOfContents) lists each section once and follows the active tab.run-scriptsandwork-with-variables: pt-br uses<Code>where English uses a fenced block, and the content is the same.main:langgraph-template,main-settings, and the style guide'scasos-de-uso.mongodb-template.nextjs-static-boilerplate.http-error-status-codes.main-settings.form-builderand thenextalshowcase.agreements/sla/sla.mdxrepeats the May 25, 2016 SLA after the current one. That version already has its own page. The repeated copy also differs from the archive page by one word ("Firewall" where the archive page says "Edge Firewall"). The agreements pages are owned by Legal, so this goes to MM-16265 and not here.How I checked it:
Rebase. The branch is rebased onto current
main, which includes docs(release-notes): fix the October 14 anchor and merge the duplicate February 24 entry #2572 and chore(lint): check the changelog entries a PR adds #2634.Structure. Headings match in all three pairs:
The release notes have 157
<DocUpdate>entries in each language, and the heading levels align line for line.No other drift. A scan of all 1,037 en/pt-br pairs on
mainat a93e244, before the rebase, finds no other pair whose headings, code blocks, or length diverge beyond the ones listed above.The changelog lint.
lint-changelog.mjsfrommainfinds no issue in either release notes page, 314 entries checked.Conflicts with open PRs. I ran
git merge-treeagainst every open PR that touches these files.mainalone, and none of them is in this PR.The docs style gate.
docs_gate.py --checkfinds 10 findings on these files, all on lines this PR does not change, and none on the two punctuation pages. The h2-to-h4 jump in Edge Services is gone.Links.
linkcheck.pyreports 0 broken links and 0 unpaired namespaces on the four files.Formatting.
prettier --checkpasses on the four files.The build.
pnpm build:localpassed on Node 26 before the rebase: 2092 pages are built, and the frontmatter check exits 0. I did not run it locally after the rebase. CI's Build job passes on the rebased head.The rendered output. Before the rebase, I read the built HTML and the
.mdtwin of each page.#websocket-proxy,#integracoes-da-azion, and a single#15-de-marco-2024entry, with noverifyTaborNO-ISSUEleft.#o-portugues-do-brasil-difere-no-travessao.h4, and its twin lists the three triggers as1),2), and3).Type of change
feat)fix) — typo, broken link, wrong informationdocs) — rewrite, expansion, upkeepi18n)refactor/chore) — reviewed by UXE, no content mixed inAuthor checklist
type(scope): summary(see GOVERNANCE.md §4)title,description,meta_tags,namespace,permalink,last_reviewed— none of the four pages haslast_reviewed, and this PR changes no frontmatterpt-brupdated in this PR or follow-upi18nissue created: — the pt-br changes are in this PR, and the two English changes bring English in line with pt-brpnpm build:local(build + frontmatter check) without errors — it passed before the rebase ontomain; on the rebased branch only CI's Build job ran, and it passed