fixed up benchmarking file names, fixed commits, truncated statistics section. Add real life example

1 files changed, 2 insertions, 2 deletions

diff --git a/railties/doc/guides/benchmarking_and_profiling/rubyprof.txt b/railties/doc/guides/benchmarking_and_profiling/rubyprof.txt
index edf036d13e..a24302390e 100644
--- a/railties/doc/guides/benchmarking_and_profiling/rubyprof.txt
+++ b/railties/doc/guides/benchmarking_and_profiling/rubyprof.txt
@@ -105,7 +105,7 @@ Total: 509.724609
   1.01      5.13     5.13     0.00     0.00       27  Array#-
 ============================================================================
 
-Very similar to the processing time format. The main difference here is that instead of calculating time we are now concerned with the amount of KB put into memory *(or is it strictly the heap)* 
+Very similar to the processing time format. The main difference here is that instead of calculating time we are now concerned with the amount of KB put into memory *(or is it strictly into the heap) can I get clarification on this minor point?* 
 
 So for <Module::YAML>#quick_emit which is  singleton method on the class YAML it uses 57.66 KB in total, 23.57 through its own actions, 6.69 from actions it calls itself and that it was called twice.
 
@@ -124,7 +124,7 @@ Total: 6537.000000
   1.44    111.00    94.00     0.00    17.00       31  Array#each-1
 ============================================================================
 
- #TODO Find correct terminology for how to describe what this is exactly profiling as in are there really 2203 array objects. 
+ #TODO Find correct terminology for how to describe what this is exactly profiling as in are there really 2203 array objects or 2203 pointers to array objects?. 
 
 === Graph Files ===