Fixing documentation

Author: William Kennedy

topics/memory_trace/readme.md

@@ -8,8 +8,7 @@ There is no way to identify specifically in the code where a leak is occuring. W
 
 To validate if a memory leak is truly occuring use the GODEBUG environmental variable. Setting gctrace=1 causes the garbage collector to emit a single line to standard error at each collection, summarizing the amount of memory collected and the length of the pause. Setting gctrace=2 emits the same summary but also repeats each collection. The format of this line is subject to change:
 
-    go build
-    GODEBUG=gctrace=1 ./memory_trace
+    export GODEBUG=gctrace=1
 
     gc # @#s #%: #+...+# ms clock, #+...+# ms cpu, #->#-># MB, # MB goal, # P