[turbolizer] Fixed naming of turbolizer perf script.

Change was meant to be in previous patch but was accidentally reverted.
README.md updated with new filename, also.

BUG=

Review-Url: https://codereview.chromium.org/2184223005
Cr-Commit-Position: refs/heads/master@{#38134}

tools/turbolizer/README.md

@@ -15,10 +15,10 @@ the turbolizer directory, e.g.:
     python -m SimpleHTTPServer 8000
 
 Optionally, profiling data generated by the perf tools in linux can be merged
-with the .json files using the perf-turbo.py file included. The following
+with the .json files using the turbolizer-perf.py file included. The following
 command is an example of using the perf script:
 
-    perf script -i perf.data.jitted -s perf-turbo.py turbo-main.json
+    perf script -i perf.data.jitted -s turbolizer-perf.py turbo-main.json
 
 The output of the above command is a json object that can be piped to a file
 which, when uploaded to turbolizer, will display the event counts from perf next
@@ -50,7 +50,7 @@ The basic example of generating the required data is as follows:
 
     perf record -k mono /path/to/d8 --turbo --trace-turbo --perf-prof main.js
     perf inject -j -i perf.data -o perf.data.jitted
-    perf script -i perf.data.jitted -s perf-turbo.py turbo-main.json
+    perf script -i perf.data.jitted -s turbolizer-perf.py turbo-main.json
 
 These commands combined will run and profile d8, merge the output into a single
 'perf.data.jitted' file, then take the event data from that and link them to the