Add documentation for MemoryCoordinator-related primitives

content/public/browser/memory_coordinator.h

Index: content/public/browser/memory_coordinator.h
diff --git a/content/public/browser/memory_coordinator.h b/content/public/browser/memory_coordinator.h
index 3b7b7494eaa1f7578e46c90962f97298c1966af4..e0927d6907b30ba4651718f541c71fc6536869ec 100644
--- a/content/public/browser/memory_coordinator.h
+++ b/content/public/browser/memory_coordinator.h
@@ -14,7 +14,7 @@ namespace content {
 // The interface that represents the browser side of MemoryCoordinator.
 // MemoryCoordinator determines memory state of each process (both browser
 // and renderers) and dispatches state change notifications to its clients.
-// See comments on MemoryCoordinatorClient for details.
+// See comments on MemoryCoordinatorClient for how to use it.

[Ryan Sleevi, 2017/02/25 02:57:10]

I think this comment (line 17) should be deleted entirely.

The MemoryCoordinatorClient doesn't describe how to use the MemoryCoordinator,
it describes how to use the MCC.

For example, a logical question is whether or not I need to explicitly
initialize the MemoryCoordinator (e.g. call MemoryCoorindator::GetInstance()) to
start notifications being processed, whether that's implicit by the
MemoryCoordinatorClient, or something else.

Does that make sense? I'm not sure what's trying to be said here, but I don't
think this comment (past or present) does what it says.

 class CONTENT_EXPORT MemoryCoordinator {
  public:
   virtual ~MemoryCoordinator() {}