Adjusted wording for "return anything from void =>" to include setters

CHANGELOG.md

Index: CHANGELOG.md
diff --git a/CHANGELOG.md b/CHANGELOG.md
index ef74602033382f77601c0fa8a3d9569476fa0441..2728e6aea9cc8772e74843b91f4386fac300dad1 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,9 +4,10 @@
 * During a dynamic type check, `void` is not required to be `null` anymore.
   In practice, this makes overriding `void` functions with non-`void` functions
   safer.
-* During static analysis, a function declared using `=>` with return type `void`
-  now allows the returned expression to have any type. For example, assuming the
-  declaration `int x;`, it is now type correct to have `void f() => ++x;`.
+* During static analysis, a function or setter declared using `=>` with return
+  type `void` now allows the returned expression to have any type. For example,
+  assuming the declaration `int x;`, it is now type correct to have
+  `void f() => ++x;`.
 
 #### Strong Mode
 
@@ -21,8 +22,8 @@ Packages that implement `Future` must either type the `onValue` parameter to
 entirely to allow inference to fill in the type.
 
 * The following is also a change in strong mode: During static analysis, a
-  function declared using `=>` with return type `void` now allows the returned
-  expression to have any type.
+  function or setter declared using `=>` with return type `void` now allows the
+  returned expression to have any type.
 
 ### Core library changes