From: Mike Brady <4265913+mikebrady@users.noreply.github.com>
Date: Mon, 23 May 2022 09:39:56 +0000 (+0100)
Subject: Update README.md
X-Git-Tag: 1.2~26
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ac62956d6a494a7d10e8e14ea0bb72500ad936c7;p=thirdparty%2Fnqptp.git

Update README.md
---

diff --git a/README.md b/README.md
index 5ec3d1d..144c81a 100644
--- a/README.md
+++ b/README.md
@@ -120,7 +120,7 @@ Please note that `nqptp` must run in `root` mode to be able to access ports 319
 
 Since `nqptp` uses ports 319 and 320, it can not coexist with any other user of those ports, such as full PTP service daemons.
 
-If you wish to use the shared mutex to ensure records are not altered while you are accessing them, you should open your side of the shared memory interface with read-write permission. Be aware that while your program has the mutex lock, it is in a "critical region" where it can halt `nqptp`, so keep any activity while you have the lock very short and very simple, e.g. copying the contents of shared memory to local memory. 
+Programmatically, if you wish to use the shared mutex to ensure records are not altered while you are accessing them, you should open your side of the shared memory interface with read-write permission. Be aware that while your program has the mutex lock, it is in a "critical region" where it can halt `nqptp`, so keep any activity while you have the lock very short and very simple, e.g. copying the contents of shared memory to local memory. 
 
 Clock records that are not updated for a period are deleted.