RiskyChanges.md: use code formatting in a few places

Change-Id: I6ead576a7ab498303358fcd583889d731e6f4907 Reviewed-on: https://go-review.googlesource.com/c/wiki/+/643296 Reviewed-by: Michael Knyszek <[email protected]>
golang · Jan 17, 2025 · b1a0705 · b1a0705
1 parent 0027f88
commit b1a0705
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/RiskyChanges.md b/RiskyChanges.md
@@ -12,10 +12,10 @@ revert** (for example, large CLs or stacks of CLs).
 
 If you plan on working on a change that may be risky, please do the following:
 1. Unless the entire change is absolutely trivial to revert, protect the new code paths with a
-   boolean flag, prefixed with "go125", that can be used to quickly toggle back to the old
+   boolean flag, prefixed with `go125`, that can be used to quickly toggle back to the old
    implementation.
-   It can be a simple bool constant, for example, const go125UseEvenBetterLinker = true.
-   Such flags **must be findable** by a simple grep for the string "go125".
+   It can be a simple bool constant, for example, `const go125UseEvenBetterLinker = true`.
+   Such flags **must be findable** by a simple grep for the string `go125`.
    That way we can find them without missing any, and they can be cleaned up when we get to the
    Go 1.26 cycle.
 2. Consider how you would answer the following questions for your change: