Update RELEASENOTES.md

diff --git a/RELEASENOTES.md b/RELEASENOTES.md
index 927b7f656e27f0eef6cc0750fbf91015ab32154f..4bdfd2ea4cf961a41d0a4af5e4f34d4e9ce68b0d 100644 (file)
--- a/RELEASENOTES.md
+++ b/RELEASENOTES.md
@@ -1,8 +1,7 @@
-
 Version 3.3d21
 ====
 **Enhancements**
-* Use `/dev/urandom` rather than `/dev/random` as a source of some kind of randomness for the crtptographic nonce used in AirPlay password exchange, as `/dev/random` blocks occasionally. Please see [here](https://unix.stackexchange.com/questions/324209/when-to-use-dev-random-vs-dev-urandom) for a discussion of the merits of both. The effect of `/dev/random`'s blocking on Shairport Sync was to make the source of randomness somewhat less random. (By the way, you should never use an important password as an AirPlay password for Shairport Sync -- it is stored in Shairport Sync's configuration file in plain text.)
+* Use `/dev/urandom` rather than `/dev/random` as a source of some kind of randomness for the cryptographic "nonce" used in AirPlay password exchange, as `/dev/random` blocks occasionally. Please see [here](https://unix.stackexchange.com/questions/324209/when-to-use-dev-random-vs-dev-urandom) for a discussion of the merits of both. The effect of `/dev/random`'s blocking on Shairport Sync was to make the source of randomness somewhat less random. (By the way, you should never use an important password as an AirPlay password for Shairport Sync -- it is stored in Shairport Sync's configuration file in plain text.)
 
 Version 3.3d20
 ====