From 5051af2e3a70a1854c36d0fe96594d7b42d025e2 Mon Sep 17 00:00:00 2001
From: Rohan Santhosh Kumar <181558744+Rohan5commit@users.noreply.github.com>
Date: Thu, 28 May 2026 11:47:11 +0800
Subject: [PATCH] docs: fix the tracing guide wording

---
 doc/dev-guide/src/tracing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/dev-guide/src/tracing.md b/doc/dev-guide/src/tracing.md
index 75caca1efc..a1d33869ad 100644
--- a/doc/dev-guide/src/tracing.md
+++ b/doc/dev-guide/src/tracing.md
@@ -118,6 +118,6 @@ Some good general heuristics:
   as these tend to help figure the puzzle of what-is-happening
 - Default to not instrumenting thin shim functions (or at least, only instrument
   them temporarily while figuring out the shape of a problem)
-- Be way of debug build timing - release optimisations make a huge difference,
+- Be aware of debug build timing - release optimisations make a huge difference,
   though debug is a lot faster to iterate on. If something isn't a problem in
   release don't pay it too much heed in debug.