Here's a quick wireframe example. This solution involves making a custom component with different states, and applying interactions to the buttons to control showing and hiding the various states (text appearing on the page).
RollOverInformation.fxp.zip 20.9 K
Sweet!...(now I sound like my daughter!) Thanks so much.
Just before you send that too me...I kinda figured I could do it with dupicating the page and then adding each text are to it's own state. Your solution seems a bit more elegant. Is there a benefit to using a custom component?
Just personal preference. I like keeping the navigation behavior separate from the content (main timeline of states/pages). The interactions on the buttons in the custom component can still control changing states/pages in the main timeline - should you add more content there.