summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTania Allard <taniar.allard@gmail.com>2021-05-10 13:48:24 +0100
committerTania Allard <taniar.allard@gmail.com>2021-05-10 13:48:24 +0100
commit6721946a9580c8032a45c178ae4b8730b32d6c83 (patch)
tree5cdd30a2becc6f7c9ada146e0f1f5c9960202496
parent0bd55555177160b1b953711f93f09f0a42fa7214 (diff)
downloadnumpy-6721946a9580c8032a45c178ae4b8730b32d6c83.tar.gz
DOC: Fix list indentation
-rw-r--r--doc/source/dev/development_gitpod.rst6
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/source/dev/development_gitpod.rst b/doc/source/dev/development_gitpod.rst
index 619bfba3a..147cf369c 100644
--- a/doc/source/dev/development_gitpod.rst
+++ b/doc/source/dev/development_gitpod.rst
@@ -46,10 +46,8 @@ The best way to work on NumPy as a contributor is by making a fork of the
repository first.
#. Browse to the `NumPy repository on GitHub`_ and `create your own fork`_.
-
#. Browse to your fork. Your fork will have a URL like
-#. https://github.com/melissawm/NumPy, except with your GitHub username in
-#. place of "melissawm".
+ https://github.com/melissawm/NumPy, except with your GitHub username in place of ``melissawm``.
Starting Gitpod
----------------
@@ -78,7 +76,7 @@ repository:
might be some actions running. This will ensure that you have a development
version of NumPy installed and that the docs are being pre-built for you.
-#. Once the build is complete, you can :ref:`test the build<testing-builds>` by
+#. When your workspace is ready, you can :ref:`test the build<testing-builds>` by
entering::
$ python runtests.py -v