Rationalize WakeLock naming conventions

content/browser/web_contents/web_contents_impl.cc

Index: content/browser/web_contents/web_contents_impl.cc
diff --git a/content/browser/web_contents/web_contents_impl.cc b/content/browser/web_contents/web_contents_impl.cc
index 626c4c89bc47ec19d86e615e900ad8069517163c..23eec8df8410f48134fff564e41c8937df6049e6 100644
--- a/content/browser/web_contents/web_contents_impl.cc
+++ b/content/browser/web_contents/web_contents_impl.cc
@@ -2648,7 +2648,7 @@ device::mojom::WakeLockContext* WebContentsImpl::GetWakeLockContext() {
   return wake_lock_context_host_->GetWakeLockContext();
 }
 
-device::mojom::WakeLockService* WebContentsImpl::GetRendererWakeLock() {
+device::mojom::WakeLock* WebContentsImpl::GetRendererWakeLock() {
   // WebContents creates a long-lived connection to one WakeLockServiceImpl.

[blundell, 2017/06/05 11:48:10]

nit: update naming in this comment. It would be a good idea to do a "git grep
WakeLockService" in your local checkout and make sure there are no results :).

[juncai, 2017/06/05 18:58:25]

Done.

   // All the frames' requests will be added into the BindingSet of
   // WakeLockServiceImpl via this connection.