Update 2024-06-20-community-meeting.mdx

Signed-off-by: Brooks Townsend <[email protected]>

community/2024-06-20-community-meeting.mdx

@@ -29,10 +29,6 @@ Welcome also [Matthew Cascio](https://www.linkedin.com/in/mcascio) - knows of us
 - This is a great first example in the [wasmCloud repo](https://github.com/wasmCloud/wasmCloud/pull/2217) - NATS key-value provider.
 - He is using wasmCloud and components in a couple of early projects. The attraction was that it can stretch capabilities - something that he needs and fits well in the Kubernetes space.
 - Amazed at how quickly he could get ramped up and get started with components then diving into providers - building on the great work done in the community.
-- Massoud shows us an example of the work that he has been doing. NATS Key-Value Provider - NATS Key-Value - demonstrates the power of community collaboration.
-    - wasmCloud messaging
-    - WASI KV interface
-    - Signing from REDIS
 - His provider shows the flexibility of wasmCloud and components. It’s hard to to justice to the demo in notes and so please take a look at Massoud’s demo in the recording below.
 
 **DISCUSSION: wasi-keyvalue and the purpose of buckets + stores**
@@ -41,7 +37,7 @@ Welcome also [Matthew Cascio](https://www.linkedin.com/in/mcascio) - knows of us
 - We implement in wasmCloud and in the interface itself it has a notion of a store and a bucket. So what does that mean? Brooks shows us how this works - check out the recording to see this in action.
 - When we interact with a key-value store, we will use the wasi-kv store to open a bucket and call operations on that bucket. This allows us to increment an object value.
 - When Massoud introduced us to his implementation, we decided to think about the role of a bucket in wasmCloud. When we think of the interaction from the NATS key-value perspective, NATS key-value has a notion of a store, where there are buckets that are opened individually and where we have a collection of keys and values.
-- New concept - link names - logically separate piece of configuration for relationship between a component and a provider.
+- wasmCloud concept - link names - logically separate piece of configuration for relationship between a component and a provider.
 - Link name as specified as the bucket - binding an identifier to a specific key-vaue store, defined at runtime - easier to understand and preserves vendor neutrality.
 - Link name = unique ID to specific connection between a capability and the things that consume it. A unique link name collects all the info needed to configure and connect multiple providers in the same interface. And swap in/out dynamically.
 - This a wide-ranging discussion and so we recommend diving into the recording below.