### Example URL(s) https://developers.cloudflare.com/changelog/post/2026-07-24-r2-sippy-azure-s3-compatible-support/ ### Actual Behavior https://developers.cloudflare.com/changelog/post/2026-07-24-r2-sippy-azure-s3-compatible-support/ renders the code block like this <img width="718" height="194" alt="Image" src="https://github.com/user-attachments/assets/13dced7b-9b2e-4da2-a11c-71cf6917d9b0" /> You can see that the `E>` at the end is of a different colour than the rest. ### Expected Behavior Consistent syntax highlighting of ```sh npx wrangler r2 bucket sippy enable <BUCKET_NAME> ``` e.g. <img width="393" height="68" alt="Image" src="https://github.com/user-attachments/assets/629b76a5-ebe5-4e58-997f-2da5bab513ed" /> ### Additional information the original PR (https://github.com/cloudflare/cloudflare-docs/pull/32310/changes) introduces this code block: ``` npx wrangler r2 bucket sippy enable <BUCKET_NAME> ``` so nothing looks off on that side, might be a rendering issue?
Example URL(s)
https://developers.cloudflare.com/changelog/post/2026-07-24-r2-sippy-azure-s3-compatible-support/
Actual Behavior
https://developers.cloudflare.com/changelog/post/2026-07-24-r2-sippy-azure-s3-compatible-support/ renders the code block like this
You can see that the
E>at the end is of a different colour than the rest.Expected Behavior
Consistent syntax highlighting of
e.g.
Additional information
the original PR (https://github.com/cloudflare/cloudflare-docs/pull/32310/changes) introduces this code block:
so nothing looks off on that side, might be a rendering issue?