[Docs] fixes

docs/linux_debugging_ssl.md

 # Debuggin SSL on Linux
 
 To help anyone looking at the SSL code, here are a few tips I've found handy.
 
 [TOC]
 
 ## Building your own NSS
 
 In order to use a debugger with the NSS library, it helps to build NSS yourself.
 Here's how I did it:
 
 First, read
-http://www.mozilla.org/projects/security/pki/nss/nss-3.11.4/nss-3.11.4-build.html
+[Network Security Services](http://www.mozilla.org/projects/security/pki/nss/nss-3.11.4/nss-3.11.4-build.html)
 and/or
-https://developer.mozilla.org/En/NSS_reference/Building_and_installing_NSS/Build_instructions
+[Build instructions](https://developer.mozilla.org/En/NSS_reference/Building_and_installing_NSS/Build_instructions).
 
 Then, to build the most recent source tarball:
 
 ```shell
 cd $HOME
 wget ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_RTM/src/nss-3.12-with-nspr-4.7.tar.gz
 tar -xzvf nss-3.12-with-nspr-4.7.tar.gz
 cd nss-3.12/
 cd mozilla/security/nss/
 make nss_build_all
@@ skipping 104 matching lines @@
 If you get unsymbolized entries in NSS backtraces, try setting:
 
     export NSS_DISABLE_UNLOAD=1
 
 (Note that if you use the Chromium valgrind scripts like
 `tools/valgrind/chrome_tests.sh` or `tools/valgrind/valgrind.sh` these will both
 be set automatically.)
 
 ## Support forums
 
-If you have nonconfidential questions about NSS, check the newsgroup
-http://groups.google.com/group/mozilla.dev.tech.crypto The NSS maintainer
-monitors that group and gives good answers.
+If you have nonconfidential questions about NSS, check
+[the newsgroup](http://groups.google.com/group/mozilla.dev.tech.crypto).
+The NSS maintainer monitors that group and gives good answers.