Fix a broken code search link.

The new source.chromium.org site accepts the link as-is, but for
cs.chromium.org, I get a "Request to Git backend failed." error. After
this CL, the link should work for both code search versions.

Change-Id: I576d88b3a6eb8bcbf7fcd26fa5ef6d3bba40d31b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067478Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Caleb Raitto <caraitto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743304}

docs/speed/benchmark/harnesses/rendering.md

@@ -27,7 +27,7 @@ These benchmarks are run on the [Chromium Perf Waterfall](https://ci.chromium.or
 
 ## What are the  rendering metrics
 
-Rendering metrics are [written in Javascript](https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/metrics/rendering). The list of all metrics and their meanings should be documented in the files they are defined in.
+Rendering metrics are [written in Javascript](https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/metrics/rendering/). The list of all metrics and their meanings should be documented in the files they are defined in.
 
 -   [cpu\_utilization.html](https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/metrics/rendering/cpu_utilization.html): `cpu_time_per_frame` and `tasks_per_frame`
 -   [frame\_time.html](https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/metrics/rendering/frame_time.html): `frame_times`, `percentage_smooth`, `frame_lengths`, `avg_surface_fps`, `jank_count`, and `ui_frame_times`