docs: MVUX Feedback

doc/Overview/Mvux/FeedView.md

@@ -4,7 +4,7 @@ uid: Overview.Mvux.FeedView
 
 # The `FeedView` control
 
-The `FeedView` control is the heart of MVUX on the View side and is one of the main way to consume Feeds and States within an application. The `FeedView` uses different visual states to control what is displayed on the screen depending on the state of the underlying feed, or state. 
+The `FeedView` control is one of the main ways to consume Feeds and States within an application. The `FeedView` uses different visual states to control what is displayed on the screen depending on the state of the underlying feed, or state. 
 
 ## How to use the `FeedView` control
 
@@ -55,9 +55,7 @@ In the above example, [`Data`](#data) is a property of the `FeedViewState` insta
 
 ### State
 
-The `State` property provides a `FeedViewState` which exposes the current state of the `FeedView`'s underlying data Feed wrapped in its metadata in an accessible way for the View to represent easily using the built-in or the customized templates accordingly.
-
-It's unlikely that you'll need to access the `State` property directly since the `FeedViewState` is automatically set as the `DataContext` of the various templates.  
+The `State` property returns a `FeedViewState` which exposes the current state of the `FeedView`'s underlying data Feed. It's unlikely that you'll need to access the `State` property directly since the `FeedViewState` is automatically set as the `DataContext` of the various templates.  
 
 #### The `FeedViewState` object
 

doc/Overview/Mvux/Feeds.md

@@ -14,7 +14,7 @@ Feeds include additional metadata that indicates whether the operation is still
 
 Feeds are typically used to request data from services and expose it in a stateless manner so that the resulting data can be displayed by the View.  
 
-Feeds are stateless and do not provide support for reacting upon changes the user makes to the data on the View, the data can only be reloaded and refreshed upon request which is when the underlying task or Async-Enumerable will be invoked and the data refreshed. In other words, a feed is a read-only representation of the data received from the server.
+Feeds are stateless and does not provide support for reacting to changes the user makes to the data on the View. The data can only be reloaded and refreshed upon request which is when the underlying task or Async-Enumerable will be invoked and the data refreshed. In other words, a feed is a read-only representation of the data received from the server.
 
 In contrast to feeds, [states](xref:Overview.Mvux.States) (`IState` or `IListState`), as the name suggests, are stateful and keep track of the latest value, as updates are applied.
 
@@ -115,7 +115,7 @@ public void SetUp()
 
 #### Awaiting feeds
 
-Feeds are directly awaitable, so to get the data currently held in the feed, this is useful when you want to use the current value in a command, etc. You can await it in the following manner:
+Feeds are directly awaitable, so to get the data currently held in the feed, the feed needs to be awaited. This is useful when you want to use the current value in a method, for example:
 
 ```csharp
 public IFeed<CurrentCount> CurrentCount => ...

doc/Overview/Mvux/ListStates.md

@@ -70,11 +70,6 @@ public IListFeed<string> FavoritesFeed => ...
 public IListState<string> FavoritesState => ListState.FromFeed(this, FavoritesFeed);
 ```
 
-## Others
-
-There's also the `ListState.Create` method which allows you to manually build the list-state with Messages.  
-You can learn about manual creation of Messages [here](xref:Overview.Reactive.State#create).
-
 ## Operators
 
 In the following examples, we'll refer to `MyStrings` which is an `IListState<string>`, to demonstrate how to use the various operators `IListState<T>` provides to update its state with modified data.
@@ -117,7 +112,7 @@ public async ValueTask TrimAll(CancellationToken ct = default)
 }
 ```
 
-Another overload is `UpdateAsync`, which allows you to apply an update on select item criteria, using a predicate that is checked before updating an individual update, and if an item qualifies, uses the `updater` argument, which in this case is a `Func<T, T>` which applies to an individual item:
+Another overload is `UpdateAsync`, which allows you to apply an update on items that match a criteria. The `match` predicate is checked for each item.It the item matches the criteria, the updater is invoked which returns a new instance of the item with the update applied:
 
 ```csharp
 public async ValueTask TrimLongNames(CancellationToken ct = default)
@@ -141,7 +136,7 @@ The `RemoveAllAsync` method uses a predicate to determine which items are to be
 
 ### ForEachAsync
 
-This operator can be called from an `IListState<T>` to execute an asynchronous action on all items currently in the list-state each time its data is changed (values are either added or removed):
+This operator can be called from an `IListState<T>` to execute an asynchronous action then the data changes. The action is invoked once for the entire set of data, rather than for individual items:
 
 ```csharp
 await MyStrings.ForEachAsync(async(list, ct) => await PerformAction(items, ct));