From f857148337fc0541a977b442c022dda0bb92739a Mon Sep 17 00:00:00 2001 From: David Baker Date: Sun, 10 Dec 2017 23:02:53 -0700 Subject: [PATCH] Fixed typos --- text/0276-named-args.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/text/0276-named-args.md b/text/0276-named-args.md index de8744ae9a..5d44170206 100644 --- a/text/0276-named-args.md +++ b/text/0276-named-args.md @@ -89,7 +89,7 @@ Since the `{{foo}}` syntax still works on `Ember.Component` (which is the only kind of components available today) via the auto-reflection mechanism, we are not really in a rush to migrate the community (and the guides, etc) to using the new syntax. In the meantime, this could be viewed as a tool to -improve clearity in templates, similar to how the optional "explicit `this`" +improve clarity in templates, similar to how the optional "explicit `this`" syntax (`{{this.foo}}`). While we think writing `{{@foo}}` would be a best practice for new code @@ -105,7 +105,7 @@ This introduces a new piece of syntax that one would need to learn in order to understand Ember templates. This mostly affects "casual" readers (as this should be very easy for an Ember -deverloper to learn, understand and remember after encounting/learning it for +developer to learn, understand and remember after encounting/learning it for the first time). However, since these casual readers are also among those who are most acutely affected by the ambiguity, we believe this is still a net improvement over the status-quo.