summaryrefslogtreecommitdiff
path: root/textproc
diff options
context:
space:
mode:
authorreed <reed>2007-01-24 17:41:43 +0000
committerreed <reed>2007-01-24 17:41:43 +0000
commitd3331f7e71d81e00625a0d4b769cff107a616a46 (patch)
tree792073f651c36b4acab24c4a32930e88afd7f27b /textproc
parentbd41aa1f6421e39c6a7594d12fc4db5ab1567e41 (diff)
downloadpkgsrc-d3331f7e71d81e00625a0d4b769cff107a616a46.tar.gz
Fix typo (or bad copy and paste?).
Diffstat (limited to 'textproc')
-rw-r--r--textproc/Markdown/DESCR2
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.