Language Flexibility

There are a few things that are hardcoded values that we can't do much about. For example the word "Grand Total" at the bottom of a schedule or "As Indicated" for view scale when used as part of a sheet's titleblock. The choice of words, the language used and formatting all  remain out of reach still after all these years. It would be excellent if these were added to project settings so a team could define what these should say. It's all part of refining the product itself and the documentation we produce using it.

Leaders

I know people care a lot about where leaders start on blocks of text. Some want them to start at the first line, others at the bottom line and still others at the center of the text. Personally this has always felt like fussiness, focusing on trees and missing the forest. For eleven years I spent some of my time reading drawings to either bid on a project or to try to build something with them. I never got upset about such things. I WAS frustrated when the leader didn't point at the correct thing or fell short of "something" to point at. Where the leader started never confused me as long as it was clear which note it belonged to.

For my time and money, as long as they are consistent I'm satisfied. Unfortunately Revit isn't in this regard. Text has settings for leader positioning that keynote tags don't. That can lead to inconsistency and that's not good. Any annotation features that are available for text should be extended to other elements that display information that sure looks like text when looking at a printed sheet of paper. My 2.5 cents.

Keep Readable

Text elements have a property called Keep Readable. This prevents the text from being displayed upside down and reorients rotated text elements so they are "readable" from left to right and bottom to top. As soon as text transitions past 90 degrees and then between 180 to 270 you'll find the text flips to ensure that it is easier to read. All of this is true for text in a project view.

In a family the text elements share this parameter but it doesn't matter if you check it or not because the family governs whether text remains easy to read. This setting (Keep text readable) governs all text, even nested label families, in the family setting.

If you are working in the Family Editor you only need to worry about this one setting to force all text and nested label families to behave, so to speak.