MARKUP
changeset 251 2de5931b723d
parent 230 b12ab7d9c276
     1.1 --- a/MARKUP	Mon Dec 17 07:41:07 2007 +0100
     1.2 +++ b/MARKUP	Fri Oct 24 01:35:27 2008 +0200
     1.3 @@ -16,7 +16,7 @@
     1.4  
     1.5  Text of a consistent indentation level running uninterrupted by empty
     1.6  lines is combined into ''blocks''. Lines in blocks can break at any
     1.7 -position; the line breaks are not included to the result:
     1.8 +position; the line breaks are not included in the result:
     1.9  
    1.10  ---------------------------------------------------------------------
    1.11  
    1.12 @@ -153,10 +153,10 @@
    1.13   * [[@@/images/loona.png@@][http://loona.neoscientists.org/]] -
    1.14   Image link
    1.15  
    1.16 -As for external links, LOona's configuration file offers a global
    1.17 -option to decide whether external links should open in a new browser
    1.18 -window or not. (Many people disregard this feature, while businesses
    1.19 -seem to swear by it.)
    1.20 +As for external links, LOona's configuration file offers an option
    1.21 +to decide whether external links should open in a new browser window
    1.22 +or not. Many people disregard this feature, while businesses seem
    1.23 +to swear by it.
    1.24  
    1.25  
    1.26  ===( Tables )===
    1.27 @@ -174,7 +174,7 @@
    1.28  
    1.29  It is also possible to create empty cells as long as the separators
    1.30  are present. Note, by the way, that cell separators do not
    1.31 -necessarily need to be aligned exactly below each other:
    1.32 +necessarily have to be aligned exactly below each other:
    1.33  
    1.34  ---------------------------------------------------------------------
    1.35  
    1.36 @@ -204,7 +204,7 @@
    1.37  ===( Rules )===
    1.38  
    1.39  A minimum of four dashes is interpreted as a horizontal rule. Rules
    1.40 -may occur at arbitrary indentation levels, but otherwise, they must
    1.41 +may occur at arbitrary indentation levels, but otherwise they must
    1.42  occupy the whole line:
    1.43  
    1.44  ---------------------------------------------------------------------
    1.45 @@ -240,7 +240,7 @@
    1.46  ''Nodes'' translate to anchors in a document, and a browser will
    1.47  usually interprete them as jump targets. Visually, nodes translate
    1.48  to headlines also; as usual, the number of equal signs with which
    1.49 -the markup is paired determines the significance and therefore
    1.50 +the heading is paired determines the significance and therefore
    1.51  size of a headline:
    1.52  
    1.53  ---------------------------------------------------------------------
    1.54 @@ -251,9 +251,9 @@
    1.55  
    1.56  ---------------------------------------------------------------------
    1.57  
    1.58 -In addition to normal node/headlines, there are nodes which are
    1.59 -displayed as code markup. This is especially useful for jump
    1.60 -targets in a technical documentation:
    1.61 +In addition to normal node headlines, there is also a variant which
    1.62 +is marked up as code. This is especially useful for jump targets in
    1.63 +technical documentation:
    1.64  
    1.65  ---------------------------------------------------------------------
    1.66  
    1.67 @@ -264,7 +264,7 @@
    1.68  ---------------------------------------------------------------------
    1.69  
    1.70  When referencing a node, use a number sign {{#}} followed by the
    1.71 -Node name. This by the way also works for referencing nodes in
    1.72 +node name. This, by the way, also works when referencing nodes in
    1.73  other documents.
    1.74  
    1.75  For example, this link will take you to the beginning of this
    1.76 @@ -277,7 +277,7 @@
    1.77  ---------------------------------------------------------------------
    1.78  
    1.79  '''NOTE''': Don't be too adventurous when selecting a node name;
    1.80 -if you need blanks or punctuation or if in doubt, use the alternate
    1.81 +if you need blanks or punctuation or if in doubt use the alternate
    1.82  text notation.
    1.83  
    1.84  
    1.85 @@ -287,12 +287,3 @@
    1.86  elements usually leads to better readability and stylistic clarity.
    1.87  If you can't produce the looks you project, first and foremost think
    1.88  of improving your stylesheet.
    1.89 -
    1.90 -Ok, for the desperate: There's a single lone hack in LOona's markup
    1.91 -format which allows you to produce additional padding between
    1.92 -elements, list items which may appear to be empty, etc. It can come
    1.93 -to the rescue in some darned situations. It's the non-breaking space;
    1.94 -produce it either by inserting the character code 160 (see your
    1.95 -browser or operating system manuals on how to achieve this), or by
    1.96 -writing the HTML equivalent ('   '). (See the plain text
    1.97 -representation of this document, as it cannot be escaped.)