[docs] fix broken links

Change-Id: Ibca429fc356bbf52e44619d25de1a67a43a6e10f

docs/development/benchmarking/running_on_ci.md

@@ -36,7 +36,7 @@ We have shell scripts that run all of a layer's benchmarks at every commit to th
 * Peridot: [//peridot/tests/benchmarks](/peridot/tests/benchmarks)
 * Topaz: [//topaz/tests/benchmarks](https://fuchsia.googlesource.com/topaz/+/master/tests/benchmarks)
 
-These shell scripts are written using a helper library called [Runbenchmarks].  Add a
+These shell scripts are written using a helper library called [benchmarking].  Add a
 command to the appropriate script to execute your test.  See the existing commands for
 examples.
 
@@ -77,6 +77,6 @@ NOTE: We do not yet have a User guide for the [Performance Dashboard Version 2].
 [Performance Dashboard]: https://chromeperf.appspot.com/report
 [Performance Dashboard User Guide]: catapult_user_guide.md
 [Performance Dashboard Version 2]: https://v2spa-dot-chromeperf.appspot.com/
-[Runbenchmarks]: /garnet/testing/runbenchmarks
+[benchmarking]: /garnet/testing/benchmarking
 [//zircon/system/ulib/perftest]: /zircon/system/ulib/perftest/
 [//garnet/go/src/benchmarks]: /garnet/go/src/benchmarks

docs/development/benchmarking/trace_based_benchmarking.md

@@ -195,4 +195,4 @@ the [dashboard user guide] and the instructions for [automating benchmarks].
 [examples/benchmark]: /garnet/examples/benchmark/
 [results schema]: results_schema.md
 [best practices]: #best-practices
-[tracing]: ../tracing/tracing-usage-guide.md
+[tracing]: ../tracing/usage-guide.md

docs/development/tracing/cpuperf-provider.md

@@ -4,7 +4,7 @@
 
 The CPU Performance Monitor Trace Provider gives the user access to the
 performance counters built into the CPU using the
-[tracing system provided by Fuchsia](tracing-usage-guide.md).
+[tracing system provided by Fuchsia](usage-guide.md).
 
 At present this is only supported for Intel chipsets.
 

docs/development/tracing/design.md

@@ -62,7 +62,7 @@ Components which can be traced or offer tracing information to the system
 implement the `TraceProvider` FIDL protocol and register it with the
 `TraceRegistry`.  Once registered, they will receive messages whenever
 tracing is started or stopped and will have the opportunity to provide
-trace data encoded in the [Fuchsia Trace Format](trace-format.md).
+trace data encoded in the [Fuchsia Trace Format](trace-format/README.md).
 
 #### Kernel Trace Provider
 

docs/development/tracing/trace-format/README.md

@@ -3,7 +3,7 @@
 This document describes the binary format used to collect, store, and
 transmit Fuchsia trace records.
 
-See [Fuchsia Tracing System Design](design.md) for an overview.
+See [Fuchsia Tracing System Design](../design.md) for an overview.
 
 ## Purpose
 

docs/development/tracing/tutorial.md

@@ -656,5 +656,5 @@ end-to-end from the client, through the server, and back to the client.
   additions required by the trace provider in order to add tracing, or disable it completely.
 * [Fuchsia Tracing System Design](design.md)
   goes through the design goals of the tracing system.
-* [Fuchsia Trace Format](trace-format.md)
+* [Fuchsia Trace Format](trace-format/README.md)
   is a reference for the in-memory data format used by the tracing system.