[Threading docs] Cross-reference FAQ and main docs
and follow-up on nits to https://chromium-review.googlesource.com/c/chromium/src/+/1261855
[email protected]
Change-Id: I2ca5305af71fa89e13be10e40779641362529a42
Reviewed-on: https://chromium-review.googlesource.com/c/1342770
Commit-Queue: François Doray <[email protected]>
Reviewed-by: François Doray <[email protected]>
Cr-Commit-Position: refs/heads/master@{#610416}diff --git a/docs/threading_and_tasks.md b/docs/threading_and_tasks.md
index 9064e7e7..694df67 100644
--- a/docs/threading_and_tasks.md
+++ b/docs/threading_and_tasks.md
@@ -2,6 +2,9 @@
[TOC]
+Note: See [Threading and Tasks FAQ](threading_and_tasks_faq.md) for more
+examples.
+
## Overview
Chromium is a very multithreaded product. We try to keep the UI as responsive as
@@ -77,7 +80,7 @@
bug to use base::CreateSequencedTaskRunnerWithTraits() when fixed).
Detailed documentation on how to migrate from single-threaded contexts to
-sequenced contexts can be found [here](threading_and_tasks_faq.md#How-can-I-migrate-from-SingleThreadTaskRunner-to-SequencedTaskRunner_).
+sequenced contexts can be found [here](threading_and_tasks_faq.md#How-to-migrate-from-SingleThreadTaskRunner-to-SequencedTaskRunner).
The discussion below covers all of these ways to execute tasks in details.
@@ -677,3 +680,6 @@
Note that this still allows removing all layers of plumbing between //chrome and
that component since unit tests will use the leaf layer directly.
+
+## FAQ
+See [Threading and Tasks FAQ](threading_and_tasks_faq.md) for more examples.
