Skip to content

Commit 31942ad

Browse files
Fix typos and "typos" in template-tag-format.md
1 parent 8757300 commit 31942ad

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

guides/release/components/template-tag-format.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -261,7 +261,7 @@ This can be a powerful refactoring technique to break up large components into s
261261

262262
## Low-level format
263263

264-
All of template-tag format can be represented in it's pure-javascript form using `template` from either `@ember/template-compiler` or `@ember/template-compiler/runtime`.
264+
All of template-tag format can be represented in it's pure javascript form using `template` from either `@ember/template-compiler` or `@ember/template-compiler/runtime`.
265265

266266
Creating a template-only component via the runtime compiler:
267267

@@ -301,7 +301,7 @@ If in an environment with compilation, omitting the `/runtime` at the end of the
301301
Without specifying `/runtime`, there are additional restrictions required for the argument passed to `template()`:
302302
- it must be a string literal
303303

304-
With the `/runtime`, the argument passed to `template()` can be an extpression, for example:
304+
With the `/runtime`, the argument passed to `template()` can be an expression, for example:
305305
```js
306306
/* someValue could be from anywhere */
307307
export default default template(someValue);

0 commit comments

Comments
 (0)