Use double brackets for intra-wiki links

[wiki.git] / projects / collaboration.mdwn

diff --git a/projects/collaboration.mdwn b/projects/collaboration.mdwn
index a70ad4fb29d70e887eb5cebfcc4031e0c7f3e2c7..25e2d9069e2fcb835b51a495d34e4b6f76031ec5 100644 (file)
--- a/projects/collaboration.mdwn
+++ b/projects/collaboration.mdwn
@@ -53,7 +53,7 @@ A license without the code is worthless! Make sure your code is posted somewhere
 Code without an idea of development progress isn't worthless, but it's still not quite optimal. Again, options that SIPB projects use include
 
  * A development <a>mailing list</a> that's public or open to interested contributors on request.
- * Publicly readable <a>archives</a> of your mailing list. (Mailman lists support archiving, or you can add a Discuss archive, for example using [[Pergamon|/doc/pergamon/]].)
+ * Publicly readable <a>archives</a> of your mailing list. (Mailman lists support archiving, or you can add a Discuss archive, for example using [[Pergamon|/doc/pergamon]].)
  * <a>Trac</a>, a bug tracker and source code browser available via the scripts.mit.edu autoinstaller.
  * <a>Github</a> issues.
  * <a>Launchpad</a>, the bug tracker and source code / Debian package host that Ubuntu developed and opened to others.