From fb2c9c8e7fee1248fe489f6cc520b8703f70f2da Mon Sep 17 00:00:00 2001 From: Peter Andreas Entschev Date: Fri, 6 Nov 2020 14:02:50 -0800 Subject: NEP: Small NEP-35 wording fix --- doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst') diff --git a/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst b/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst index 907f08fb6..6d1f8bf27 100644 --- a/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst +++ b/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst @@ -120,9 +120,9 @@ conversion, ultimately raising a Now we should look at how a library like Dask could benefit from ``like=``. Before we understand that, it's important to understand a bit about Dask basics -and ensures correctness with ``__array_function__``. Note that Dask can perform -computations on different sorts of objects, like dataframes, bags and arrays, -here we will focus strictly on arrays, which are the objects we can use +and how it ensures correctness with ``__array_function__``. Note that Dask can +perform computations on different sorts of objects, like dataframes, bags and +arrays, here we will focus strictly on arrays, which are the objects we can use ``__array_function__`` with. Dask uses a graph computing model, meaning it breaks down a large problem in -- cgit v1.2.1