From: Mike Brady <4265913+mikebrady@users.noreply.github.com>
Date: Sun, 10 May 2026 07:25:44 +0000 (+0100)
Subject: Clarify D-Bus interface usage in Shairport Sync [skip ci]
X-Git-Tag: 5.1-dev~5
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=48559c45dfe91bb00fbdd7ea3c8d2ee152e55ac8;p=thirdparty%2Fshairport-sync.git

Clarify D-Bus interface usage in Shairport Sync [skip ci]

Reorganize content for clarity regarding the D-Bus interface.
---

diff --git a/documents/D-Bus.md b/documents/D-Bus.md
index 654fea71..99c5ef3e 100644
--- a/documents/D-Bus.md
+++ b/documents/D-Bus.md
@@ -1,6 +1,8 @@
 ## Shairport Sync D-Bus Interface
 
-Shairport Sync can have a D-Bus interface, which can be used to control aspects of its operation and get status information from it. For Classic AirPlay only, remote control commands, for example `play`, `pause` and volume control, can be sent to the player.
+Shairport Sync can have a D-Bus interface, which can be used to control aspects of its operation and get status information from it.
+
+For Classic AirPlay only, remote control commands, for example `play`, `pause` and volume control, can be sent to the player.
 
 To include the D-Bus interface at build time, add the `--with-dbus-interface` flag at the `./configure…` stage. When the D-Bus interface is included in Shairport Sync, its Version String will include the term `dbus`, for instance:
 ```