From 5ce70894f6cade9dc4d7c2a376724c0d8083ff8a Mon Sep 17 00:00:00 2001 From: Volodymyr Kot Date: Thu, 25 Dec 2025 13:39:11 +0000 Subject: Doc: correct spelling and wording mistakes Fixed capitalization and punctuation in process documentation. Signed-off-by: Volodymyr Kot Signed-off-by: Jonathan Corbet Message-ID: <20251225133911.87512-1-volodymyr.kot.ua@gmail.com> --- Documentation/process/4.Coding.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'Documentation/process/4.Coding.rst') 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: :: -- cgit v1.2.3