Remove incorrect information about foreach-loops (exercism#2003)

jmrunkle · web-flow · commit f7ee696b926c · 2021-09-06T13:05:10.000-07:00
diff --git a/concepts/foreach-loops/about.md b/concepts/foreach-loops/about.md
@@ -43,14 +43,3 @@ Generally a `for-each` loop is preferrable over a `for` loop for the following r
 - A `for-each` loop is more _declarative_ meaning the code is communicating _what_ it is doing, instead of _how_ it is doing it.
 - A `for-each` loop is foolproof, whereas with `for` loops it is easy to have an off-by-one error (think of using `<` versus `<=`).
 - A `for-each` loop works on all collection types, including those that do not support using an index to access elements (eg. a `Set`).
-
-To guarantee that a `for-each` loop will iterate over _all_ values, the compiler will not allow updating of a collection within a `for-each` loop.
-For example:
-
-```java
-char[] vowels = ['a', 'e', 'i', 'o', 'u'];
-
-for(char vowel: vowels) {
-    vowels = ['Y'];  // This would result in a compiler error
-}
-```
diff --git a/concepts/foreach-loops/introduction.md b/concepts/foreach-loops/introduction.md
@@ -43,14 +43,3 @@ Generally a `for-each` loop is preferrable over a `for` loop for the following r
 - A `for-each` loop is more _declarative_ meaning the code is communicating _what_ it is doing, instead of _how_ it is doing it.
 - A `for-each` loop is foolproof, whereas with `for` loops it is easy to have an off-by-one error (think of using `<` versus `<=`).
 - A `for-each` loop works on all collection types, including those that do not support using an index to access elements (eg. a `Set`).
-
-To guarantee that a `for-each` loop will iterate over _all_ values, the compiler will not allow updating of a collection within a `for-each` loop.
-For example:
-
-```java
-char[] vowels = ['a', 'e', 'i', 'o', 'u'];
-
-for(char vowel: vowels) {
-    vowels = ['Y'];  // This would result in a compiler error
-}
-```
