From 30d912d66e0a1adc2e9ce1e389df860b9fb5e630 Mon Sep 17 00:00:00 2001 From: Eina Safor <109956262+encarbassotnopot@users.noreply.github.com> Date: Wed, 7 Jan 2026 15:59:14 +0100 Subject: [PATCH] docs: fix a small error in hci socket up/down commands --- docs/mkdocs/src/platforms/linux.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mkdocs/src/platforms/linux.md b/docs/mkdocs/src/platforms/linux.md index 77f46f86..e0618a24 100644 --- a/docs/mkdocs/src/platforms/linux.md +++ b/docs/mkdocs/src/platforms/linux.md @@ -63,7 +63,7 @@ HCI sockets provide a way to send/receive HCI packets to/from a Bluetooth contro See the [HCI Socket Transport page](../transports/hci_socket.md) for details on the `hci-socket` tansport syntax. The HCI device referenced by an `hci-socket` transport (`hci`, where `` is an integer, with `hci0` being the first controller device, and so on) must be in the `DOWN` state before it can be opened as a transport. -You can bring a HCI controller `UP` or `DOWN` with `hciconfig hci up` and `hciconfig hci up`. +You can bring a HCI controller `UP` or `DOWN` with `hciconfig hci up` and `hciconfig hci down`. !!! tip "HCI Socket Permissions" By default, when running as a regular user, you won't have the permission to use