Thank you for the questions, I will do my best to answer them for you:
1. While User Stories and Use Cases are similar, there are some differences. A user story often takes the form of a single sentance or very small paragraph, whereas a Use Case is much more formalized. Furthermore, a Use Case generally discusses implementation details that a User Story will not go into. The following link has a pretty decent comparison of the two that I think might help you decide how you'd like to approach entering your stories into TeamPulse: http://www.stellman-greene.com/2009/05/03/requirements-101-user-stories-vs-use-cases/
2. Our upcoming Service Pack release will be including the newly released Telerik Rich Text Editor control, which will provide a much broader depth of editing capabilities than our current implementation. Printing will also be included with this, via a button in the ribbon.
3. As described a bit above, user stories don't generally imply implementation details, but this is where tasks can often be used to help provide that information. For example, if your story is "Customer details can be persisted for later retrieval", when you decompose that story into tasks you may have tasks such as "Create SQL Server database schema for Customer data" and "Develop data persistence service for customer objects". You may then further decompose those tasks into lower levels of granularity as well, if you wish.
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items