Build chains & triggers (requesting clarification on documentation)

In your documentation, you state "If you have a build chain (i.e. a number of builds interconnected by snapshot dependencies),  the triggers are to be configured in the resulting build, the top-most build. When this build is triggered, all its snapshot dependencies are triggered too."  This is ambiguous as I would consider the "resulting build" to be at the end of the build chain, not at the top, so I have no idea what this is trying to tell me.

I have a chain that looks like this:

 A -> B -> C -> F

          |               ^

          v              |

          D    ->     E

Which would you consider to be the "top-most build"?  Which would you consider to be the "resulting build"?  From the doc, I would think they would be the same but, in my case, I would consider A to be the "top-most build" and F to be the "resulting build".  Adding a picture to the documentation would clarify this, in addition to fixing the ambiguous language.

I have VCS triggers set on B, C, D, E & F. that trigger a build on changes in snapshot dependencies.

I have a VCS trigger set on A that triggers a build on each check-in.  Is this the correct way to set this up?  Or should this be E instead.

When a check-in is done, two builds are triggered for each of A..E but then the build queue is usually cleaned up a few seconds later and only the 5 (A..E) remain.  However, occasionally, all 10 seem to persist.  Any idea what the problem is?

Thanks in advance.

--Karen

PS: Found the edit option but the gear icon is not intuitive.  Usually means settings.