Use the <page> tag, or use it correctly.
Matt Pagan

Matt Pagan commited on 2014-05-13 02:03:48
Zeige 2 geänderte Dateien mit 3 Einfügungen und 3 Löschungen.

... ...
@@ -1607,7 +1607,7 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
1607 1607
     (sha256sums.txt)?</a></h3>
1608 1608
 
1609 1609
     <p>Instructions are on the <a 
1610
-    href="<page docs/verifying-signatures#BuildVerification>">verifying 
1610
+    href="<page docs/verifying-signatures>#BuildVerification">verifying 
1611 1611
     signatures</a> page.</p>
1612 1612
 
1613 1613
     <hr>
... ...
@@ -201,7 +201,7 @@
201 201
     <ul>
202 202
       <li>Download the Tor Browser package, the sha256sums.txt file, and the
203 203
       sha256sums signature files. They can all be found in the same directory 
204
-      under <a href="https://www.torproject.org/dist/torbrowser/">
204
+      under <a href="<page dist/torbrowser>">
205 205
       https://www.torproject.org/dist/torbrowser/</a>, for example in '3.5' 
206 206
       for TBB 3.5.</li>
207 207
       <li>Retrieve the signers' GPG keys. This can be done from the command 
... ...
@@ -209,7 +209,7 @@
209 209
       <pre>gpg --keyserver keys.mozilla.org --recv-keys 0x29846B3C683686CC</pre>
210 210
       (This will bring you developer Mike Perry's public key. Other 
211 211
       developers' key IDs can be found on
212
-      <a href="https://www.torproject.org/docs/signing-keys.html.en">this 
212
+      <a href="<page docs/signing-keys>">this 
213 213
       page</a>.)</li>
214 214
       <li>Verify the sha256sums.txt file by executing this command:
215 215
       <pre>gpg --verify &lt;NAME OF THE SIGNATURE FILE&gt;.asc sha256sums.txt</pre></li>
216 216