diff --git a/scribblings/lp-dev-guide.scrbl b/scribblings/lp-dev-guide.scrbl
index 8496f49..8de27bd 100644
--- a/scribblings/lp-dev-guide.scrbl
+++ b/scribblings/lp-dev-guide.scrbl
@@ -31,6 +31,6 @@ This will create a directory called @tt{leftparen} on your local machine.
 
 Right now I (Rob) soley evaluate all submitted LeftParen patches.  To keep the process running along smoothly (with high-quality patches getting into mainline LeftParen quickly), and to preserve my sanity, I require that each patch (a bug fix, a particular feature, etc) gets its own branch.  If you try to bundle a bunch of bug fixes and/or feature additions together, it's harder for me to evaluate the patch.  Small patches are less-error prone, and get through the system faster.
 
-Unless your only purpose is to submit a single patch to leftparen (and not continue on, say, future patches), you should make a separate (non-master) branch to do your work on.  This way, you can iterate on your patch, committing changes to the branch, and, when done, you can point me to the branch and I can evaluate it separate from other changes you might be working on.  Alternatively, if you did your patch on the master branch, you would essentially have to stop all other LeftParen development because I will only look at single feature/bug patches.
+Unless your only purpose is to submit a single patch to LeftParen (and not continue on, say, future patches), you should make a separate (non-master) branch to do your work on.  This way, you can iterate on your patch, committing changes to the branch, and, when done, you can point me to the branch and I can evaluate it separate from other changes you might be working on.  Alternatively, if you did your patch on the master branch, you would essentially have to stop all other LeftParen development because I will only look at single feature/bug patches.
 
 As an example of the branch and patch process, I'm going to fix a typo in this file.