README: plain declarative prose, no em dashes

Same content, fewer tells: dropped the em dashes, the bold-label bullets that
restated themselves, and the phrases that named a feeling rather than a
mechanism.

Author: AboveColin

README.md

@@ -2,40 +2,39 @@
 
 [![hacs][hacs-badge]][hacs]
 
-Home Assistant integration for **Fitdays / ICOMON smart scales** — the Robi S6 and
-the family of rebadged body-composition scales that use the Fitdays app.
+Home Assistant integration for Fitdays and ICOMON smart scales: the Robi S6 and
+the rebadged body-composition scales that use the Fitdays app.
 
-Your scale already measures fat, muscle, water, bone mass, BMR and body age. It
-computes them from bio-impedance, uploads them, and then they live only inside the
-app. This integration brings them into Home Assistant.
+Your scale computes fat, muscle, water, bone mass, BMR and body age from
+bio-impedance, uploads them, and then they stay inside the app. This integration
+reads them into Home Assistant.
 
 ## Why not Bluetooth?
 
-Every other smart-scale option in Home Assistant reads the scale over BLE, which
-means:
+The other smart-scale options in Home Assistant read the scale over BLE. That
+costs you three things.
 
-* Home Assistant has to be in Bluetooth range **at the moment you step on**, or the
-  weigh-in is simply lost.
-* You get weight, and little else — the body-composition maths happens in the
-  vendor's cloud, not on the scale.
-* No history: nothing before the day you set it up.
+Home Assistant has to be in Bluetooth range at the moment you step on, or the
+weigh-in is lost. You get weight and little else, because the body-composition
+maths runs in the vendor's cloud rather than on the scale. And you get no
+history from before the day you set it up.
 
-This integration talks to the Fitdays cloud instead, so every measurement lands in
-Home Assistant regardless of where you weighed yourself, with the full set of
-metrics and your existing history behind it.
+This integration reads the Fitdays cloud instead, so a weigh-in lands in Home
+Assistant wherever you took it, with every metric and your existing history.
 
 ## Features
 
-- **One device per person.** A Fitdays account can hold several member profiles;
-  each becomes its own Home Assistant device, so a shared scale doesn't produce one
-  ambiguous pile of sensors. Profiles added in the app later appear without a reload.
-- **Full body composition** — weight, BMI, body fat (% and kg), muscle (% and kg),
-  skeletal muscle, body water, bone mass, protein, subcutaneous and visceral fat,
-  BMR, body age, and impedance.
-- **Goal tracking** — target weight and how far you are from it.
-- **Local-history-friendly** — `last_measurement` is a proper timestamp sensor, so
-  automations can react to a new weigh-in.
-- Diagnostics + system health, English and Dutch translations.
+- One device per person. A Fitdays account can hold several member profiles, and
+  each becomes its own Home Assistant device, so a shared scale does not produce
+  one ambiguous pile of sensors. A profile added in the app appears without a
+  reload.
+- Body composition: weight, BMI, body fat in percent and kg, muscle in percent
+  and kg, skeletal muscle, body water, bone mass, protein, subcutaneous and
+  visceral fat, BMR, body age and impedance.
+- Target weight and the distance to it.
+- `last_measurement` is a timestamp sensor, so an automation can trigger on a new
+  weigh-in.
+- Diagnostics, system health, and English and Dutch translations.
 
 ## Installation
 
@@ -54,13 +53,13 @@ restart.
 
 **Settings → Devices & Services → Add Integration → Fitdays**
 
-Enter the email and password you use in the Fitdays app, plus the two-letter country
-code your account is registered in (`NL` by default).
+Enter the email and password you use in the Fitdays app, plus the two-letter
+country code your account is registered in, `NL` by default.
 
 Your password is hashed (double MD5, exactly as the app does it) before anything
-leaves Home Assistant, and only that digest is stored in the config entry — never
+leaves Home Assistant, and only that digest is stored in the config entry, never
 the plaintext. The digest is what lets the integration silently renew an expired
-session instead of nagging you to log in again.
+session without asking you to log in again.
 
 ## Entities
 
@@ -70,8 +69,8 @@ Per member profile:
 |---|---|
 | Weight | kg, with measurement context as attributes |
 | BMI | |
-| Body fat | % — and *Body fat mass* in kg |
-| Muscle | % — and *Muscle mass* in kg |
+| Body fat | %, with Body fat mass in kg as a second sensor |
+| Muscle | %, with Muscle mass in kg as a second sensor |
 | Skeletal muscle | % (mass variant disabled by default) |
 | Body water | % (mass variant disabled by default) |
 | Bone mass | kg |
@@ -80,33 +79,33 @@ Per member profile:
 | Basal metabolic rate | kcal |
 | Body age | years |
 | Last measurement | timestamp |
-| Subcutaneous fat, Heart rate, Impedance, Target weight, Weight to target, Measurements | disabled by default — enable as needed |
+| Subcutaneous fat, Heart rate, Impedance, Target weight, Weight to target, Measurements | disabled by default, enable as needed |
 
 Heart rate only reports on scales that measure it (`measures_heart_rate` on the
 device). On a scale without it the sensor stays *unknown*, not *unavailable*.
 
 ## Notes and limitations
 
-- **Cloud polling**, every 30 minutes. Scales are stepped on a couple of times a
-  day, so there is nothing to gain from polling harder.
-- Weigh-ins taken without proper skin contact come back **weight-only**, with no
+- Cloud polling every 30 minutes. A scale gets stepped on a couple of times a
+  day, so polling harder buys nothing.
+- A weigh-in taken without proper skin contact comes back weight-only, with no
   impedance and so no body composition. The body-composition sensors go to
-  *unknown* for that weigh-in rather than holding their previous value, and the
-  `weight_only` attribute on the weight sensor flags why.
-- The integration is **read-only**. It never modifies your Fitdays account.
+  unknown for that weigh-in rather than holding their previous value, and the
+  `weight_only` attribute on the weight sensor says why.
+- The integration is read-only. It never writes to your Fitdays account.
 - Brand artwork in `custom_components/fitdays/brand/` is a generic placeholder
   glyph, not the vendor's logo. Home Assistant reads that folder from 2026.3.0
   onward; on older cores the integration renders without an icon.
 
 ## Disclaimer
 
-Not affiliated with, endorsed by, or supported by GUANGDONG ICOMON or Fitdays. Built
-on [`fitdays`](https://github.com/AboveColin/fitdays), an unofficial client derived
-from the app's own traffic. Endpoints may change without notice.
+Not affiliated with or supported by GUANGDONG ICOMON or Fitdays. Built on
+[`fitdays`](https://github.com/AboveColin/fitdays), an unofficial client derived
+from the app's own traffic. The endpoints can change without notice.
 
 ## Licence
 
-MIT — see [LICENSE](LICENSE).
+MIT, see [LICENSE](LICENSE).
 
 [hacs]: https://github.com/hacs/integration
 [hacs-badge]: https://img.shields.io/badge/HACS-Custom-41BDF5.svg