doc: Fix to use lower-case anchors in links to C++ Core Guidelines
What changed, and why it matters
This commit only fixes the capitalization of web link anchors in developer documentation. It changes three URLs from upper-case anchors (like #Renum-caps) to lower-case anchors (like #renum-caps) so the links work correctly. There is no change to any program code, no security issue, and no risk to users.
No security action needed. Treat as a normal documentation fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch updates three Markdown hyperlinks in doc/developer-notes.md to use lower-case fragment identifiers matching the C++ Core Guidelines website’s current anchor format. The change is purely documentation markup; no C++ source, build system, tests, or runtime behavior is modified.
Changed components
doc/developer-notes.mdInspect captured patch +3 / −3
diff --git a/doc/developer-notes.md b/doc/developer-notes.md
index d838ddff..eac70382 100644
--- a/doc/developer-notes.md
+++ b/doc/developer-notes.md
@@ -42,7 +42,7 @@ code.
- Constant names are all uppercase, and use `_` to separate words.
- Enumerator constants may be `snake_case`, `PascalCase` or `ALL_CAPS`.
This is a more tolerant policy than the [C++ Core
- Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Renum-caps),
+ Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#renum-caps),
which recommend using `snake_case`. Please use what seems appropriate.
- Class names, function names, and method names are UpperCamelCase
(PascalCase). Do not prefix class names with `C`. See [Internal interface
@@ -61,7 +61,7 @@ code.
between integer types, use functional casts such as `int(x)` or `int{x}`
instead of `(int) x`. When casting between more complex types, use `static_cast`.
Use `reinterpret_cast` and `const_cast` as appropriate.
- - Prefer [`list initialization ({})`](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Res-list) where possible.
+ - Prefer [`list initialization ({})`](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#res-list) where possible.
For example `int x{0};` instead of `int x = 0;` or `int x(0);`
- Recursion is checked by clang-tidy and thus must be made explicit. Use
`NOLINTNEXTLINE(misc-no-recursion)` to suppress the check.
@@ -790,7 +790,7 @@ Guidelines](https://isocpp.github.io/CppCoreGuidelines/).
Common misconceptions are clarified in those sections:
- Passing (non-)fundamental types in the [C++ Core
- Guideline](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rf-conventional).
+ Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#rf-conventional).
- If you use the `.h`, you must link the `.cpp`.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.