I guess non-READMEs don't need the master part.

diff --git a/workflow.markdown b/workflow.markdown
index 4668562393c5656e469f7d8e41e6d01deb114507..fe9496053adaafef6f951199d3d932e747e2778f 100644 (file)
--- a/workflow.markdown
+++ b/workflow.markdown
@@ -45,8 +45,8 @@ When candidate_1.1 is released, we checkout stable, `git merge --no-ff candidate
 \r
 Note that the [update-stable][1] hook enforces this first-parent movement of stable and the [update-ensure-follows][2] enforces topic branches merge in the new release at their earliest possible convenience (i.e. before being able to push again).\r
 \r
-[1]: master/server/update-stable\r
-[2]: master/server/update-ensure-follows\r
+[1]: server/update-stable\r
+[2]: server/update-ensure-follows\r
 \r
 candidates\r
 ==========\r
@@ -73,5 +73,5 @@ Rebasing:
 * Is great for local commits to avoid same-branch merges (where a dev has a local, unshared commit and then creates a useless merge of it into the same branch that has since moved on)\r
 * Is a PITA unless you use the [pull][3] scripts\r
 \r
-[3]: master/scripts/pull\r
+[3]: scripts/pull\r
 \r