docs: improve lazy import example

[Rich-Harris]

The language added in #13993 is a little confusing:

• it's not a 'dynamic component', it's just a component
• import() isn't a function, it's a function-like expression
• the result of calling it is a module, not a component

[changeset-bot]

⚠️ No Changeset found

Latest commit: 188f0c0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

pnpm add https://pkg.pr.new/svelte@14076

commit: 188f0c0

[Conduitry]

How do we feel about {#await import('./Component.svelte') then { default: Component }}?

[Rich-Harris]

I thought about that... the only reason I didn't was that it's quite a lot to fit on one line if you're reading on mobile. But maybe that's okay? { default: Component } does have some clear advantages — pick your own name, and the syntax works on 3/4 as well as 5 (since <module.default> is an element in 3/4)

[Rich-Harris]

I changed it