Repository navigation
docs(guides): remove the residual "These checks confirm" use-case lines - #2611
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
…es (MM-16252) PR #2457 left a "These checks confirm the <use case> use case." line at the end of the confirm sections of 32 guides, and its pt-br twin in the same 32 pages. The how-to style guide defines only two use-case lines ("uses the values of this example" and "use case, expect:"), so these lines are template residue. Every page still links each use case from a Next steps card or from the body, so no link is lost.
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-16252 (T40) · Epic MM-16212
Pages affected: 32 en guides and their 32 pt-br twins (see the diff). The en pages are in the Applications, Availability, Data, AI, Security, Observability and Streaming guides, plus
point-domain,integrate-siemsand the WAFapply-rule-setexample.#2457 moved use-case values and checks into the guides. It also left one line at the end of many confirm sections,
These checks confirm the [<use case>](…) use case.(pt-br:Estas verificações confirmam o caso de uso […](…).). The how-to style guide (style-guide/content/how-to-guides.mdx) defines only two use-case lines, "…uses the values of this example" and "In the […] use case, expect:", so these lines are template residue. Some pages stacked two or three of them back to back (point-domain,integrate-siems,restrict-an-origin-to-azion-with-origin-ip-acl), and others repeated a use case that the section had just named.This PR deletes all 39 lines in en and the 39 matching lines in pt-br, with one blank line each. Nothing else changes.
image-processorthrough three references in the body. The use-case pages also still link to these guides.integrate-siems), cluster 4 (EDU-2020-Remove-guides-from-Edge-Application-Ciphers #32,create-mcpandroute-an-api-path-to-a-backend) and cluster 6 (EDU-1988-update-reference-rte #25,debug-functions-dts), and none of those has its own task. The fix is the same everywhere, so this PR covers all of them.How I checked it
^These checks confirm the \[…\](…) use case\.$and the pt-br form) returns 0 matches after the change. The similar sentence inconnector-azion-edge-storage.mdx("Two checks confirm the delivery…") is real copy, and it stays.---separator (which would render as a heading), and the end of every file is unchanged.Known gap, out of scope: in
debug-functions-dts, the "Screen file uploads for malicious content" use case has a Next steps card but no "expect:" block, while the other two use cases on the page do. Writing that block is content work, not cleanup.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— no frontmatter is added or changedpt-brupdated in this PR or follow-upi18nissue created: —pt-bris updated in this PRpnpm build:local(build + frontmatter check) without errors — not run: the change only deletes whole paragraphs and touches no MDX syntax, frontmatter, or links; CI builds the branch