Remove WTF_LOG().

third_party/WebKit/Source/wtf/ScopedLogger.md

 # Debugging with ScopedLogger
 
 ## Overview
 
 ScopedLogger is a logger that shows nested calls by indenting.
 
 For example, if you were debugging a layout issue you could add a ScopedLogger
 to the top of the `LayoutBlock::layout` function:
 
 ```c++
@@ skipping 71 matching lines @@
 ## Requirements
 
 The ScopedLogger class and associated macros are defined in
 [Assertions.h](Assertions.h), which most Blink source files already include
 indirectly.  ScopedLogger can't be used outside of Blink code yet.
 
 The ScopedLogger macros work in debug builds by default.  They are compiled out
 of release builds, unless your `GYP_DEFINES` or GN args file includes one of the
 following:
 
-* `dcheck_always_on`: enables assertions and logging
-* `blink_logging_always_on`: enables logging, but not assertions
-
-(These are the same rules that govern `WTF_LOG` and other WTF logging macros.)
+* `dcheck_always_on`: enables assertions and ScopedLogger
+* `blink_logging_always_on`: enables ScopedLogger, but not assertions
 
 The macro names are cumbersome to type, but most editors can be configured to
 make this easier.  For example, you can add the following to a Sublime Text key
 binding file to make Ctrl+Alt+L insert a ScopedLogger:
 
 ```
   { "keys": ["ctrl+alt+l"], "command": "insert",
     "args": {"characters": "WTF_CREATE_SCOPED_LOGGER(logger, \"msg\");"}
   }
 ```