summaryrefslogtreecommitdiff
path: root/doc/source
diff options
context:
space:
mode:
authorChunlin <fangchunlin@huawei.com>2020-04-25 23:33:48 +0800
committerGitHub <noreply@github.com>2020-04-25 10:33:48 -0500
commit6ee49178517088966e63c2aedf6a8a5779ad5384 (patch)
tree8ea96ee9757724dfb590bf359a90cd2c75196331 /doc/source
parent6d6df47fefdc503fbcffd8cb14a5daaa956ef220 (diff)
downloadnumpy-6ee49178517088966e63c2aedf6a8a5779ad5384.tar.gz
DOC: Add missing bracket (gh-16051)
Add missing closing brackets, script to generate the list in the PR gh-16051.
Diffstat (limited to 'doc/source')
-rw-r--r--doc/source/dev/index.rst2
-rw-r--r--doc/source/reference/c-api/array.rst2
-rw-r--r--doc/source/user/tutorial-svd.rst2
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/source/dev/index.rst b/doc/source/dev/index.rst
index c3f880a35..dc6099992 100644
--- a/doc/source/dev/index.rst
+++ b/doc/source/dev/index.rst
@@ -84,7 +84,7 @@ Here's the short summary, complete TOC links are below:
* Enter your GitHub username and password (repeat contributors or advanced
users can remove this step by connecting to GitHub with
- :ref:`SSH<set-up-and-configure-a-github-account>` .
+ :ref:`SSH<set-up-and-configure-a-github-account>`).
* Go to GitHub. The new branch will show up with a green Pull Request
button. Make sure the title and message are clear, concise, and self-
diff --git a/doc/source/reference/c-api/array.rst b/doc/source/reference/c-api/array.rst
index 22b15fc57..83289010b 100644
--- a/doc/source/reference/c-api/array.rst
+++ b/doc/source/reference/c-api/array.rst
@@ -3026,7 +3026,7 @@ Other conversions
.. code-block:: c
- #define error_converting(x) (((x) == -1) && PyErr_Occurred()
+ #define error_converting(x) (((x) == -1) && PyErr_Occurred())
.. c:function:: npy_intp PyArray_PyIntAsIntp(PyObject* op)
diff --git a/doc/source/user/tutorial-svd.rst b/doc/source/user/tutorial-svd.rst
index e1918f394..086e0a6de 100644
--- a/doc/source/user/tutorial-svd.rst
+++ b/doc/source/user/tutorial-svd.rst
@@ -455,7 +455,7 @@ and
:include-source: 0
should give you an image indistinguishable from the original one (although we
-may introduce floating point errors for this reconstruction. In fact,
+may introduce floating point errors for this reconstruction). In fact,
you might see a warning message saying `"Clipping input data to the
valid range for imshow with RGB data ([0..1] for floats or [0..255] for
integers)."` This is expected from the manipulation we just did on the original