From f26d374cde5b63c40d557d37eb790c16ca312438 Mon Sep 17 00:00:00 2001 From: Matthew Rocklin Date: Wed, 7 Aug 2019 11:05:14 -0700 Subject: [PATCH] Simplify language in API doc --- docs/source/api.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/source/api.rst b/docs/source/api.rst index 90043c60c8e..da88ac4315b 100644 --- a/docs/source/api.rst +++ b/docs/source/api.rst @@ -3,12 +3,12 @@ API Dask APIs generally follow from upstream APIs: -- The :doc:`Dask Array API ` follows the NumPy API -- The :doc:`Dask DataFrame API ` follows the Pandas API -- The `Dask-ML API `_ follows the Scikit-Learn API and other related machine learning libraries -- The :doc:`Dask Bag API ` follows the map/filter/groupby/reduce API common in PySpark, PyToolz, and the Python standard library -- The :doc:`Dask Delayed API ` wraps general Python code -- The :doc:`Real-time Futures API ` follows the `concurrent.futures `_ API from the standard library. +- :doc:`Arrays` follows NumPy +- :doc:`DataFrames ` follows Pandas +- :doc:`Bag ` follows map/filter/groupby/reduce common in Spark and Python iterators +- `Dask-ML `_ follows the Scikit-Learn and others +- :doc:`Delayed ` wraps general Python code +- :doc:`Futures ` follows `concurrent.futures `_ from the standard library for real-time computation. Additionally, Dask has its own functions to start computations, persist data in memory, check progress, and so forth that complement the APIs above.