Fix flame graph

Author: savannahostrowski

peps/pep-0830.rst

@@ -201,10 +201,10 @@ processes.  The Linux kernel has no DWARF unwinder and, per Linus Torvalds,
 will not gain one [#torvalds_fp]_; the kernel developed its own ORC format for
 internal use instead.
 
-The impact extends beyond CPU profiling.  Off-CPU flamegraphs (used to
+The impact extends beyond CPU profiling.  Off-CPU flame graphs (used to
 diagnose latency caused by I/O waits, lock contention, and scheduling delays)
 rely on the same ``bpf_get_stackid()`` helper to capture the stack at the point
-where a thread blocks.  As Brendan Gregg notes, off-CPU flamegraphs "can be
+where a thread blocks.  As Brendan Gregg notes, off-CPU flame graphs "can be
 dominated by libc read/write and mutex functions, so without frame pointers end
 up mostly broken" [#gregg2024]_.  For Python services where latency matters
 more than raw CPU throughput, off-CPU profiling is often the most valuable