What the developer wrote
Authored by kilavvy
doc: fix typos
What changed, and why it matters
This commit fixes a spelling mistake in a documentation file. It changes 'expensive_calulation' to 'expensive_calculation' in a code example within a markdown document. There is no code change that affects how the software runs, and no security risk is present.
No action needed. This is a documentation-only typo fix with no security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit is a single-character typo correction in doc/tracing.md, changing a misspelled variable name in a documentation code snippet. It does not modify any executable source code, build scripts, tests, or configuration. There is no functional or security impact.
Changed components
doc/tracing.mdInspect captured patch +1 / −1
diff --git a/doc/tracing.md b/doc/tracing.md
index b9323589..927fd34b 100644
--- a/doc/tracing.md
+++ b/doc/tracing.md
@@ -368,7 +368,7 @@ serialization of data structures is probably fine, a `sleep(10s)` not.
TRACEPOINT_SEMAPHORE(example, gated_expensive_argument);
…
if (TRACEPOINT_ACTIVE(example, gated_expensive_argument)) {
- expensive_argument = expensive_calulation();
+ expensive_argument = expensive_calculation();
TRACEPOINT(example, gated_expensive_argument, expensive_argument);
}
```
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.