deploy: 930dc9e2d3efd6d82b86c2205b80d6ccb9b4bb86
1 files changed, 3 insertions, 3 deletions
diff --git a/develop/development/git.html b/develop/development/git.html
index cd675a4207..854bb64b23 100644
--- a/develop/development/git.html
+++ b/develop/development/git.html
@@ -168,10 +168,10 @@ before. Here, by way of an arbitrary example, is the top of <code>git log --grap
<p>Note how the commit comment explains clearly what is changing and why. Also
note the <em>absence</em> of merge commits, as well as the absence of commits called
things like (to pick a few culprits):
-<a href="https://github.com/element.-hq/synapse/commit/84691da6c">“pep8”</a>, <a href="https://github.com/element.-hq/synapse/commit/474810d9d">“fix broken
+<a href="https://github.com/element-hq/synapse/commit/84691da6c">“pep8”</a>, <a href="https://github.com/element-hq/synapse/commit/474810d9d">“fix broken
test”</a>,
-<a href="https://github.com/element.-hq/synapse/commit/c9d72e457">“oops”</a>,
-<a href="https://github.com/element.-hq/synapse/commit/836358823">“typo”</a>, or <a href="https://github.com/element.-hq/synapse/commit/707374d5d">“Who's
+<a href="https://github.com/element-hq/synapse/commit/c9d72e457">“oops”</a>,
+<a href="https://github.com/element-hq/synapse/commit/836358823">“typo”</a>, or <a href="https://github.com/element-hq/synapse/commit/707374d5d">“Who's
the president?”</a>.</p>
<p>There are a number of reasons why keeping a clean commit history is a good
thing:</p>
|
