Update RELEASENOTES.md

diff --git a/RELEASENOTES.md b/RELEASENOTES.md
index 0fc5e040ad6d45da1e8bf9820f4792a439929f83..52ec8a88392d826a9c9db84dcdccae84adc444c9 100644 (file)
--- a/RELEASENOTES.md
+++ b/RELEASENOTES.md
@@ -7,7 +7,7 @@ These updates are about stability.
 
 With great help from [gibman](https://github.com/gibman) — see [#772](https://github.com/mikebrady/shairport-sync/issues/772) for the gory details — myriad issues have been identified and fixed. In particular, [gibman](https://github.com/gibman) shared an automated way of stress-testing Shairport Sync, and this has resulted in the detection of many bugs.
 
-With due apologies to Shakespeare, we have taken up arms against a sea of troubles, and by opposing we have ended them. It is hoped that the result is considerably more stable and can better withstand the, uh, slings and arrows of outrageous fortune and other hard-to-reproduce scenarios.
+An so, with due apologies to Shakespeare, we have taken up arms against a sea of troubles, and by opposing we have ended them. It is hoped that the result is considerably more stable and can better withstand the, uh, slings and arrows of outrageous fortune and other hard-to-reproduce scenarios.
 
 Here is a flavour of some of the issues addressed:
 * Replace the existing watchdog, which only offered partial coverage, with a much more robust thread-based watchdog.