Clarify <turbo-stream> Processing in Docs

[marcelokanzaki]

Current wording about “stream elements connected to the page dom” felt a bit vague, so this update tries to make it clearer. Open to any suggestions if it can be improved further!

[radanskoric]

Thanks for trying to clarify this. I wrote that sentence and I struggled a bit to get the right wording without losing precision. "Connected" is picked deliberately because this is how it's called in the browser lifecycle of custom elements: https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements#custom_element_lifecycle_callbacks

The nuance is that it can be added to the page in any way possible and it will execute: for example you can construct it with javascript and you can also insert it using a turbo stream action (yes, action in an action). So "connected to the page dom" is the most technically accurate description.

However, I agree it's confusing if you're not familiar with that. And, the two use cases you mention are going to be by far the most common uses.

Maybe a slightly different wording might still be equally readable while being more accurate:

Also, any `<turbo-stream>` element that's inserted into the page (e.g. through full page or frame load), will be processed ...

Wdyt?

[marcelokanzaki]

Hey @radanskoric I agree. I've updated the PR. Thank you for the explanation.