Fixed markdown links in README and README.dev

[Patched with some tweaks by tabbott]

README.dev.md

@@ -395,7 +395,8 @@ migrations and then cleanly restaring the server for you).
 Running the test suite
 ======================
 
-For more details, check out the [detailed testing
+For more details, especially on how to write tests, check out the
+[detailed testing
 docs](http://zulip.readthedocs.org/en/latest/testing.html).
 
 To run all the tests, do this:
@@ -447,4 +448,4 @@ Possible testing issues
   `do-destroy-rebuild*-database` scripts.
 
 - When building the development environment using Vagrant and the LXC provider, if you encounter permissions errors, you may need to `chown -R 1000:$(whoami) /path/to/zulip` on the host before running `vagrant up` in order to ensure that the synced directory has the correct owner during provision. This issue will arise if you run `id username` on the host where `username` is the user running Vagrant and the output is anything but 1000.
-  This seems to be caused by Vagrant behavior; more information can be found here https://github.com/fgrehm/vagrant-lxc/wiki/FAQ#help-my-shared-folders-have-the-wrong-owner
+  This seems to be caused by Vagrant behavior; more information can be found [here](https://github.com/fgrehm/vagrant-lxc/wiki/FAQ#help-my-shared-folders-have-the-wrong-owner).

README.md

@@ -46,7 +46,7 @@ guidelines](http://zulip.readthedocs.org/en/latest/code-style.html#commit-messag
 * **Testing**. The Zulip automated tests all run automatically when
 you submit a pull request, but you can also run them all in your
 development environment following the instructions in the [testing
-section](https://github.com/zulip/zulip#running-the-test-suite) below.
+docs](https://github.com/zulip/zulip/blob/master/README.dev.md#running-the-test-suite).
 
 * **Developer Documentation**.  Zulip has a growing collection of
 developer documentation on [Read The Docs](https://zulip.readthedocs.org/).