TabContents -> WebContentsImpl, part 14.

content/browser/renderer_host/resource_dispatcher_host_uitest.cc

Index: content/browser/renderer_host/resource_dispatcher_host_uitest.cc
diff --git a/content/browser/renderer_host/resource_dispatcher_host_uitest.cc b/content/browser/renderer_host/resource_dispatcher_host_uitest.cc
index 1ed043edbb95d743954fc3532491b3094a2f0f7b..df6f1b85ab0dfc1d2b5a7ea7611cbde9649a1405 100644
--- a/content/browser/renderer_host/resource_dispatcher_host_uitest.cc
+++ b/content/browser/renderer_host/resource_dispatcher_host_uitest.cc
@@ -366,7 +366,7 @@ TEST_F(ResourceDispatcherTest, DISABLED_CrossSiteNavigationErrorPage) {
   // Check that renderer-initiated navigations still work.  In a previous bug,
   // the ResourceDispatcherHost would think that such navigations were
   // cross-site, because we didn't clean up from the previous request.  Since
-  // TabContents was in the NORMAL state, it would ignore the attempt to run
+  // WebContentsImpl was in the NORMAL state, it would ignore the attempt to run
   // the onunload handler, and the navigation would fail. We can't test by
   // redirecting to javascript:window.location='someURL', since javascript:
   // URLs are prohibited by policy from interacting with sensitive chrome