Assets docs page under-explains child bundles

[rkofman]

The following text:

Assets of similar types are grouped together into the same output bundle. If you import an asset of a different type (for example, if you imported a CSS file from JS), it starts a child bundle and leaves a reference to it in the parent. This will be illustrated in the following sections.

Could benefit from having a link (or several) in the last sentence (This will be illustrated in the following sections.). Without it, the reader is left pocking around the documentation aimlessly -- and feeling betrayed when they can't find how child bundles actually get integrated into their parents.

[rkofman]

I would suggest a specific fix, but I haven't been able to find the information myself as of yet :)

[rkofman]

Closing old issue I opened.