@@ -54,7 +54,7 @@ your regular Mopidy install, which you set up in the first step, is unaffected
5454by your hacking and will always be working.
5555
5656Most of us use the `virtualenvwrapper
57- <https://virtualenvwrapper.readthedocs.org /> `_ to ease working with
57+ <https://virtualenvwrapper.readthedocs.io /> `_ to ease working with
5858virtualenvs, so that's what we'll be using for the examples here. First,
5959install and setup virtualenvwrapper as described in their docs.
6060
@@ -262,14 +262,14 @@ environments using the ``-e`` option, e.g. to run just unit tests::
262262
263263 tox -e py27
264264
265- To learn more, see the `tox documentation <http ://tox.readthedocs.org / >`_ .
265+ To learn more, see the `tox documentation <https ://tox.readthedocs.io / >`_ .
266266
267267
268268Running unit tests
269269------------------
270270
271- Under the hood, ``tox -e py27 `` will use `pytest <http ://pytest.org/ >`_ as the
272- test runner. We can also use it directly to run all tests::
271+ Under the hood, ``tox -e py27 `` will use `pytest <https ://docs. pytest.org/ >`_
272+ as the test runner. We can also use it directly to run all tests::
273273
274274 pytest
275275
@@ -335,7 +335,7 @@ We're quite pedantic about :ref:`codestyle` and try hard to keep the Mopidy
335335code base a very clean and nice place to work in.
336336
337337Luckily, you can get very far by using the `flake8
338- <http://flake8.readthedocs.org /> `_ linter to check your code for issues before
338+ <http://flake8.readthedocs.io /> `_ linter to check your code for issues before
339339submitting a pull request. Mopidy passes all of flake8's checks, with only a
340340very few exceptions configured in :file: `setup.cfg `. You can either run the
341341``flake8 `` tox environment, like Travis CI will do on your pull request::
@@ -362,8 +362,8 @@ If successful, the command will not print anything at all.
362362Writing documentation
363363=====================
364364
365- To write documentation, we use `Sphinx <http://sphinx-doc.org/ >`_. See their
366- site for lots of documentation on how to use Sphinx.
365+ To write documentation, we use `Sphinx <http://www. sphinx-doc.org/ >`_. See
366+ their site for lots of documentation on how to use Sphinx.
367367
368368.. note ::
369369
@@ -509,7 +509,7 @@ For clarity, we can rename the ``origin`` remote to ``upstream``::
509509 upstream https://github.com/mopidy/mopidy.git (push)
510510
511511If you haven't already, `fork the repository
512- <https://help.github.com/articles/fork-a-repo/ > `_ to your own GitHub account.
512+ <https://help.github.com/en/ articles/fork-a-repo> `_ to your own GitHub account.
513513
514514Then, add the new fork as a remote to your local clone::
515515
@@ -553,7 +553,7 @@ When everything is done and committed, push the branch to your fork on GitHub::
553553
554554Go to the repository on GitHub where you want the change merged, in this case
555555https://github.com/mopidy/mopidy, and `create a pull request
556- <https://help.github.com/articles/creating-a-pull-request/ > `_.
556+ <https://help.github.com/en/ articles/creating-a-pull-request> `_.
557557
558558
559559Updating a pull request
0 commit comments