[sanitizers] Simplify Explainer about dyld and weak overrides on Darwin. (NFC)

[rsundahl]

Summary

Presenting more than one way to satisfy the single-weak-ref requirement leads to
confusing messaging for the end user. Use the introduction of a single unused
weak variable as the preferred solution. This differential modifies D146745.

rdar://103453678

[yln]

LGTM, with nit!

llvm/docs/ReleaseNotes.rst

252–255

[rsundahl]

Added some suggested comments

llvm/docs/ReleaseNotes.rst

* LLDB is now able to show the subtype of signals found in a core file. For example
   memory tagging specific segfaults such as ``SIGSEGV: sync tag check fault``.
 
 Changes to Sanitizers
 ---------------------
 * For Darwin users that override weak symbols, note that the dynamic linker will
   only consider symbols in other mach-o modules which themselves contain at
   least one weak symbol. A consequence is that if your program or dylib contains
   an intended override of a weak symbol, then it must contain at least one weak
-  symbol as well for the override to be effective. That weak symbol may be the
-  intended override itself, an otherwise usused weak symbol added solely to meet
-  the requirement, or an existing but unrelated weak symbol.
-
-    Examples:
-      __attribute__((weak)) const char * __asan_default_options(void) {...}
+  symbol as well for the override to take effect.
 
+    Example:
+      // Add this to make sure your override takes effect
       __attribute__((weak,unused)) unsigned __enableOverrides;
-      
-      __attribute__((weak)) bool unrelatedWeakFlag;
+      // Example override
+      extern "C" const char *__asan_default_options() { ... }
 
 Other Changes
 -------------
 
 External Open Source Projects Using LLVM 15
 ===========================================
 
 * A project...