Documentation: clean up

site/dev/testing/testing.md

 Correctness Testing
 ===================
 
 Skia correctness testing is primarily served by a tool named DM.
 This is a quickstart to building and running DM.
 
 ~~~
-$ ./gyp_skia
+$ python bin/sync-and-gyp
 $ ninja -C out/Debug dm
 $ out/Debug/dm -v -w dm_output
 ~~~
 
 When you run this, you may notice your CPU peg to 100% for a while, then taper
 off to 1 or 2 active cores as the run finishes.  This is intentional.  DM is
 very multithreaded, but some of the work, particularly GPU-backed work, is
 still forced to run on a single thread.  You can use `--threads N` to limit DM to
 N threads if you like.  This can sometimes be helpful on machines that have
 relatively more CPU available than RAM.
@@ skipping 116 matching lines @@
 That means it is possible for two different configurations to produce
 the same exact .png, but have their checksums differ.
 
 Unit tests don't generally output anything but a status update when they pass.
 If a test fails, DM will print out its assertion failures, both at the time
 they happen and then again all together after everything is done running.
 These failures are also included in the dm.json file.
 
 DM has a simple facility to compare against the results of a previous run:
 ~~~
-$ ./gyp_skia
+$ python bin/sync-and-gyp
 $ ninja -C out/Debug dm
 $ out/Debug/dm -w good
 
-   (do some work)
+  # do some work
 
-$ ./gyp_skia
+$ python bin/sync-and-gyp
 $ ninja -C out/Debug dm
 $ out/Debug/dm -r good -w bad
 ~~~
 When using `-r`, DM will display a failure for any test that didn't produce the
 same image as the `good` run.
 
 For anything fancier, I suggest using skdiff:
 ~~~
-$ ./gyp_skia
+$ python bin/sync-and-gyp
 $ ninja -C out/Debug dm
 $ out/Debug/dm -w good
 
-   (do some work)
+  # do some work
 
-$ ./gyp_skia
+$ python bin/sync-and-gyp
 $ ninja -C out/Debug dm
 $ out/Debug/dm -w bad
 
 $ ninja -C out/Debug skdiff
 $ mkdir diff
 $ out/Debug/skdiff good bad diff
 
-  (open diff/index.html in your web browser)
+  # open diff/index.html in your web browser
 ~~~
 
 That's the basics of DM.  DM supports many other modes and flags.  Here are a
 few examples you might find handy.
 ~~~
 $ out/Debug/dm --help        # Print all flags, their defaults, and a brief explanation of each.
 $ out/Debug/dm --src tests   # Run only unit tests.
 $ out/Debug/dm --nocpu       # Test only GPU-backed work.
 $ out/Debug/dm --nogpu       # Test only CPU-backed work.
 $ out/Debug/dm --match blur  # Run only work with "blur" in its name.
 $ out/Debug/dm --dryRun      # Don't really do anything, just print out what we'd do.
 ~~~