diff --git a/doc/contributing/investigating_native_memory_leak.md b/doc/contributing/investigating-native-memory-leak.md
similarity index 99%
rename from doc/contributing/investigating_native_memory_leak.md
rename to doc/contributing/investigating-native-memory-leak.md
index fba03a1ed9a7cf..667c5a8355afbc 100644
--- a/doc/contributing/investigating_native_memory_leak.md
+++ b/doc/contributing/investigating-native-memory-leak.md
@@ -450,3 +450,6 @@ Running Valgrind using the debug build of Node.js shows:
 
 Now we can see the specific file name and line in the Node.js code which
 caused the allocation (inspector\_agent.cc:140).
+
+Thusly, we can examine the line (and its surrounding code) in order
+to find a potential solution for the memory leak.