Removal of Profile from content part 1.

content/browser/in_process_webkit/dom_storage_context.h

Index: content/browser/in_process_webkit/dom_storage_context.h
diff --git a/content/browser/in_process_webkit/dom_storage_context.h b/content/browser/in_process_webkit/dom_storage_context.h
index 2d3c6673b2eada23fe79a52407ef498d0166951a..cac9083479a287e83ec87a9a0c9a84bb4222e5ab 100644
--- a/content/browser/in_process_webkit/dom_storage_context.h
+++ b/content/browser/in_process_webkit/dom_storage_context.h
@@ -24,7 +24,7 @@ class SpecialStoragePolicy;
 }
 
 // This is owned by WebKitContext and is all the dom storage information that's
-// shared by all the DOMStorageMessageFilters that share the same profile.  The
+// shared by all the DOMStorageMessageFilters that share the same context.  The
 // specifics of responsibilities are fairly well documented here and in
 // StorageNamespace and StorageArea.  Everything is only to be accessed on the
 // WebKit thread unless noted otherwise.
@@ -136,7 +136,7 @@ class DOMStorageContext {
   // True if the destructor should delete its files.
   bool clear_local_state_on_exit_;
 
-  // Path where the profile data is stored.
+  // Path where the context data is stored.
   // TODO(pastarmovj): Keep in mind that unlike indexed db data_path_ variable
   // this one still has to point to the upper level dir because of the
   // MigrateLocalStorageDirectory function. Once this function disappears we can