From e6bc0b6e521a3225a421bfce0bdcf0123e44de2b Mon Sep 17 00:00:00 2001 From: Simon Ihmig Date: Sat, 28 Oct 2017 14:28:13 +0200 Subject: [PATCH] Fix typos --- text/0000-non-context-shifting-partials.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/text/0000-non-context-shifting-partials.md b/text/0000-non-context-shifting-partials.md index ba50304f6f..7942f0dcb2 100644 --- a/text/0000-non-context-shifting-partials.md +++ b/text/0000-non-context-shifting-partials.md @@ -20,7 +20,7 @@ calling context) and deprecate the current form. {{!-- This partial will only have access to the explicitly passed `post` and `author` (via the name `contributor`) variables, but not `url`, `model` and everything else on `this` --}} - {{partial "contributor-card" post=post contirbutor=author}} + {{partial "contributor-card" post=post contributor=author}} {{/each}} {{/with}} {{/each}} @@ -166,7 +166,7 @@ Glimmer VM) with a combination of AST-transform and using Glimmer's component sy The only exception is the deprecation message. Since the actual triage for `{{foo}}` happens [deep inside the VM internals][resolve-maybe-local], we would probably have -to expose additional hooks (or other mechanisms) for Ember to issue to deprecation +to expose additional hooks (or other mechanisms) for Ember to issue the deprecation warning. [resolve-maybe-local]: https://github.com/glimmerjs/glimmer-vm/blob/f78e91b47af9195d2ab063cb24e12ae5f1e5c9be/packages/%40glimmer/opcode-compiler/lib/syntax.ts#L272 @@ -227,7 +227,7 @@ them. * Creating extra churn when adding Glimmer components - When "Glimmer components" land, the "new-style partial" functionailty will be rendered + When "Glimmer components" land, the "new-style partial" functionality will be rendered obsolete as "template-only Glimmer components" will offer a superset of its features and be just as easy to use. Presumably, when that happens, the partial feature will be phased out and removed from core. Therefore, landing this feature now might introduce