Remove pointless TODO comments someone added.

docs/updating_clang_format_binaries.md

 # Updating Clang format binaries
 
 Instructions on how to update the [clang-format binaries](clang_format.md) that
 come with a checkout of Chromium.
 
 ## Prerequisites
 
 You'll need a Windows machine, a Linux machine, and a Mac; all capable of
 building clang-format. You'll also need permissions to upload to the appropriate
 google storage bucket. Chromium infrastructure team members have this, and
@@ skipping 58 matching lines @@
     -DLLVM_ENABLE_ASSERTIONS=NO -DLLVM_ENABLE_THREADS=NO ../llvm/
 time caffeinate ninja clang-format
 strip bin/clang-format
 
 # (On Linux, to build with clang, which produces smaller binaries, add this to
 # your cmake invocation.
 # On Mac, the system compiler is already clang so it's not needed there.)
 -DCMAKE_C_COMPILER=$PWD/../chrome/src/third_party/llvm-build/Release+Asserts/bin/clang -DCMAKE_CXX_COMPILER=$PWD/../chrome/src/third_party/llvm-build/Release+Asserts/bin/clang++
 ```
 
-TODO: these ^^ instructions looks odd. Are they correct???
-
 Platform specific notes:
 
 *   Windows: Visual Studio 2013 only.
 *   Linux: so far (as of January 2014) we've just included a 64-bit binary. It's
     important to disable threading, else clang-format will depend on
     libatomic.so.1 which doesn't exist on Precise.
 *   Mac: Remember to set `MACOSX_DEPLOYMENT_TARGET` when building! If you get
     configure warnings, you may need to install XCode 5 and avoid a goma
     environment.
 
@@ skipping 26 matching lines @@
     The binaries were built at clang revision ####### on ####DATETIME####.
 
     BUG=
 
 The change should **always** include new `.sha1` files for each platform (we
 want to keep these in lockstep), should **never** include `clang-format`
 binaries directly. The change should **always** update `README.chromium`
 
 clang-format binaries should weigh in at 1.5MB or less. Watch out for size
 regressions.