diff --git a/scenarios/node_heap/README.md b/scenarios/node_heap/README.md
index cdf2ea6..4b937e7 100644
--- a/scenarios/node_heap/README.md
+++ b/scenarios/node_heap/README.md
@@ -14,17 +14,8 @@ Both functions are called once per iteration in a timed loop, creating equal **n
 
 **Objects Profile**: Should count allocation instances
 - Theoretically: 50% `a` / 50% `b` (equal number of calls)
-- Actually measured: 33% `a` / 66% `b` (biased toward larger objects)
+- Measured: Matches expectations
 
 **Space Profile**: Should count memory usage  
 - Expected: 33% `a` / 66% `b` (proportional to allocation sizes)
 - Measured: Matches expectations
-
-## Open Questions
-
-The objects profile shows bias toward larger allocations (66% vs 50% expected), suggesting the Node.js heap profiler may be:
-- Sampling based on allocation size rather than allocation count
-- Using size-weighted sampling for performance reasons
-- Exhibiting V8 engine optimization effects on string allocation
-
-**TODO**: Clarify with the Node.js profiler team how sampling works and why there's bias toward larger objects in the objects profile.