Update intermittent_memory_spike.md

diff --git a/documentation/tutorial/intermittent_memory_spike.md b/documentation/tutorial/intermittent_memory_spike.md
index bb31a66bbe6123be84ccea8f626b279da5106439..b3b1692c6de2d8293a3093027311c7017b41c958 100644 (file)
--- a/documentation/tutorial/intermittent_memory_spike.md
+++ b/documentation/tutorial/intermittent_memory_spike.md
@@ -53,8 +53,8 @@ Events that are written to the EventPipe can come from multiple sources (or prov
 #### Writing the tool...
 We have two requirements in order to implemented a tool that will create a dump file based on memory consumption:
 
-Being able to read dotnet memory counter to know when it breaches the specified threshold
-Generate the actual core dump
++Being able to read dotnet memory counter to know when it breaches the specified threshold
++Generate the actual core dump
 
 Let's start with the first requirement, reading dotnet counters. As explained earlier, we can use the EventPipe mechanism to read counters from the runtime. In this case, the provider that writes counter events is System.Runtime. Below is the code that 
 sets up the System.Runtime provider for use in our tool: