2 of 2: Update stores.mdx (#666)

Co-authored-by: Atila Fassina <atilafassina@gmail.com>

Author: klequis

src/routes/concepts/stores.mdx

@@ -9,7 +9,8 @@ Within Solid, these stores can spawn a collection of reactive signals, each corr
 
 ## Creating a store
 
-Stores were intentionally designed to manage data structures like objects and arrays but are capable of handling other data types, such as strings and numbers.
+Stores can manage many data types, including: objects, arrays, strings, and numbers.
+
 Using JavaScript's [proxy](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) mechanism, reactivity extends beyond just the top-level objects or arrays.
 With stores, you can now target nested properties and elements within these structures to create a dynamic tree of reactive data.
 
@@ -251,7 +252,7 @@ setStore("users", store.users.length, {
 
 ### Range specification
 
-With path syntax, you can specify a range of indices to update or modify to target a subset of the elements within the array for modification.
+With path syntax, you can target a subset of elements to update or modify by specifying a range of indices.
 You can do this using an array of values:
 
 ```jsx
@@ -353,7 +354,7 @@ Other collection types, such as JavaScript [Sets](https://developer.mozilla.org/
 ### Data integration with `reconcile`
 
 When new information needs to be merged into an existing store `reconcile` can be useful.
-`reconcile` will determine the differences between new and existing data, initiating updates only when there are _changed_ values which avoids unnecessary updates.
+`reconcile` will determine the differences between new and existing data and initiate updates only when there are _changed_ values, thereby avoiding unnecessary updates.
 
 ```jsx
 const { createStore, reconcile } from "solid-js/stores"