From f41d8104acb5f0fc4b3c7e39c5f432f42ac0c08a Mon Sep 17 00:00:00 2001 From: Eksperimental Date: Thu, 7 Feb 2019 03:27:37 -0500 Subject: Reword docs about Collectable.into/1 (#8775) Be explicit that we are talking about Collectable.into/1 and Enumerable.reduce/3 --- lib/elixir/lib/collectable.ex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/elixir/lib/collectable.ex b/lib/elixir/lib/collectable.ex index a2367e524..b0dee491c 100644 --- a/lib/elixir/lib/collectable.ex +++ b/lib/elixir/lib/collectable.ex @@ -21,9 +21,9 @@ defprotocol Collectable do shape where just the range limits are stored. The `Collectable` module was designed to fill the gap left by the - `Enumerable` protocol. `into/1` can be seen as the opposite of - `Enumerable.reduce/3`. If `Enumerable` is about taking values out, - `Collectable.into/1` is about collecting those values into a structure. + `Enumerable` protocol. `Collectable.into/1` can be seen as the opposite of + `Enumerable.reduce/3`. If the functions in `Enumerable` are about taking values out, + then `Collectable.into/1` is about collecting those values into a structure. ## Examples -- cgit v1.2.1