Sequence[d]TaskRunner

docs/task_scheduler_migration.md

Index: docs/task_scheduler_migration.md
diff --git a/docs/task_scheduler_migration.md b/docs/task_scheduler_migration.md
index af458e310ddc8dd9e4af2fa4f4f649a5a717a6d6..a7200d46b834b6ccb5436c8c4c5557f2b5d2bdeb 100644
--- a/docs/task_scheduler_migration.md
+++ b/docs/task_scheduler_migration.md
@@ -81,7 +81,7 @@ assigned files by:
  2. Removing the plumbing: if GetTaskRunnerForThread(BrowserThread::FOO) is
     passed down into a component the prefered paradigm is to remove all of that
     plumbing and simply have the leaf layers requiring a TaskRunner get it from
-    base::CreateSequenceTaskRunnerWithTraits() directly.
+    base::CreateSequencedTaskRunnerWithTraits() directly.
  3. Ideally migrating from a single-threaded context to a
     [much preferred](threading_and_tasks.md#Prefer-Sequences-to-Threads) sequenced context.
     * Note: if your tasks use COM APIs (Component Object Model on Windows),