resolved comments

Signed-off-by: Ryan Winter <[email protected]>

Author: ryanwinter

articles/iot-operations/create-edge-apps/edge-apps-overview.md

@@ -55,9 +55,9 @@ MQTT subscriptions with QoS-1 ensure eventual consistency across identical appli
 
 [Shared subscriptions](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901250) enable load balancing across multiple instances of a highly available application. Instead of each subscriber receiving a copy of every message, the messages are distributed evenly among the subscribers. MQTT broker currently only supports a round robin algorithm to distribute messages allowing an application to scale out. A typical use case is to deploy multiple pods using Kubernetes ReplicaSet that all subscribe to MQTT broker using the same topic filter in shared subscription.
 
-## Distributed state store (DSS)
+## State store
 
-The Distributed state store (DSS) is a replicated in-memory *HashMap* for managing application processing state. Unlike *etcd*, for example, DSS prioritizes high-velocity throughput, horizontal scaling, and low latency through in-memory data structures, partitioning, and chain-replication. It allows applications to use the the state stores distributed nature and fault tolerance while accessing a consistent state quickly across instances. To use the built-in key-value store provided by the distributed broker:
+State store is a replicated in-memory *HashMap* for managing application processing state. Unlike *etcd*, for example, state store prioritizes high-velocity throughput, horizontal scaling, and low latency through in-memory data structures, partitioning, and chain-replication. It allows applications to use the the state stores distributed nature and fault tolerance while accessing a consistent state quickly across instances. To use the built-in key-value store provided by the distributed broker:
 
 * Implement ephemeral storage and retrieval operations using the broker's key-value store API, ensuring proper error handling and data consistency. Ephemeral state is a short-lived data storage used in stateful processing for fast access to intermediate results or metadata during real-time computations. In the context of HA application, an ephemeral state helps recover application states between crashes. It can be written to disk but remains temporary, as opposed to cold storage that's designed for long-term storage of infrequently accessed data.
 

articles/iot-operations/create-edge-apps/overview-state-store.md

@@ -1,13 +1,13 @@
 ---
 title: Persisting data in the state store
-description: Using the state store to persist data between sessions
+description: Understand how to develop application that persist data between sessions using the state store.
 author: PatAltimore
 ms.subservice: azure-mqtt-broker
 ms.author: patricka
 ms.topic: concept-article
 ms.custom:
   - ignite-2023
-ms.date: 10/22/2024
+ms.date: 11/12/2024
 
 #CustomerIntent: As an developer, I want understand how to develop application that persist data between sessions using the state store.
 ms.service: azure-iot-operations
@@ -25,10 +25,10 @@ The state store is implemented via MQTTv5. Its service is integrated directly in
 
 The state store allows an edge application to persist data on the edge. Typical uses of the state store include:
 
-1. Creating stateless applications
-1. Sharing state between applications
-1. Developing highly available applications
-1. Storing data to be used by dataflows
+* Creating stateless applications
+* Sharing state between applications
+* Developing highly available applications
+* Storing data to be used by dataflows
 
 ## State store authorization