TabContents -> WebContentsImpl, part 14.

content/public/browser/site_instance.h

Index: content/public/browser/site_instance.h
diff --git a/content/public/browser/site_instance.h b/content/public/browser/site_instance.h
index 37c6201bae9282066a4b125b8ae5e25ba9d78c18..66081ec1f1f53feb38bf64a5fc5d4cb61c24fb33 100644
--- a/content/public/browser/site_instance.h
+++ b/content/public/browser/site_instance.h
@@ -27,8 +27,8 @@ class RenderProcessHost;
 // to the other).  We represent instances using the BrowsingInstance class.
 //
 // In --process-per-tab, one SiteInstance is created for each tab (i.e., in the
-// TabContents constructor), unless the tab is created by script (i.e., in
-// TabContents::CreateNewView).  This corresponds to one process per
+// WebContents constructor), unless the tab is created by script (i.e., in
+// WebContents::CreateNewView).  This corresponds to one process per
 // BrowsingInstance.
 //
 // In process-per-site-instance (the current default process model),
@@ -42,7 +42,7 @@ class RenderProcessHost;
 // throughout the entire browser context.  This ensures that only one process
 // will be dedicated to each site.
 //
-// Each NavigationEntry for a TabContents points to the SiteInstance that
+// Each NavigationEntry for a WebContents points to the SiteInstance that
 // rendered it.  Each RenderViewHost also points to the SiteInstance that it is
 // associated with.  A SiteInstance keeps track of the number of these
 // references and deletes itself when the count goes to zero.  This means that