From f1d156219ea154a469d6d2b0d0cc4883c53ceba9 Mon Sep 17 00:00:00 2001 From: Peter Andreas Entschev Date: Wed, 19 Aug 2020 18:56:35 +0200 Subject: Update doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst Co-authored-by: Eric Wieser --- doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (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 c1edfa750..e31f975e7 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 @@ -124,7 +124,7 @@ 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 -many smaller problems and merge their results to reach the final result. To +many smaller problems and merges their results to reach the final result. To break the problem down into smaller ones, Dask also breaks arrays into smaller arrays, that it calls "chunks". A Dask array can thus consist of one or more chunks and they may be of different types. However, in the context of -- cgit v1.2.1