aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2013-09-19 17:17:43 +0200
committerMattias Andrée <maandree@operamail.com>2013-09-19 17:17:43 +0200
commit3beb599d5594b3dd56fad70943c40facd077ea9c (patch)
tree08435161712d8f43af0ea81af1794985b5a5248e
parentgrammaro (diff)
downloadusing-git-3beb599d5594b3dd56fad70943c40facd077ea9c.tar.gz
using-git-3beb599d5594b3dd56fad70943c40facd077ea9c.tar.bz2
using-git-3beb599d5594b3dd56fad70943c40facd077ea9c.tar.xz
typo
Signed-off-by: Mattias Andrée <maandree@operamail.com>
-rw-r--r--using-git.texinfo4
1 files changed, 2 insertions, 2 deletions
diff --git a/using-git.texinfo b/using-git.texinfo
index 3dab0ec..e5091ad 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -369,12 +369,12 @@ Small projects will usally have one
maintainer and contributors clone her
blessed repository and sends submissons
to her. Larger projects may have multiple
-maintainers that helps with excepting
+maintainers that helps with accepting
submissons. A common model like this,
that you often se on GitHub, is the
integeration manager workflow, where the
maintainer is an integeration manager
-than excepts pull requests from developers
+than accepts pull requests from developers
that have public repositores, often
called forks (which should not be confused
with a project fork where the forker