Fix some style nites in PerformanceTests/README.md

third_party/WebKit/PerformanceTests/README.md

 # Blink Performance Tests
 
 [TOC]
 
 ## Overview
 
 Blink perf tests are used for micro benchmarking the surface of Blink that
-is exposed to the Web. They are the counterpart of [LayoutTests/]
-(https://chromium.googlesource.com/chromium/src/+/master/docs/testing/layout_tests.md)
+is exposed to the Web. They are the counterpart of [LayoutTests/](../../../docs/testing/layout_tests.md)
 but for performance coverage.
 
 ## Writing Tests
 Each test entry point is a HTML file written using
 [runner.js](resources/runner.js)
 testing framework. The test file is placed inside a sub folder of
 [Blink/PerformanceTests/](.)
 and is started by importing `runner.js` script into the document:
 ```
   <script src="../resources/runner.js"></script>
@@ skipping 22 matching lines @@
    setup: function () { ... },  // test setup logic, called once before each run
    run: function () { ... },  // contains the code to benchmark
    iterationCount: 5   // repeat the test 5 times
 });
 ```
 
 In the case of `PerfTestRunner.measureRunsPerSecond`, each run invokes
 `test.run` multiple times.
 
 **Tracing support**
+
 When the test is run through Telemetry, you can also collect timing of trace
 events that happen during each run by specifying `tracingCategories` &
 `traceEventsToMeasure` in the test object. For example:
 
 ```
 PerfTestRunner.measureTime({
    ...
    run: foo,
    iterationCount: 3,
    tracingCategories: 'blink',
@@ skipping 13 matching lines @@
                    v1      v2            v3     v4            v5     v6
 ```
 
 Besides outputting timeseries `[u1, u2, u3]`, telemetry perf test runner will
 also compute the total CPU times for trace events  'A' & 'B' per `foo()` run:
 
 *   CPU times of trace events A: `[v0 + v2, v4, 0.0]`
 *   CPU times of trace events B: `[0.0, v3, v5]`
 
 Example tracing synchronous tests:
-[append-child-measure-time.html](TestData/append-child-measure-time.html)
-[simple-html-measure-page-load-time.html](TestData/simple-html-measure-page-load-time.html)
+
+*   [append-child-measure-time.html](TestData/append-child-measure-time.html)
+
+*   [simple-html-measure-page-load-time.html](TestData/simple-html-measure-page-load-time.html)
 
 
 ### Asynchronous Perf Tests
 In asynchronous perf test, you define your test scheduler and do your own
 measurement. For example:
 
 ```
 var isDone = false;
 var startTime;
 
@@ skipping 22 matching lines @@
 });
 ```
 
 In the example above, the call
 `PerfTestRunner.measureValueAsync(value)` send the metric of a single run to
 the test runner and also let the runner know that it has finished a single run.
 Once the number of run reaches `iterationCount` (6 in the example above), the
 `done` callback is invoked, setting the your test state to finished.
 
 **Tracing support**
+
 Like synchronous perf tests, tracing metrics are only available when you run
 your tests with Telemetry.
 
 Unlike synchronous perf tests which the test runner framework handles test
 scheduling and tracing coverage for you, for most asynchronous tests, you need
 to manually mark when the async test begins
 (`PerfTestRunner.addRunTestStartMarker`) and ends
 (`PerfTestRunner.addRunTestEndMarker`). Once those are marked, specifying
 `tracingCategories` and `traceEventsToMeasure` will output CPU time metrics
 of trace events that happen during test runs in the fashion similar to the
 example of synchronous tracing test above.
 
 Example of tracing asynchronous tests:
+
 [color-changes-measure-frame-time.html](TestData/color-changes-measure-frame-time.html)
+
 [simple-blob-measure-async.html](TestData/simple-blob-measure-async.html)
 
 
 ## Running Tests
 
 ** Running tests directly in browser **
 Most of Blink Performance tests should be runnable by just open the test file
 directly in the browser. However, features like tracing metrics & HTML results
 viewer won't be supported.
 
 ** Running tests with Telemetry **
 Assuming your current directory is chromium/src/, you can run tests with:
+
 `./tools/perf/run_benchmark blink_perf [--test-path=<path to your tests>]`
 
 For information about all supported options, run:
+
 `./tools/perf/run_benchmark blink_perf --help`