summaryrefslogtreecommitdiff
path: root/doc/source
diff options
context:
space:
mode:
authorMelissa Weber Mendonça <melissawm@gmail.com>2020-01-24 10:43:24 -0300
committerGitHub <noreply@github.com>2020-01-24 10:43:24 -0300
commitc391b32a523749aa7cd019a2888ac4ce4ab8d0dc (patch)
tree8a1be3a3df2388e312cfc40b6d06602d4f079eca /doc/source
parenta900530f03f08ec82de62fef1025140b16953bea (diff)
downloadnumpy-c391b32a523749aa7cd019a2888ac4ce4ab8d0dc.tar.gz
Update doc/source/user/tutorial-svd.rst
Co-Authored-By: Anne Bonner <35413198+bonn0062@users.noreply.github.com>
Diffstat (limited to 'doc/source')
-rw-r--r--doc/source/user/tutorial-svd.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/user/tutorial-svd.rst b/doc/source/user/tutorial-svd.rst
index 0ca1e7dfe..8291ec7e5 100644
--- a/doc/source/user/tutorial-svd.rst
+++ b/doc/source/user/tutorial-svd.rst
@@ -385,7 +385,7 @@ and
>>> plt.imshow(np.transpose(reconstructed, (1, 2, 0)))
should give you an image indistinguishable from the original one (although we
-do possibly introduce floating point errors for this reconstruction; in fact, it
+may introduce floating point errors for this reconstruction. In fact,
is possible that you 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