be toward merging it rather than blocking on relatively minor edits.
Formatting Preferences
-^^^^^^^^^^^^^^^^^^^^^^
+----------------------
In general, the documentation team has focused on trying to make sure
that the instructions are comprehensible, but not being overly pedantic
* Line wrapping at something reasonable, i.e., 72–100 characters
Key terms
-^^^^^^^^^
+---------
* Functionality: something useful a project provides abstractly
* Feature: a Karaf feature that somebody could install
other terms is hard.
Common writing style mistakes
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+-----------------------------
* In per-project user documentation, you should never say *git clone*,
but should assume people have downloaded and installed the controller
project.
Grammar Preferences
-"""""""""""""""""""
+^^^^^^^^^^^^^^^^^^^
* Avoid contractions: use cannot instead of can't, it is instead of
it's, and the like.
Troubleshooting
---------------
-See `AsciiDoc Tips
-<https://wiki.opendaylight.org/view/Documentation/Tools/AsciiDoc_Tips>`_
-on the wiki for more information.
+See `AsciiDoc Tips`_ on the wiki for more information.
Common AsciiDoc mistakes
^^^^^^^^^^^^^^^^^^^^^^^^
-See also [[Documentation/Tools/AsciiDoc Tips|AsciiDoc Tips and Tricks]]
+See also `AsciiDoc Tips`_.
* Lists that get formatted incorrectly because of no blank line above
the list.
To something like::
- .. image:: images/dlux-default.png
+ .. figure:: images/dlux-default.png
A helpful regular expression for automating the replacements is
something like::
.. _Documentation Group: https://wiki.opendaylight.org/view/Documentation/
.. _RelEng/Builder: https://wiki.opendaylight.org/view/RelEng/Builder
.. _Pandoc: http://pandoc.org/
+.. _AsciiDoc Tips: https://wiki.opendaylight.org/view/Documentation/Tools/AsciiDoc_Tips