Repository navigation
i18n(pt-br): label unlabelled asides and fix label casing - #2622
Open
bruno-andrade-azion wants to merge 1 commit into
Open
bruno-andrade-azion wants to merge 1 commit into
bruno-andrade-azion wants to merge 1 commit into
Conversation
Label 21 unlabelled Brazilian Portuguese asides with the localized labels the style guide sets (nota, dica, Atenção), so they match the ~440 pt-br asides already labelled. Capitalize the two `[atenção]` labels to `[Atenção]`, the casing the style guide fixes. Asides in files that open pull requests delete or rewrite at or next to those lines are left for after those merge.
This was referenced Nov 10, 2026
This branch has not been deployed
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-16255
Pages affected: 10 pt-br pages under
apps/docs/src/content/docs/pt-br/pages/and 2 pt snippets underapps/docs/src/includes/snippets/:arquiteturas/orch/application-deliver-automation.mdx,deploy-jornada/avancado/desinstalar-node/desinstalar-node.mdx,deploy-jornada/configurar-node/instalar-orch-agent/instalar-orch-agent.mdx,guias/troubleshooting/basic-troubleshooting.mdx,menu-principal/referencia/build/edge-application/domains/domains.mdx,menu-principal/referencia/build/edge-application/error-responses.mdx,menu-principal/referencia/build/edge-application/origins.mdx,menu-principal/referencia/build/edge-application/v3/edge-application-v3.mdx,menu-principal/referencia/build/edge-application/v3/main-settings-v3.mdx,menu-principal/release-notes/release-notes.mdx,JourneyAPI/pt/snippet.mdx,LetsEncryptExpiration/pt/snippet.mdxThe pt-br style guide localizes aside labels (
guia-de-estilo/componentes.mdx,guia-de-estilo/convencoes/paginas-bilingues.mdx)::::note[nota],:::tip[dica],:::caution[Atenção], withAtençãocapitalized. 435 pt-br asides already carry these labels, and the docs style gate flags the unlabelled ones as P1. This PR labels 21 of the 57 unlabelled pt-br asides on main and capitalizes the two[atenção]labels as[Atenção]. Every changed line is an aside opener. No aside body, link, or frontmatter field changes.What the reader sees. An unlabelled pt-br aside did not show English text before this change.
DocCallouthas no title row, and the.mdtwin already headed it with a localizedNota,Dica, orAtenção. With the label, the HTML callout opens withnota —,dica —, orAtenção —, like the other pt-br asides, and the.mdtwin heads the blockquote with the label as written (**nota**). The three**Aumente limites**tips now readdica — **Aumente limites**, which is the:::tip[dica]example the style guide itself gives.The two snippets.
JourneyAPI/ptis included only bybuild-jornada/edite-edge-app/main-settings.mdx, which #2587 deletes. No page importsLetsEncryptExpiration/pttoday, but the style guide lists it as an available snippet. Both stay in the repository for reuse, so the fix holds there.What this PR leaves alone, on purpose:
framework-overview,lang-wasm,form-builder, andcriar-certificado.zero-touch-provisioning,deploy-service,deploy-jornada/overview, andactive-em-producao.configurar-mtls,proteja-infraestrutura, andedge-firewall-monitorar-metricas.edge-node-first-steps.desinstalar-node.mdx:83,rodar-scripts.mdx:40,56,116,139,308, andtrabalhar-com-variaveis.mdx:24,121,239.rodar-scripts.mdx:56sits right after the block docs(orchestrator): split how-tos into API v4 and API v3 pages #2584 removes, sogit merge-treereports a conflict there.instalar-orch-agent.mdx:41,72.infra-automation.mdx:17andmanaged-configurations.mdx:16.guia-de-estilo/conteudo/referencia.mdx:153. It sits inside an example that is in en-US on purpose.[Opcional],[Importante],[Obsoleto],[Descontinuado], and[Em liberação gradual]say more than the type does, and they mirror their English twins.[Nota]and the two[importante]labels from the template guides. docs(platform): retire the v3 build and deploy journey pages #2587 deletesMainSettingsSAN.mdx, which has the third[atenção].LetsEncryptExpirationtype mismatch. The en twin is anoteand the pt twin is acaution, a separate question of content parity.Aside.astroor the Markdown twin. Content and code stay in separate PRs.How I checked it:
git diff --numstatshows 23 lines added and 23 removed across 12 files, with no line-ending churn. A grep of the diff finds no changed line that is not an aside opener.git merge-treefrom this branch and from main against the head of all 45 open PRs. This branch adds no conflict to any of them. I droppedrodar-scripts.mdx:56after it conflicted with docs(orchestrator): split how-tos into API v4 and API v3 pages #2584.docs_gate.py --checkfindings on these files go from 41 on main to 20. The 21 removed findings are all aside-label P1s, and no finding is new. The 4 aside-label findings that remain are the deferred lines indesinstalar-nodeandinstalar-orch-agent, plus the custom[Importante]in the release notes.linkcheck.pyreports 29 broken rendered links, all already on main and all outside the changed lines.edge-application-v3.mdxand 1 is inmain-settings-v3.mdx. They point to the old/produtos/build/edge-application/permalinks.LetsEncryptExpiration/pt. They are pt-br links inside a pt snippet.pnpm build:localpasses on Node 26: 2092 pages are built, and the frontmatter check exits 0.origins,domains, andinvestigacao-problemas-basico, and theorigins.mdanddomains.mdtwins.Atenção —,nota —, anddica —.> **Atenção**,> **nota**, and> **dica**.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 10 pages haslast_reviewed, and this PR changes no frontmatteredge-application-v3.mdxandmain-settings-v3.mdxalready have 29 broken links to the old/produtos/build/edge-application/permalinkspt-brupdated in this PR or follow-upi18nissue created: — this PR changes only pt-br content, and the English twins need no changepnpm build:local(build + frontmatter check) without errors