Address Martin’s comments

Author: szeiger

blog/_posts/2017-02-25-collections-rework.md

@@ -108,8 +108,9 @@ While `BitSet` is a rather esoteric collection type, the same principle of impli
 - All `Map` types: `T <:< (_, _)` ("must be a Tuple2")
 - All sorted collections (like `TreeSet`): `Ordering[T]` ("must have an Ordering")
 - String (not a collection type per se but it gets many collection methods as extension methods): `T <:< Char` ("must be a Char")
+- Array (same situation as String): `ClassTag[T]` ("must have a ClassTag")
 
-This covers most uses of `CanBuildFrom` in a much simpler way. The most important use cases that cannot be supported by the new design are `collection.breakOut` (for building a different collection type directly without an extra conversion step) and `to` (for converting to a different collection type for which a `CanBuildFrom` is available).
+This covers most uses of `CanBuildFrom` in a much simpler way. The most important use cases that cannot be supported directly by the new design are `collection.breakOut` (for building a different collection type directly without an extra conversion step) and `to` (for converting to a different collection type for which a `CanBuildFrom` is available). The new design provides alternative ways to achieve the same effects.
 
 ## FromIterable