linux-kernel - [PATCH] Took care of some grammatical mistakes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20231127155758.33070-1-tintinm2017@gmail.com>
Date:   Mon, 27 Nov 2023 21:27:59 +0530
From:   attreyee-muk <tintinm2017@...il.com>
To:     jpoimboe@...nel.org, jikos@...nel.org, mbenes@...e.cz,
        pmladek@...e.com, joe.lawrence@...hat.com, corbet@....net
Cc:     attreyee-muk <tintinm2017@...il.com>,
        live-patching@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: [PATCH] Took care of some grammatical mistakes

Respected Maintainers, 

I have made some grammatical changes in the livepatch.rst file where I
felt that the sentence would have sounded more correct and would have become easy for
beginners to understand by reading. 
Requesting review of my proposed changes from the mainatiners. 

Thank You
Attreyee Mukherjee

Signed-off-by: attreyee-muk <tintinm2017@...il.com>
---
 Documentation/livepatch/livepatch.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/livepatch/livepatch.rst b/Documentation/livepatch/livepatch.rst
index 68e3651e8af9..a2d2317b7d6b 100644
--- a/Documentation/livepatch/livepatch.rst
+++ b/Documentation/livepatch/livepatch.rst
@@ -35,11 +35,11 @@ and livepatching:
     compiler using the '-pg' gcc option.
 
   - Livepatching typically needs to redirect the code at the very beginning
-    of the function entry before the function parameters or the stack
+    of the function entry, before the function parameters or the stack
     are in any way modified.
 
 All three approaches need to modify the existing code at runtime. Therefore
-they need to be aware of each other and not step over each other's toes.
+they need to be aware of each other and not step over each others' toes.
 Most of these problems are solved by using the dynamic ftrace framework as
 a base. A Kprobe is registered as a ftrace handler when the function entry
 is probed, see CONFIG_KPROBES_ON_FTRACE. Also an alternative function from
@@ -50,8 +50,8 @@ some limitations, see below.
 3. Consistency model
 ====================
 
-Functions are there for a reason. They take some input parameters, get or
-release locks, read, process, and even write some data in a defined way,
+Functions are there for a reason. They take some input parameters, acquire or
+release locks, read, process, write some data in a defined way, and also
 have return values. In other words, each function has a defined semantic.
 
 Many fixes do not change the semantic of the modified functions. For
-- 
2.34.1