render your XHTML invalid, and must be replaced by their named entities
"&", "<", and ">".
+Keep line lengths within 108 characters so that additions or changes are easy to view in github pull requests.
+Code examples that are supposed to be all one line are an exception in which case the <pre></pre> tag should be
+used to to tell the browser to display the code as one line.
3. Custom classes
=================
so that it points to the correct URL.
-4.1 Inline markups
+4.2 Inline markups
------------------
<dfn>
entire manual in one go!).
-4.2 Lists
+4.3 Lists
---------
<ul>, <ol>
not abuse them for anything else.
-4.3 Quotations
+4.4 Quotations
--------------
<blockquote>
www.w3.org/TR/xhtml1/dtds.html">use the cite and q elements</q>.
-4.4 Keyboard/Controller interaction
+4.5 Keyboard/Controller interaction
-----------------------------------
<kbd>
class="mod1">N</kbd>. It will render as "Ctrl N" for you, and as "Cmd N" for
your Mac-using friend. Nice, huh?
-N.B.: If you want to have just the name of the modifier key by itself, use
-<kbd class="mod1>‌</kbd> (zero-width non-joiner).
+Multiple modifier keys are supported as "modNM" as well, so for Ctrl-Shift-N on Linux, you would use "mod13".
+
+N.B.: If you want to have just the name of the modifier key by itself, use the
+ modN name followed by a lower case "n", like so: <kbd class="mod1n></kbd>
For anything you want the user to type, use <kbd> as a block-level element.
See above for other <kbd> classes to denote menu items, selections, mouse
CSS Classes used with <kbd> are:
-.modN
+.modN, .modNM, .modNn, .modNMn
.mouse: mouse buttons
.cmd: a command line
.lin, .win, .mac: add nice prompts to that command line
types or presses.
-4.5 Images
+4.6 Images
----------
<img>
Images are usually placed as block-level elements, i.e. outside of a paragraph,
unless they are no higher than one row and make sense in the text flow.
+Images should also be wrapped (unless they are embedded inside a paragraph) in
+a <figure></figure> block, and should contain a <figcaption></figcaption> block
+inside as well to describe to the reader what the image is.
+
5. Other conventions
====================
* Avoid any typographical quotation marks to highlight terms or express any
kind of subtle inflection, use semantic markup instead.
-* The hyphen is used to for compound words such as this well-advised example.
+* The hyphen is used for compound words such as this well-advised example.
* Do not hyphenate words at line breaks.
* For breaks in thought—such as this splendid example—use the long
em-dash. Note that the em-dash is snugged up against the text on both