Update views.md

Harish Hurchurn · Harish Hurchurn · commit 72169d7552b3 · 2014-08-05T06:48:20.000+01:00
Changed wording back to original wording
diff --git a/overviews/collections/views.md b/overviews/collections/views.md
@@ -108,7 +108,7 @@ What happened here is that negate changed all elements of `subarr`, which was or
 
 After having seen all these nifty uses of views you might wonder why have strict collections at all? One reason is that performance comparisons do not always favor lazy over strict collections. For smaller collection sizes the added overhead of forming and applying closures in views is often greater than the gain from avoiding the intermediary data structures. A probably more important reason is that evaluation in views can be very confusing if the delayed operations have side effects.
 
-Here's an example which caught out a few users of versions of Scala before 2.8. In these versions the Range type was lazy, so it behaved in effect like a view. People were trying to create a number of actors like this:
+Here's an example which bit a few users of versions of Scala before 2.8. In these versions the Range type was lazy, so it behaved in effect like a view. People were trying to create a number of actors like this:
 
 
     val actors = for (i <- 1 to 10) yield actor { ... }
