Demodocs: Cleanup, text wrapping

Author: Blendify

demo_docs/source/demo.rst

@@ -12,31 +12,24 @@ Paragraph Level Markup
 Inline Markup
 =============
 
-Paragraphs contain text and may contain inline markup: *emphasis*,
-**strong emphasis**, ``inline literals``, standalone hyperlinks
-(http://www.python.org), external hyperlinks (Python_), internal
-cross-references (example_), external hyperlinks with embedded URIs
-(`Python web site <http://www.python.org>`__), footnote references
-(manually numbered [1]_, anonymous auto-numbered [#]_, labeled
-auto-numbered [#label]_, or symbolic [*]_), citation references
-([2]_), substitution references (|example|), and _`inline hyperlink targets`
-(see Targets_ below for a reference back to here).
-Character-level inline markup is also possible (although exceedingly ugly!)
-in *re*\ ``Structured``\ *Text*.  Problems are indicated by |problematic| text
-(generated by processing errors; this one is intentional).
-
-Also with ``sphinx.ext.autodoc``, which I use in the demo,
-I can link to :class:`test_py_module.test.Foo`.
+Paragraphs contain text and may contain inline markup: *emphasis*, **strong emphasis**, ``inline literals``,
+standalone hyperlinks (http://www.python.org), external hyperlinks (Python_), internal cross-references (example_),
+external hyperlinks with embedded URIs (`Python web site <http://www.python.org>`__), footnote references
+(manually numbered [1]_, anonymous auto-numbered [#]_, labeled auto-numbered [#label]_, or symbolic [*]_),
+citation references ([2]_), substitution references (|example|), and _`inline hyperlink targets`
+(see Targets_ below for a reference back to here). Character-level inline markup is also possible
+(although exceedingly ugly!) in *re*\ ``Structured``\ *Text*. Problems are indicated by |problematic|
+text (generated by processing errors; this one is intentional).
+
+Also with ``sphinx.ext.autodoc``, which I use in the demo, I can link to :class:`test_py_module.test.Foo`.
 It will link you right my code documentation for it.
 
-The default role for interpreted text is `Title Reference`.  Here are
-some explicit interpreted text roles: a PEP reference (:PEP:`287`); an
-RFC reference (:RFC:`2822`); a :sub:`subscript`; a :sup:`superscript`;
+The default role for interpreted text is `Title Reference`.  Here are some explicit interpreted text roles:
+a PEP reference (:PEP:`287`); an RFC reference (:RFC:`2822`); a :sub:`subscript`; a :sup:`superscript`;
 and explicit roles for :emphasis:`standard` :strong:`inline` :literal:`markup`.
 
-GUI labels are a useful way to indicate that :guilabel:`Some action` is
-to be taken by the user. The GUI label should not run over
-``line-height`` so as not to :guilabel:`interfere` with text from adjacent lines.
+GUI labels are a useful way to indicate that :guilabel:`Some action` is to be taken by the user.
+The GUI label should not run over ``line-height`` so as not to :guilabel:`interfere` with text from adjacent lines.
 
 Key-bindings indicate that the read is to press a button on the keyboard or mouse,
 for example :kbd:`MMB` and :kbd:`Shift-MMB`. Another useful markup to indicate a user action