summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorChristian Dywan <christian@twotoasts.de>2011-01-30 21:35:39 +0100
committerChristian Dywan <christian@twotoasts.de>2011-01-30 21:35:39 +0100
commit13a9f08622b88c814ff30cd70944ba877008ebdb (patch)
tree7f08ef621bd853d545d57331124b2b6f8ac0ad9c /HACKING
parent5933bb422b835eef288fc8cf1eb84d5faa74c1eb (diff)
downloadmidori-13a9f08622b88c814ff30cd70944ba877008ebdb.tar.gz
Correct typo 'registerS' in HACKING
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING2
1 files changed, 1 insertions, 1 deletions
diff --git a/HACKING b/HACKING
index 0b97d05c..0a184795 100644
--- a/HACKING
+++ b/HACKING
@@ -13,7 +13,7 @@ There are several ways to contribute to the project:
For translating, have a look at the file TRANSLATE.
-For helping with testing and triaging bug reports, you should registers with the bug tracker at https://bugs.launchpad.net/midori and join #midori on irc.freenode.net where a lot of problems are discussed. You can start right away by trying to reproduce bug reports and comment with your findings.
+For helping with testing and triaging bug reports, you should register with the bug tracker at https://bugs.launchpad.net/midori and join #midori on irc.freenode.net where a lot of problems are discussed. You can start right away by trying to reproduce bug reports and comment with your findings.
If you are interested in contributing code, there are a few options. You can join #midori to discuss a particular problem you would like to look into, or a feature you would want to implement. Opening a bug report or feature request if there isn't already one is the next step. To attract some attention, if you attached a patch or have questions, ask in #midori.