[clang-tools-extra] 0aad6b0 - [NFC] [clang-tidy] [doc] Don't use unicode character in doc (#180641)

[via cfe-commits]

Author: Florian Mayer
Date: 2026-02-09T17:50:37-08:00
New Revision: 0aad6b0657972ed10f30f3497277a9e6badc8b1c

URL: https://github.com/llvm/llvm-project/commit/0aad6b0657972ed10f30f3497277a9e6badc8b1c
DIFF: https://github.com/llvm/llvm-project/commit/0aad6b0657972ed10f30f3497277a9e6badc8b1c.diff

LOG: [NFC] [clang-tidy] [doc] Don't use unicode character in doc (#180641)

Added: 
    

Modified: 
    clang-tools-extra/docs/clang-tidy/checks/abseil/unchecked-statusor-access.rst

Removed: 
    


################################################################################
diff  --git a/clang-tools-extra/docs/clang-tidy/checks/abseil/unchecked-statusor-access.rst b/clang-tools-extra/docs/clang-tidy/checks/abseil/unchecked-statusor-access.rst
index 7aef674724b08..8a766e8f6abe4 100644
--- a/clang-tools-extra/docs/clang-tidy/checks/abseil/unchecked-statusor-access.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/abseil/unchecked-statusor-access.rst
@@ -24,7 +24,7 @@ ok (e.g. by passing a value to its constructor).
 Below we list some examples of safe and unsafe ``StatusOr<T>`` access
 patterns.
 
-Note: If the check isn’t behaving as you would have expected on a code
+Note: If the check isn't behaving as you would have expected on a code
 snippet, please `report it <http://github.com/llvm/llvm-project/issues/new>`__.
 
 False negatives