From a1e9bf56d80e5f412729b938db427a87f39e1122 Mon Sep 17 00:00:00 2001 From: Charles Harris Date: Sun, 3 Jan 2016 15:48:50 -0700 Subject: MAINT: Fix typos in 1.11.0-notes.rst and mtrand.pyx documentation. --- doc/release/1.11.0-notes.rst | 2 +- numpy/random/mtrand/mtrand.pyx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/release/1.11.0-notes.rst b/doc/release/1.11.0-notes.rst index 705ce73c1..6de10b553 100644 --- a/doc/release/1.11.0-notes.rst +++ b/doc/release/1.11.0-notes.rst @@ -99,7 +99,7 @@ New Features The specification is by precision rather than by C type. Hence, on some platforms np.int64 may be a `long` instead of `long long` even if the specified dtype is `long long` because the two may have the same - precision. The resulting type depends on which c type numpy uses for the + precision. The resulting type depends on which C type numpy uses for the given precision. The byteorder specification is also ignored, the generated arrays are always in native byte order. diff --git a/numpy/random/mtrand/mtrand.pyx b/numpy/random/mtrand/mtrand.pyx index 110b60a9b..489cc9e6e 100644 --- a/numpy/random/mtrand/mtrand.pyx +++ b/numpy/random/mtrand/mtrand.pyx @@ -1216,7 +1216,7 @@ cdef class RandomState: single value is returned. dtype : dtype, optional Desired dtype of the result. All dtypes are determined by their - name, i.e., 'int64', 'int`, etc, so byteorder is not available + name, i.e., 'int64', 'int', etc, so byteorder is not available and a specific precision may have different C types depending on the platform. The default value is 'l' (C long). -- cgit v1.2.1