The whole project spells macOS and Bluetooth one way

Two words the project was saying two ways, now settled to one each.

`macOS` is how Apple has styled it since 2016, and the repo was already split:
`connection.py`, `flash.py` and `test_disconnect.py` had it right, while the
About page and the new Summary said `MacOS`. Three files change, all of them
prose. Same five characters either way, so nothing about a rendered width moves.

`BLE` becomes `Bluetooth` in the Summary and the package docstring. Those two
lines are read by people deciding whether this runs on their machine, and
`Bluetooth` is the word they know and the word the About page already uses. The
identifier stays `BLE` everywhere it is one — the transport name, the connection
code, the config keys, the CLI. That is the boundary: the acronym is what the
thing is called in the code, the plain word is what it is called when introducing
the project to someone who has not met it yet.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

meshterm/__init__.py

@@ -1,6 +1,6 @@
 """MeshTerm is a full-featured TUI-based MeshCore client for your terminal.
 
-Supports USB, BLE and TCP companion connection. For Windows, MacOS and Linux.
+Supports USB, Bluetooth and TCP companion connection. For Windows, macOS and Linux.
 """
 
 from datetime import datetime

meshterm/assets/pages/about.md

@@ -14,7 +14,7 @@ Everything the radio overhears is recorded to a local database from the moment i
 
 The project had humble beginnings as a set of scripts in early 2026. As time passed, quality-of-life features were added, and at some point, the logical next step was to build a complete MeshCore client with all the features I felt were missing in other offerings.
 
-I wanted something I could run from my computer. I wanted it to run on Windows, MacOS, and Linux, and I wanted it to work with any MeshCore companion device, via Bluetooth, USB, or TCP. I wanted a mouseless keyboard-driven MeshCore experience. I wanted something retro-futuristic. I wanted to push the envelope of what can be done on a text terminal, while keeping system requirements low so it could run on an older computer or a lower-end System on a Chip *(SoC)*.
+I wanted something I could run from my computer. I wanted it to run on Windows, macOS, and Linux, and I wanted it to work with any MeshCore companion device, via Bluetooth, USB, or TCP. I wanted a mouseless keyboard-driven MeshCore experience. I wanted something retro-futuristic. I wanted to push the envelope of what can be done on a text terminal, while keeping system requirements low so it could run on an older computer or a lower-end System on a Chip *(SoC)*.
 
 ## Platform-specific developments
 

pyproject.toml

@@ -5,7 +5,7 @@ build-backend = "hatchling.build"
 [project]
 name = "meshterm"
 version = "0.1.0"
-description = "MeshTerm is a full-featured TUI-based MeshCore client for your terminal. Supports USB, BLE and TCP companion connection. For Windows, MacOS and Linux."
+description = "MeshTerm is a full-featured TUI-based MeshCore client for your terminal. Supports USB, Bluetooth and TCP companion connection. For Windows, macOS and Linux."
 readme = "README.md"
 requires-python = ">=3.10"
 authors = [{ name = "Jean-Pierre Martineau" }]