summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEksperimental <eksperimental@users.noreply.github.com>2019-02-07 03:27:37 -0500
committerJosé Valim <jose.valim@gmail.com>2019-02-07 09:27:37 +0100
commitf41d8104acb5f0fc4b3c7e39c5f432f42ac0c08a (patch)
treef544a8c228e348fb18bb2163c0b040da852bbf67
parent99d919e0c881c1d346dde9273c059360fdfd2f57 (diff)
downloadelixir-f41d8104acb5f0fc4b3c7e39c5f432f42ac0c08a.tar.gz
Reword docs about Collectable.into/1 (#8775)
Be explicit that we are talking about Collectable.into/1 and Enumerable.reduce/3
-rw-r--r--lib/elixir/lib/collectable.ex6
1 files 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