From fa15f6f5b892c10d404bc92a4393fe220992f16a Mon Sep 17 00:00:00 2001 From: ivmarkov Date: Mon, 27 May 2024 11:10:33 +0000 Subject: [PATCH] typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e72edd3..95f7a08 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ Using `MatterStack<...>` hard-codes the following: The core of `rs-matter-stack` is `no_std` and no-`alloc`. -For production use-cases you still need to provide implementations of the following platform-specific traits: +For production use-cases you need to provide implementations of the following platform-specific traits: - `Persist` - non-volatile storage abstraction. For STD, `rs-matter-stack` provides `KvPersist` + `DirKvStore`. Easiest is to implement `KvBlobStore`, the stack will take care of the rest. - `Netif` - network interface abstraction (i.e. monitoring when the network interface is up or down, and what is its IP configuration). For IP IO, the stack uses the [`edge-nal`](https://github.com/ivmarkov/edge-net/tree/master/edge-nal) crate, and is thus compatible with [`STD`](https://github.com/ivmarkov/edge-net/tree/master/edge-nal-std) and [`Embassy`](https://github.com/ivmarkov/edge-net/tree/master/edge-nal-embassy). - `Modem` (for BLE &Wifi only) - abstraction of the device radio, that can operate either in Wifi, or in BLE mode.