Rename TaskRunner::RunsTasksOnCurrentThread() in //content

content/public/test/test_browser_thread.cc

Index: content/public/test/test_browser_thread.cc
diff --git a/content/public/test/test_browser_thread.cc b/content/public/test/test_browser_thread.cc
index 54db8953941918246ff1cecda725c13340a1ca65..2efe6929554797ae677efc05cd936d1af42adc53 100644
--- a/content/public/test/test_browser_thread.cc
+++ b/content/public/test/test_browser_thread.cc
@@ -59,7 +59,7 @@ TestBrowserThread::~TestBrowserThread() {
   // been flushed and deleted in Stop(). In the case of an externally provided
   // MessageLoop however, this means that TaskRunners obtained through
   // |BrowserThreadImpl::GetTaskRunnerForThread(identifier_)| will no longer
-  // recognize their BrowserThreadImpl for RunsTasksOnCurrentThread(). This
+  // recognize their BrowserThreadImpl for RunsTasksInCurrentSequence(). This
   // happens most often when such verifications are made from
   // MessageLoop::DestructionObservers. Callers that care to work around that
   // should instead use this shutdown sequence: