summaryrefslogtreecommitdiff
path: root/pages
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2015-03-17 16:30:59 -0700
committerelijah <elijah@riseup.net>2015-03-17 16:30:59 -0700
commite4bb118653a9d8f12077e6f961f105351390f19d (patch)
tree954380a44e4c7f508b2ed8b1a7ce8139dc250d0f /pages
parent9e6656f1ca3c0aee872e359f8683255544a7b3e7 (diff)
fix broken /docs/client links
Diffstat (limited to 'pages')
-rw-r--r--pages/docs/client/en.md11
-rw-r--r--pages/docs/client/testers-howto.md21
2 files changed, 12 insertions, 20 deletions
diff --git a/pages/docs/client/en.md b/pages/docs/client/en.md
index 15c55bf..ff7c826 100644
--- a/pages/docs/client/en.md
+++ b/pages/docs/client/en.md
@@ -2,7 +2,7 @@
@title = 'Bitmask'
@summary = "The Internet Encryption Toolkit: Encrypted Internet Proxy and Encrypted Mail"
-**Bitmask** is the multiplatform desktop client for the services offered by [the LEAP Platform](platform).
+**Bitmask** is the multiplatform desktop client for the services offered by [[the LEAP Platform => platform]]. For more information, see [[bitmask.net => https://bitmask.net]].
It is written in python using [PySide](http://qt-project.org/wiki/PySide) and licensed under the GPL3. Currently we distribute pre-compiled bundles for Linux and OSX, with Windows bundles following soon.
@@ -10,22 +10,23 @@ We include below some sections of the user guide and the development documentati
User Guide
----------
-* [Installing Bitmask](client/user-install)
-* [Running Bitmask](client/user-running)
+
+* [[Installing Bitmask => user-install]]
+* [[Running Bitmask => user-running]]
Tester Guide
------------
This part of the documentation details how to fetch the last development version and how to report bugs.
-* [Howto for testers](client/testers-howto)
+* [[HOWTO for testers => testers-howto]]
Hackers Guide
-------------
If you want to contribute to the project, we wrote this for you.
-* [Setting up a development environment](client/dev-environment)
+* [[Setting up a development environment => dev-environment]]
<!--
diff --git a/pages/docs/client/testers-howto.md b/pages/docs/client/testers-howto.md
index 9e6ff7d..e09549e 100644
--- a/pages/docs/client/testers-howto.md
+++ b/pages/docs/client/testers-howto.md
@@ -1,12 +1,5 @@
@nav_title = "Testing"
-@title = "Howto for Testers"
-
-This document covers a how-to guide to:
-
-1. Where and how report bugs for Bitmask \<reporting\_bugs\>, and
-2. Quickly fetching latest development code \<fetchinglatest\>.
-
-Let's go!
+@title = "HOWTO for Testers"
Reporting bugs
--------------
@@ -18,10 +11,8 @@ way to get it fixed quickly, and get our unconditional gratitude.
It is quick, easy, and probably the best way to contribute to Bitmask
development, other than submitting patches.
-> **Reporting better bugs**
->
-> New to bug reporting? Here you have a [great document about this noble
-> art](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html).
+**Reporting better bugs:** New to bug reporting? Here you have a
+[great document about this noble art](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html).
### Where to report bugs
@@ -80,9 +71,9 @@ web](http://webchat.freenode.net/?nick=leaper....&channels=%23leap&uio=d4).
Fetching latest development code
--------------------------------
-Normally, testing the latest client bundles \<standalone-bundle\> should
-be enough. We are engaged in a three-week release cycle with minor
-releases that are as stable as possible.
+Normally, testing the latest client bundles should be enough. We are engaged
+in a three-week release cycle with minor releases that are as stable as
+possible.
However, if you want to test that some issue has *really* been fixed
before the next release is out (if you are testing a new provider, for