From ca88b70c1321c29228b7081095e463817eefb327 Mon Sep 17 00:00:00 2001 From: s-martin Date: Mon, 13 May 2024 23:29:09 +0200 Subject: [PATCH] fix formatting (#2371) --- README.md | 3 ++- components/controls/buttons-bluetooth-headphone/README.md | 6 ++++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 0398ff707..3b615efb8 100644 --- a/README.md +++ b/README.md @@ -141,7 +141,8 @@ There is a growing section of [troubleshooting](https://github.com/MiczFlor/RPi- Here is a list of equipment needed. You can find a lot second hand online (save money and the planet). The links below lead to Amazon, not at all because I want to support them, but because their PartnerNet program helps to support the Phoniebox maintenance (a little bit...). -Note: depending on individual projects, the hardware requirements vary. +> [!NOTE] +> Depending on individual projects, the hardware requirements vary. ### Raspberry Pi diff --git a/components/controls/buttons-bluetooth-headphone/README.md b/components/controls/buttons-bluetooth-headphone/README.md index c13e48f57..a9256f690 100644 --- a/components/controls/buttons-bluetooth-headphone/README.md +++ b/components/controls/buttons-bluetooth-headphone/README.md @@ -19,13 +19,15 @@ Out-of-the box support is included for the following buttons Key codes are standarized and so it should also work with your headphones. If you want to add more keys or assign a different behaviour see [Troubleshooting](#troubleshooting) -*Note:* Volume up/down is inherently supported by the bluetooth protocol. There is no need to handle these by this script. +> [!NOTE] +> Volume up/down is inherently supported by the bluetooth protocol. There is no need to handle these by this script. ## On Connect / On Disconnect If the feature [bluetooth-sink-switch](../../bluetooth-sink-switch) is enabled, the script automatically switches the audio stream to headphones / regular speakers on bluetooth connect / disconnect respectivly. Playback state (play/pause) is retained. -*Note:* On-connect actions may take up to 4 seconds - please be patient (bluetooth connection is only checked every two seconds, bluetooth stream needs to be buffered, etc...) + > [!NOTE] + > On-connect actions may take up to 4 seconds - please be patient (bluetooth connection is only checked every two seconds, bluetooth stream needs to be buffered, etc...) You can **customize** the behaviour by editing the functions