more editing

This commit is contained in:
Tarek Ziadé 2009-12-28 00:13:16 +00:00
parent 728344dd84
commit 4b2781cc35
1 changed files with 6 additions and 6 deletions

View File

@ -128,7 +128,7 @@ the markup they use.
To support empty lines and lines with indentation with respect to
the RFC 822 format, any new line has to be suffixed by 7 spaces
followed by a pipe (`|`) char. As a result, the Description field is
followed by a pipe ("|") char. As a result, the Description field is
encoded into a folded field that can be interpreted by RFC822
parser [2]_.
@ -143,8 +143,8 @@ Example::
| 3
|
This encoding implies that any occurences of ``\n |`` have to be replaced
by ``\n`` when the field is unfolded using a RFC822 reader.
This encoding implies that any occurences of "\n |" have to be replaced
by "\n" when the field is unfolded using a RFC822 reader.
Keywords (optional)
@ -410,8 +410,8 @@ version numbers, separated by commas. Conditional operators
must be one of "<", ">", "<=", ">=", "==", "~=" and "!=".
Any number of conditional operators can be specified, e.g.
the string ``>1.0, !=1.3.4, <2.0`` is a legal version declaration.
The comma (``,``) is equivalent to the **or** operator.
the string ">1.0, !=1.3.4, <2.0" is a legal version declaration.
The comma (",") is equivalent to the **or** operator.
Each version number must be in the format specified in PEP 386.
@ -443,7 +443,7 @@ Environment markers
===================
An **environment marker** is a marker that can be added at the end of a
field after a semi-colon (';'), to add a condition about the execution
field after a semi-colon (";"), to add a condition about the execution
environment.
Here are some example of fields using such markers::