From 79dc40189c26db0ef637b27df7c15318f3297c8c Mon Sep 17 00:00:00 2001
From: Mike Brady <4265913+mikebrady@users.noreply.github.com>
Date: Wed, 5 Oct 2022 10:45:49 +0100
Subject: [PATCH] Update AIRPLAY2.md

---
 AIRPLAY2.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/AIRPLAY2.md b/AIRPLAY2.md
index 56675b69..ae2ef389 100644
--- a/AIRPLAY2.md
+++ b/AIRPLAY2.md
@@ -29,7 +29,7 @@ Here are some guidelines:
 * Full access, including `root` privileges, to a system at least as powerful as a Raspberry Pi 2 or a Raspberry Pi Zero 2 W.
 * Ports 319 and 320 must be free to use (i.e. they must not be in use by another service such as a PTP service) and must not be blocked by a firewall.
 * An up-to-date Linux or FreeBSD. This is important, as some of the libraries must be the latest available.
-* Shairport Sync will not run on a Mac because NQPTP, on which it relies, needs ports 319 and 320, which are already used by macOS.
+* Shairport Sync will not run in AirPlay 2 mode on a Mac because NQPTP, on which it relies, needs ports 319 and 320, which are already used by macOS.
 * A version of the [FFmpeg](https://www.ffmpeg.org) library with an AAC decoder capable of decoding Floating Planar -- `fltp` -- material. There is a guide [here](TROUBLESHOOTING.md#aac-decoder-issues-airplay-2-only) to help you find out if your system has it.
 * An audio output, for example an ALSA device (or `sndio` in FreeBSD). The device must be capable of running at 44,100 frames per second. You can use an `sps-alsa-explore`](https://github.com/mikebrady/sps-alsa-explore) to test the suitability of hardware ALSA audio devices on your device.
 Other backends continue to work as with "classic" Shairport Sync.