"up-to-date" should only use hyphens when used as compound modifier of a noun

docs/linux_faster_builds.md

 # Tips for improving build speed on Linux
 
 This list is sorted such that the largest speedup is first; see
 [Linux build instructions](linux_build_instructions.md) for context and
 [Faster Builds](common_build_tasks.md) for non-Linux-specific techniques.
 
 [TOC]
 
 ## General configuration
 
@@ skipping 76 matching lines @@
 to get to the local physical disk directory where you keep those working
 development directories, consider putting
 
     alias cd="cd -P"
 
 in your `.bashrc` so that `$PWD` or `cwd` always refers to a physical, not
 logical directory (and make sure `CCACHE_BASEDIR` also refers to a physical
 parent).
 
 If you tune ccache correctly, a second working directory that uses a branch
-tracking trunk and is up-to-date with trunk and was gclient sync'ed at about the
+tracking trunk and is up to date with trunk and was gclient sync'ed at about the
 same time should build chrome in about 1/3 the time, and the cache misses as
 reported by `ccache -s` should barely increase.
 
 This is especially useful if you use `git-new-workdir` and keep multiple local
 working directories going at once.
 
 ## Using tmpfs
 
 You can use tmpfs for the build output to reduce the amount of disk writes
 required. I.e. mount tmpfs to the output directory where the build output goes:
 
 As root:
 
     mount -t tmpfs -o size=20G,nr_inodes=40k,mode=1777 tmpfs /path/to/out
 
 *** note
 **Caveat:** You need to have enough RAM + swap to back the tmpfs. For a full
 debug build, you will need about 20 GB. Less for just building the chrome target
 or for a release build.
 ***
 
 Quick and dirty benchmark numbers on a HP Z600 (Intel core i7, 16 cores
 hyperthreaded, 12 GB RAM)
 
 *   With tmpfs:
     *   12m:20s
 *   Without tmpfs
     *   15m:40s