summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSebastian Berg <sebastian@sipsolutions.net>2020-09-01 08:55:41 -0500
committerGitHub <noreply@github.com>2020-09-01 08:55:41 -0500
commit815f3a22aafb2eb5ffb4d5650415af0bacc4aacd (patch)
tree8ec85a26f0645e62a2858e538c4a5cf97bb8901d
parent6afc44d620272a032208c774aa766a11b2ea271e (diff)
downloadnumpy-815f3a22aafb2eb5ffb4d5650415af0bacc4aacd.tar.gz
Apply suggestions from code review
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
-rw-r--r--numpy/core/_add_newdocs.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/numpy/core/_add_newdocs.py b/numpy/core/_add_newdocs.py
index a94b3193e..31fdb60b6 100644
--- a/numpy/core/_add_newdocs.py
+++ b/numpy/core/_add_newdocs.py
@@ -5497,12 +5497,12 @@ add_newdoc('numpy.core.multiarray', 'dtype', ('metadata',
The metadata field can be set using any dictionary at data-type
creation. NumPy currently has no uniform approach to propagating
- metadata; although some array operations preserve it there is no
+ metadata; although some array operations preserve it, there is no
guarantee that others will.
.. warning::
- Although used in certain projects this feature was long undocumented
+ Although used in certain projects, this feature was long undocumented
and is not well supported. Some aspects of metadata propagation
are expected to change in the future.