From 073ec0a7eb581fb40e925ad8487d50b2e70ad029 Mon Sep 17 00:00:00 2001
From: Naomi Black <naomiblack@users.noreply.github.com>
Date: Thu, 28 Apr 2016 19:03:54 -0700
Subject: [PATCH] chore(CHANGELOG): Fix breaking changes description

Adds more info and examples about how ngFor is affected by the change.
---
 CHANGELOG.md | 20 +++++++++++++++-----
 1 file changed, 15 insertions(+), 5 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 69319c022a..a025a4427c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -18,12 +18,22 @@
 
 ### BREAKING CHANGES
 
-* - `#...` now always means `ref-`.
-- `<template #abc>` now defines a reference to the TemplateRef, instead of an input variable used inside of the template.
-- `#...` inside of a *ngIf, … directives is deprecated.
-  Use `let …` instead.
-- `var-...` is deprecated. Replace with `let-...` for `<template>` elements and `ref-` for non `<template>` elements.
+The reference `#...` now always means `ref-`.
 
+**Before:**
+- Outside of `ngFor`, a `#...` meant a reference.
+- Inside of `ngFor`, it meant a local variable. 
+
+This was pattern was confusing.
+
+**After:**
+
+- `<template #abc>` now defines a reference to a TemplateRef, instead of an input variable used inside of the template.
+- Inside of structural directives that declare local variables, such as `*ngFor`, usage of `#...` is deprecated. Use `let` instead.
+  - `<div *ngFor="#item of items">` now becomes `<div *ngFor="let item of items">`
+- `var-...` is deprecated. 
+  - use `#` or a `ref-` outside of `*ngFor`
+  - for `ngFor`, use the syntax:  `<template ngFor let-... [ngForOf]="...">`
 
 
 <a name="2.0.0-beta.16"></a>