summaryrefslogtreecommitdiff
path: root/community/weblogs
diff options
context:
space:
mode:
authorArne Babenhauserheide <arne_bab@web.de>2012-06-01 13:31:25 +0200
committerArne Babenhauserheide <arne_bab@web.de>2012-06-01 13:31:25 +0200
commitf3efa40dd18bd9f7f6254c668d2af79d63f40ac5 (patch)
tree571fcab0dc5d9ed4b93a4b6dbcd0bc1d65c53bba /community/weblogs
parentdf8da81ffb61371b71e384bff41708896888a282 (diff)
blog-entry: missing comma
Diffstat (limited to 'community/weblogs')
-rw-r--r--community/weblogs/ArneBab/how-i-write-a-qoth.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn
index 2ba6ac9e..87b1f07d 100644
--- a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn
+++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn
@@ -17,7 +17,7 @@ Additionally I open the Arch Hurd news:
Having all those news at hand, I read every thread-starter and every news-item. For each of them I first check if I understand them (no use trying to explain something I don’t get myself) and if they provide a way for people to test what they improved (however complex that might be), then I
* note the name of the main contributor(-s),
-* write a line of text what it does (often partly copied from the news-item)
+* write a line of text what it does (often partly copied from the news-item),
* add a link to the news-item, a code-repo or a patch and
* a note how that new development helps achieve the goals_of_the_Hurd (see [[contributing/web_pages/news/writing_the_qoth]] for details).