Remove references to profiling::MemlogClient.

It has been renamed.

Change-Id: I201956ef9597345e21782554033b798fd14fc1c7
Reviewed-on: https://chromium-review.googlesource.com/741446Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#512548}

chrome/common/profiling/profiling_client.h

@@ -17,9 +17,9 @@ namespace profiling {
 
 class MemlogSenderPipe;
 
-// The MemlogClient listens on the interface for a StartProfiling message. On
+// The ProfilingClient listens on the interface for a StartProfiling message. On
 // receiving the message, it begins profiling the current process.
-// It is also possible to use the MemlogClient to begin profiling the current
+// It is also possible to use the ProfilingClient to begin profiling the current
 // process without connecting to the service manager interface, if the caller
 // has a |sender_pipe| to pass to StartProfiling.
 class ProfilingClient : public mojom::ProfilingClient {
@@ -27,7 +27,7 @@ class ProfilingClient : public mojom::ProfilingClient {
   ProfilingClient();
   ~ProfilingClient() override;
 
-  // mojom::MemlogClient overrides:
+  // mojom::ProfilingClient overrides:
   void StartProfiling(mojo::ScopedHandle memlog_sender_pipe) override;
   void FlushMemlogPipe(uint32_t barrier_id) override;
 

chrome/profiling/README.md

@@ -51,8 +51,8 @@ client processes to communicate memory events to the profiling process.
 
 Code Locations
 --------------
-`//chrome/common/profiling` - Logic for MemlogClient.
+`//chrome/common/profiling` - Logic for ProfilingClient.
 `//chrome/browser/profiling_host` - Logic in browser process for starting
-profiling service, and connecting MemlogClients to the profiling service.
+profiling service, and connecting ProfilingClients to the profiling service.
 `//chrome/profiling` - Profiling service.