summaryrefslogtreecommitdiff
path: root/doc/source/reference
diff options
context:
space:
mode:
authormattip <matti.picus@gmail.com>2018-10-25 20:36:31 +0300
committermattip <matti.picus@gmail.com>2018-10-25 20:36:31 +0300
commitd17edb39d43873d93a074fb9e3802e573a8b391a (patch)
treea3ea82dcc86c527ddd5d0dbe985967163271c67b /doc/source/reference
parentfc60b27257924ed7f3c140bed00c13a35b057dc8 (diff)
downloadnumpy-d17edb39d43873d93a074fb9e3802e573a8b391a.tar.gz
DOC: fixes from review
Diffstat (limited to 'doc/source/reference')
-rw-r--r--doc/source/reference/alignment.rst8
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/source/reference/alignment.rst b/doc/source/reference/alignment.rst
index f067f0d03..c749972b4 100644
--- a/doc/source/reference/alignment.rst
+++ b/doc/source/reference/alignment.rst
@@ -1,8 +1,10 @@
.. _alignment:
+Memory Alignment
+================
Numpy Alignment Goals
-=====================
+---------------------
There are three use-cases related to memory alignment in numpy (as of 1.14):
@@ -33,7 +35,7 @@ alignment of 4 and "uint" alignment of 8 (equal to the true alignment of
``uint64``).
Variables in Numpy which control and describe alignment
-=======================================================
+-------------------------------------------------------
There are 4 relevant uses of the word ``align`` used in numpy:
@@ -60,7 +62,7 @@ There are 4 relevant uses of the word ``align`` used in numpy:
an analagous way to how ``IsAligned`` checks for true-alignment.
Consequences of alignment
-=========================
+-------------------------
Here is how the variables above are used: