Skip to content

Commit 0361af5

Browse files
Apply suggestions from @elwayman02 code review
Co-authored-by: Jordan Hawker <hawker.jordan@gmail.com>
1 parent 1ac44df commit 0361af5

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

guides/release/components/block-content.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -345,17 +345,17 @@ You could also want to pass some values. This is the same process as the default
345345
</div>
346346
```
347347

348-
If we hadn’t named blocks, we would certainly have to pass components as `args` to the popover. But this is much more practical!
348+
Without named blocks, we would certainly have to pass components as `args` to the popover. But this is much more practical!
349349

350-
Here’s how we would call it:
350+
Here’s how we would call our named blocks as a consumer:
351351

352352
```handlebars
353353
<Popover>
354354
<:trigger as |open|>
355355
<button type="button">Click to {{if open "close" "open"}} the popover!</button>
356356
</:trigger>
357357
<:content>
358-
This is what is showed when I'm opened!
358+
This is what is shown when I'm opened!
359359
</:content>
360360
</Popover>
361361
```
@@ -412,7 +412,7 @@ The title being optional when you create a card, you can use the `(has-block)` h
412412
</Card>
413413
```
414414

415-
As you are not using named blocks, you can simply yield the content you would like to add.
415+
As you are not using named blocks, you can simply yield the content you would like to add, which becomes the default yield block.
416416

417417

418418

0 commit comments

Comments
 (0)