From 7be37f82196f41ebab47a51d249b27aacccc9c54 Mon Sep 17 00:00:00 2001
From: Mike Brady <4265913+mikebrady@users.noreply.github.com>
Date: Fri, 24 Mar 2023 10:46:44 +0000
Subject: [PATCH] Update PulseAudioAndPipeWire.md

---
 ADVANCED TOPICS/PulseAudioAndPipeWire.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ADVANCED TOPICS/PulseAudioAndPipeWire.md b/ADVANCED TOPICS/PulseAudioAndPipeWire.md
index b6fb7335..000d6ebf 100644
--- a/ADVANCED TOPICS/PulseAudioAndPipeWire.md	
+++ b/ADVANCED TOPICS/PulseAudioAndPipeWire.md	
@@ -28,6 +28,6 @@ Per (5) above, the ALSA `"default"` device either won't exist or -- if it does e
 There are three ways to address this problem:
 1. Stop using Shairport Sync as a system service. Instead, launch it from a terminal window after log-in through the GUI.
 Alternatively, create a user service startup script so that it will be launched automatically after the user has logged in. This means that the system can not run without user intervention.
-2. If you are using the `"alsa"` backend, set the output device to a real ALSA hardware output device. Use `$ shairport-sync -h` (or, better, `sps-alsa-explore`) to get a list of output devices, and use the configuration file to set the device. Now this might prevent PulseAudio from working properly. 
+2. If you are using the `"alsa"` backend, set the output device to a real ALSA hardware output device. Use `$ shairport-sync -h` (or, better, [`sps-alsa-explore`](https://github.com/mikebrady/sps-alsa-explore)) to get a list of output devices, and use the configuration file to set the device. There is a possibility this might prevent PulseAudio from working properly. 
 # The Best Fix
 3. The best of all fixes is, if possible, to avoid using a system containing PulseAudio altogether. Linux operating systems typically have a "server", "lite" or "headless" version that has no GUI and no PulseAudio.