getrandom.2: Clarify sentence on getrandom() and partial GRND_RANDOM reads

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/getrandom.2 b/man2/getrandom.2
index f302508dbae6bda3afcef1a2117beb1c86c39ad7..c5fdf15cb3a50033797277873f6860ae22e4fffa 100644 (file)
--- a/man2/getrandom.2
+++ b/man2/getrandom.2
@@ -224,7 +224,7 @@ is not specified and
 .I buflen
 is less than or equal to 256,
 a return of fewer bytes than requested should never happen,
-but the careful user-space code should check for this anyway!
+but the careful programmer will check for this anyway!
 .SS Choice of random device
 Unless you are doing long-term key generation (and perhaps not even
 then), you probably shouldn't be using
@@ -235,9 +235,11 @@ are quite conservative, and so should be sufficient for all purposes.
 The disadvantage of
 .B GRND_RANDOM
 is that it can block.
-Furthermore, dealing with partially fulfilled
+Furthermore, dealing with the partially fulfilled
 .BR getrandom ()
-requests increases code complexity.
+requests that can occur when using
+.B GRND_RANDOM
+increases code complexity.
 .SS Emulating OpenBSD's getentropy()
 The
 .BR getentropy ()