summaryrefslogtreecommitdiff
path: root/Documentation/process/4.Coding.rst
diff options
context:
space:
mode:
authorVolodymyr Kot <volodymyr.kot.ua@gmail.com>2025-12-25 13:39:11 +0000
committerJonathan Corbet <corbet@lwn.net>2026-01-06 14:39:58 -0700
commit5ce70894f6cade9dc4d7c2a376724c0d8083ff8a (patch)
tree4be764abe6e6522ec19ca2fed2043e6844326bf5 /Documentation/process/4.Coding.rst
parent4971ca2007e3858171982c286421ac1af1d624a9 (diff)
downloadlwn-5ce70894f6cade9dc4d7c2a376724c0d8083ff8a.tar.gz
lwn-5ce70894f6cade9dc4d7c2a376724c0d8083ff8a.zip
Doc: correct spelling and wording mistakes
Fixed capitalization and punctuation in process documentation. Signed-off-by: Volodymyr Kot <volodymyr.kot.ua@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Message-ID: <20251225133911.87512-1-volodymyr.kot.ua@gmail.com>
Diffstat (limited to 'Documentation/process/4.Coding.rst')
-rw-r--r--Documentation/process/4.Coding.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/process/4.Coding.rst b/Documentation/process/4.Coding.rst
index 80bcc1cabc23..c0f57d0c4f73 100644
--- a/Documentation/process/4.Coding.rst
+++ b/Documentation/process/4.Coding.rst
@@ -160,12 +160,12 @@ irrelevant.
Locking
*******
-In May, 2006, the "Devicescape" networking stack was, with great
+In May 2006, the "Devicescape" networking stack was, with great
fanfare, released under the GPL and made available for inclusion in the
mainline kernel. This donation was welcome news; support for wireless
networking in Linux was considered substandard at best, and the Devicescape
stack offered the promise of fixing that situation. Yet, this code did not
-actually make it into the mainline until June, 2007 (2.6.22). What
+actually make it into the mainline until June 2007 (2.6.22). What
happened?
This code showed a number of signs of having been developed behind
@@ -204,7 +204,7 @@ regression in the first place.
It is often argued that a regression can be justified if it causes things
to work for more people than it creates problems for. Why not make a
change if it brings new functionality to ten systems for each one it
-breaks? The best answer to this question was expressed by Linus in July,
+breaks? The best answer to this question was expressed by Linus in July
2007:
::