Fix broken link and typos in Dangling Pointers markdown.
Bug: 1291138
Change-Id: I6e34b9ae3c6de903eee7a53b925ce4808b364e68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4189560
Reviewed-by: Arthur Sonzogni <[email protected]>
Commit-Queue: Charlie Reis <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1097061}
diff --git a/docs/dangling_ptr.md b/docs/dangling_ptr.md
index db37f72..8379d4e 100644
--- a/docs/dangling_ptr.md
+++ b/docs/dangling_ptr.md
@@ -1,12 +1,12 @@
-# Dangling pointer detector.
+# Dangling Pointer Detector
Dangling pointers are not a problem unless they are dereferenced and used.
However, they are a source of UaF bugs and highly discouraged unless you are
100% confident that they are never dereferenced after the pointed-to objects are
freed.
-See also the guide: [how to fix dangling pointers.
-[docs/dangling_ptr.md](./dangling_ptr_guide.md)
+See also the [Dangling Pointers Guide](./dangling_ptr_guide.md) for how to fix
+cases where dangling pointers occur.
Behind build flags, Chrome implements a dangling pointer detector. It causes
Chrome to crash, whenever a raw_ptr becomes dangling:
@@ -23,7 +23,7 @@
raw_ptr<T, DisableDanglingPtrDetection> ptr_may_dangle;
```
-The `DanglingUntriaged` has been used to annotate pre-existing dangling
+The `DanglingUntriaged` option has been used to annotate pre-existing dangling
pointers in Chrome:
```cpp
raw_ptr<T, DanglingUntriaged> ptr_dangling_mysteriously;
