I think the t:saveState description starts off too technical. My opinion is that it'd be better to say what a user would use it for first.
Maybe something along the lines of: t:saveState enables you to persist beans and values longer than request scope, but shorter than session scope. It is ideal for persisting backing beans and values with the same scope as your view components. It does this by saving the target state with the component tree.
