Update class comments of ServiceWorkerObjectHost

Some comments were outdated and mentioned classes which no longer
exist. Update these comments.

Bug: N/A
Change-Id: I2264e8a664d2a74f56080f8a4ccdc98d1fd0a5e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1880239
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#709345}

content/browser/service_worker/service_worker_object_host.h

@@ -28,10 +28,11 @@ namespace service_worker_object_host_unittest {
 class ServiceWorkerObjectHostTest;
 }  // namespace service_worker_object_host_unittest
 
-// Roughly corresponds to one WebServiceWorker object in the renderer process.
+// Roughly corresponds to one blink::ServiceWorker object in the renderer
+// process.
 //
-// The WebServiceWorker object in the renderer process maintains a reference to
-// |this| by owning an associated interface pointer to
+// The blink::ServiceWorker object in the renderer process maintains a
+// reference to |this| by owning a Mojo remote to
 // blink::mojom::ServiceWorkerObjectHost. When all Mojo connections bound with
 // |receivers_| are disconnected, |this| will be deleted. See also comments on
 // |receivers_|.
@@ -111,12 +112,12 @@ class CONTENT_EXPORT ServiceWorkerObjectHost
   const url::Origin provider_origin_;
   scoped_refptr<ServiceWorkerVersion> version_;
   // Typically both |receivers_| and |remote_objects_| contain only one Mojo
-  // connection, corresponding to the content::WebServiceWorkerImpl in the
-  // renderer which corresponds to the ServiceWorker JavaScript object. However,
-  // multiple Mojo connections may exist while propagating multiple service
-  // worker object infos to the renderer process, but only the first one that
-  // arrived there will be used to create the new content::WebServiceWorkerImpl
-  // instance and be bound to it.
+  // connection, corresponding to the blink::ServiceWorker in the renderer which
+  // corresponds to the ServiceWorker JavaScript object. However, multiple Mojo
+  // connections may exist while propagating multiple service worker object
+  // infos to the renderer process, but only the first one that arrived there
+  // will be used to create the new blink::ServiceWorker instance and be bound
+  // to it.
   mojo::AssociatedReceiverSet<blink::mojom::ServiceWorkerObjectHost> receivers_;
   mojo::AssociatedRemoteSet<blink::mojom::ServiceWorkerObject> remote_objects_;