summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorYusuke Endoh <mame@ruby-lang.org>2020-12-24 18:03:39 +0900
committerYusuke Endoh <mame@ruby-lang.org>2020-12-24 18:03:39 +0900
commit1a74fb011d318a5afde7b233a6b8c34e7c2b8263 (patch)
treeec659aa96f2ce91433eeaccc6f13f06b9a5a2ac3 /doc
parent8664c3ddef548b53c4f5c5264cccd24ae08f174f (diff)
doc/maintainers.rdoc: typo
Diffstat (limited to 'doc')
-rw-r--r--doc/maintainers.rdoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/maintainers.rdoc b/doc/maintainers.rdoc
index f6131e0..64510b2 100644
--- a/doc/maintainers.rdoc
+++ b/doc/maintainers.rdoc
@@ -13,7 +13,7 @@ A module maintainer is responsible for a certain part of Ruby.
* They have "developer" role on the Redmine to modify issues.
* They have authority to decide the feature of their part. But they should always respect discussions on ruby-core/ruby-dev.
-A submaintainer of a module is like a maintainer. But The submaintainer does
+A submaintainer of a module is like a maintainer. But the submaintainer does
not have authority to change/add a feature on his/her part. They need consensus
on ruby-core/ruby-dev before changing/adding. Some of submaintainers have
commit right, others don't.