Fix link-breaking typo in unsafe_buffers.md
Bug: none
Change-Id: Ia3cb33cf49edea7131f47d18d179d8bbd8e069e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6480478
Commit-Queue: Evan Stade <[email protected]>
Reviewed-by: Tom Sepez <[email protected]>
Commit-Queue: Tom Sepez <[email protected]>
Auto-Submit: Evan Stade <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1450167}
diff --git a/docs/unsafe_buffers.md b/docs/unsafe_buffers.md
index 4f8c655..4a4d5e4 100644
--- a/docs/unsafe_buffers.md
+++ b/docs/unsafe_buffers.md
@@ -138,13 +138,13 @@
### Opting out individual expressions
Individual expressions or blocks of code are opted out by using the
-`UNSAFE_BUFFERS()` macro as defined in [`//base/compiler_specific.h`[(../base/compiler_specific.h)
+`UNSAFE_BUFFERS()` macro as defined in [`//base/compiler_specific.h`](../base/compiler_specific.h)
file. These should be rare once a project is fully converted, except
perhaps when working with C-style external APIs. These must
always be accompanied by a `// SAFETY:` comment explaining in detail
how the code has been evaluated to be safe for all possible input.
-Code introducing UNSAFE_BUFFERS() macro invocations without corresponding
+Code introducing `UNSAFE_BUFFERS()` macro invocations without corresponding
`// SAFETY:` comment should be summarily rejected during code review.
To allow for incremental conversion, code can be temporarily opted out by
