Remove old-implementation references from source doc comments

4 files changed, 7 insertions, 8 deletions

diff --git a/src/config.rs b/src/config.rs
index 8288d4e..43059f9 100644
--- a/src/config.rs
+++ b/src/config.rs
@@ -1,5 +1,5 @@
-//! Validated JSON configuration, file-compatible with the TypeScript
-//! implementation (`/etc/mattertimectl/config.json`, camelCase keys).
+//! Validated JSON configuration (`/etc/mattertimectl/config.json`, camelCase
+//! keys).
 //!
 //! Unknown fields are rejected loudly via serde's `deny_unknown_fields`;
 //! device membership deliberately lives in controller storage, not here.
diff --git a/src/controller/ops.rs b/src/controller/ops.rs
index 7db1431..2a54a06 100644
--- a/src/controller/ops.rs
+++ b/src/controller/ops.rs
@@ -100,7 +100,7 @@ impl Op for CommissionOp {
         );
         let opts = CommissionOptions {
             // Consumer devices carry vendor DACs we cannot verify without the
-            // DCL; matter.js accepted these the same way.
+            // DCL, so accept them without attestation verification.
             allow_test_attestation: true,
             ..CommissionOptions::new()
         };
diff --git a/src/time.rs b/src/time.rs
index 6616194..5bdac1f 100644
--- a/src/time.rs
+++ b/src/time.rs
@@ -3,8 +3,8 @@
 //! Matter UTC time is microseconds since 2000-01-01T00:00:00Z (the "Matter
 //! epoch"), not the Unix epoch. `jiff::Timestamp` is the lingua franca
 //! everywhere else in this program; [`MatterMicros`] exists only at the wire
-//! boundary. Unlike matter.js, rs-matter passes spec values through
-//! unconverted, so no Unix-epoch API shift exists here.
+//! boundary. rs-matter passes spec values through unconverted, so no
+//! Unix-epoch API shift exists here.
 
 use std::fmt;
 
diff --git a/src/tz.rs b/src/tz.rs
index 2820c59..f48833c 100644
--- a/src/tz.rs
+++ b/src/tz.rs
@@ -2,9 +2,8 @@
 //! and offset introspection for status output.
 //!
 //! jiff exposes the real tzdb transition table, so upcoming DST changes are
-//! read directly instead of probed for (the TypeScript implementation had to
-//! binary-search ICU offsets; here `TimeZone::following` is exact by
-//! construction).
+//! read directly instead of probed for by binary-searching offsets;
+//! `TimeZone::following` is exact by construction.
 
 use jiff::Timestamp;
 use jiff::tz::TimeZone;