summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormattip <matti.picus@gmail.com>2019-02-28 11:39:25 +0200
committermattip <matti.picus@gmail.com>2019-02-28 11:46:34 +0200
commit76099ada3cca1d815e1b32f5d0c9786e1c5e0481 (patch)
tree9a13f30deadd78d142fc0153a09a636079a47696
parent2f41bb26b061821c77aff6982630de937ad9007a (diff)
downloadnumpy-76099ada3cca1d815e1b32f5d0c9786e1c5e0481.tar.gz
DOC: fixes from review
-rw-r--r--numpy/doc/glossary.py14
1 files changed, 8 insertions, 6 deletions
diff --git a/numpy/doc/glossary.py b/numpy/doc/glossary.py
index 292f293b7..7d1c9a1d5 100644
--- a/numpy/doc/glossary.py
+++ b/numpy/doc/glossary.py
@@ -435,12 +435,14 @@ Glossary
``logical_or``.
vectorization
- Optimizing a looping block by specialized code. In a traditional send,
- vectorization operates on data with fixed strides via specialized
- hardware. Compilers know how to take advantage of well-constructed loops
- and match the data to specialized hardware that can operate on a number
- of operands in parallel. NumPy uses :ref:`vectorization
- <whatis-vectorization>` to mean any optimization via specialized code.
+ Optimizing a looping block by specialized code. In a traditional sense,
+ vectorization performs the same operation on multiple elements with
+ fixed strides between them via specialized hardware. Compilers know how
+ to take advantage of well-constructed loops to implement such
+ optimizations. NumPy uses :ref:`vectorization <whatis-vectorization>`
+ to mean any optimization via specialized code performing the same
+ operations on multiple elements, typically achieving speedups by
+ avoiding some of the overhead in looking up and converting the elements.
view
An array that does not own its data, but refers to another array's