diff options
| author | reed <reed@pkgsrc.org> | 2007-01-24 17:41:43 +0000 |
|---|---|---|
| committer | reed <reed@pkgsrc.org> | 2007-01-24 17:41:43 +0000 |
| commit | ad0b6bd0fb39ce96436e0937fa6679712a836b16 (patch) | |
| tree | 792073f651c36b4acab24c4a32930e88afd7f27b /textproc/Markdown | |
| parent | 4b9be24196399badbfd9a92379740f344a061a04 (diff) | |
| download | pkgsrc-ad0b6bd0fb39ce96436e0937fa6679712a836b16.tar.gz | |
Fix typo (or bad copy and paste?).
Diffstat (limited to 'textproc/Markdown')
| -rw-r--r-- | textproc/Markdown/DESCR | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/textproc/Markdown/DESCR b/textproc/Markdown/DESCR index 5f295cc3e1a..f39a3fa0bf3 100644 --- a/textproc/Markdown/DESCR +++ b/textproc/Markdown/DESCR @@ -5,7 +5,7 @@ format, then convert it to structurally valid XHTML (or HTML). The overriding design goal for Markdown's formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking -like it?s been marked up with tags or formatting instructions. While +like it's been marked up with tags or formatting instructions. While Markdown's syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown's syntax is the format of plain text email. |