summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUlrich Müller <ulm@gentoo.org>2018-07-10 17:18:37 +0200
committerUlrich Müller <ulm@gentoo.org>2018-07-18 00:37:25 +0200
commit7024d42532a2b7e7d20cf03b18bc7fb471503431 (patch)
tree86c374b34576d4c2ee9d4972e8716ab4413b0c34
parentglep-0001: Small update to reflect current practice. (diff)
downloadglep-7024d42532a2b7e7d20cf03b18bc7fb471503431.tar.gz
glep-7024d42532a2b7e7d20cf03b18bc7fb471503431.tar.bz2
glep-7024d42532a2b7e7d20cf03b18bc7fb471503431.zip
glep-0001: Typo.
-rw-r--r--glep-0001.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/glep-0001.rst b/glep-0001.rst
index b3b5239..d9d8202 100644
--- a/glep-0001.rst
+++ b/glep-0001.rst
@@ -117,7 +117,7 @@ design phases, etc. GLEP authors should use their discretion here.
Once the authors have completed a GLEP, they must inform the Gentoo Council
[#COUNCIL]_ that it is ready for review by way of the appropriate mailing
-list. GLEPs are then reviewed at a Council meeting where the may be approved
+list. GLEPs are then reviewed at a Council meeting where they may be approved
or rejected outright, or sent back to the author(s) for revision. This
generally should be done a few weeks in advance of the actual review so as to
avoid the appearance of "slipping" a GLEP in without proper public review