[Style] Vincent's suggestions

collects/scribblings/style/branch-and-commit.scrbl

@@ -48,8 +48,8 @@ On occasion, you will find that you are spending a significant amount of
  you will not know for a long time whether the performance implication
  allow a commit to the PLT repository.
 
-@margin-note*{See @hyperlink["http://tmp.barzilay.org/git.txt"]{Eli's
- write-up} on using git in PLT for details.}
+@margin-note*{See @hyperlink["http://tmp.barzilay.org/git.txt"]{Eli
+ Barzilay's write-up} on using git in PLT for details.}
 As a reminder, here are the essential elements of git for working on a
 fork:
 @itemlist[

collects/scribblings/style/testing.scrbl

@@ -31,7 +31,10 @@ After you commit, watch for and read(!)
  succeed now, and the latter is for tests that are currently expected to
  fail. See the
  @hyperlink["https://github.com/plt/racket/tree/master/collects/tests/typed-scheme"]{Typed
- Racket testing arrangement} for an example.
+ Racket testing arrangement} for an example. When you create such
+ @tt{failure} tests, you may to disable DrDr's checking like this:
+@nested{@tt{git prop set drdr:command-line "" <file> ...}}
+ This is a Racket-specific @tt{git} command.
 
 @; -----------------------------------------------------------------------------
 @section[#:tag "test-bang"]{Always Test!}