Fix typos and improve readability of ruby nesting constraints.

[spoeschel]

The ruby nesting constraints as part of 10.2.34 currently are a bit hard to read, as it is a quite long list of about 30 constraints without any separation in between.

As it seems that adjacent constraints have been grouped by the ruby category that applies to the element on which it is actually specified, the list should somehow be (visually) divided when that ruby category changes. Or for example something like that (of course with correct text emphasis):

• if the computed value of tts:ruby is container
  • then the computed value of tts:ruby of all ancestor elements is none
  • then the computed value of tts:ruby of each of its child elements is not none
  • ...
• ...

Furthermore the order of the constraints needs to be fixed, as after the first constraint applying to delimiter, two further text constraints follow. So the delimiter constraints should be moved afterwards the two.

(and there is a small typo; search for "descendats")

[skynavga]

Thanks for noting the typos, which I will fix. However, as nothing is broken otherwise, that's the only change I intend to entertain.