typo

README.md

@@ -27,7 +27,7 @@ Using `MatterStack<...>` hard-codes the following:
 The core of `rs-matter-stack` is `no_std` and no-`alloc`.
 
 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.
+- `Persist` - non-volatile storage abstraction. Easiest is to implement `KvBlobStore`, and then use it with the provided `KvPersist` utility. For STD, `rs-matter-stack` provides `DirKvBlobStore`.
 - `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.
 

src/persist.rs

@@ -253,10 +253,10 @@ where
 
 /// An implementation of the `KvBlobStore` trait that stores the BLOBs in a directory.
 #[cfg(feature = "std")]
-pub struct DirKvStore(std::path::PathBuf);
+pub struct DirKvBlobStore(std::path::PathBuf);
 
 #[cfg(feature = "std")]
-impl DirKvStore {
+impl DirKvBlobStore {
     /// Create a new `DirKvStore` instance.
     pub const fn new(path: std::path::PathBuf) -> Self {
         Self(path)
@@ -335,7 +335,7 @@ impl DirKvStore {
 }
 
 #[cfg(feature = "std")]
-impl KvBlobStore for DirKvStore {
+impl KvBlobStore for DirKvBlobStore {
     async fn load<'a>(&mut self, key: &str, buf: &'a mut [u8]) -> Result<Option<&'a [u8]>, Error> {
         DirKvStore::load(self, key, buf)
     }