summaryrefslogtreecommitdiff
path: root/Documentation/process
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2017-09-25 12:36:20 +0300
committerJonathan Corbet <corbet@lwn.net>2017-09-26 23:53:51 +0300
commitd4306db189d04886e07751f682495aeae61a4c4f (patch)
tree76d2289b06b88ff11d2353e284659d9558512565 /Documentation/process
parentd19b3e32375bd21b5d89cc484dfc56cbd9b7fee4 (diff)
downloadlinux-d4306db189d04886e07751f682495aeae61a4c4f.tar.xz
Documentation/process: phrasofix
Devils in the details are found only when the high level design is refined and gets more detailed, and the appropriate phrase to use to describe this is "problems are revealed", not "problems are reviewed". Reviews may reveal these problems, though ;-) Signed-off-by: Junio C Hamano <gitster@pobox.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/process')
-rw-r--r--Documentation/process/3.Early-stage.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/process/3.Early-stage.rst b/Documentation/process/3.Early-stage.rst
index af2c0af931d6..be00716071d4 100644
--- a/Documentation/process/3.Early-stage.rst
+++ b/Documentation/process/3.Early-stage.rst
@@ -178,7 +178,7 @@ matter is (1) kernel developers tend to be busy, (2) there is no shortage
of people with grand plans and little code (or even prospect of code) to
back them up, and (3) nobody is obligated to review or comment on ideas
posted by others. Beyond that, high-level designs often hide problems
-which are only reviewed when somebody actually tries to implement those
+which are only revealed when somebody actually tries to implement those
designs; for that reason, kernel developers would rather see the code.
If a request-for-comments posting yields little in the way of comments, do