From d5abc5ba89058c7041347f6bc516a19b3e34de3d Mon Sep 17 00:00:00 2001 From: Tudor Timi Date: Fri, 7 Nov 2025 15:25:47 +0100 Subject: [PATCH] Fix syntax of fenced code blocks containing text There's no reference of being able to use `{. }` for fenced code blocks in the GitHub flavored Markdown docs. --- review/developer/handling-comments.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/review/developer/handling-comments.md b/review/developer/handling-comments.md index cb43fb98..8f4df36b 100644 --- a/review/developer/handling-comments.md +++ b/review/developer/handling-comments.md @@ -64,11 +64,11 @@ If you can't answer that question, ask the reviewer for clarification. And then, if you understand the comments but disagree with them, it's important to think collaboratively, not combatively or defensively: -```txt {.bad} +```txt Bad: "No, I'm not going to do that." ``` -```txt {.good} +```txt Good: "I went with X because of [these pros/cons] with [these tradeoffs] My understanding is that using Y would be worse because of [these reasons]. Are you suggesting that Y better serves the original tradeoffs, that we should