Merge branch 'v1.11' into issue_1200

daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md

@@ -1,13 +1,13 @@
 ---
 type: docs
-title: "In Memory"
-linkTitle: "In Memory"
+title: "In-memory"
+linkTitle: "In-memory"
 description: "Detailed documentation on the In Memory pubsub component"
 aliases:
   - "/operations/components/setup-pubsub/supported-pubsub/setup-inmemory/"
 ---
 
-The In Memory pub/sub component is useful for development purposes and works inside of a single machine boundary.
+The in-memory pub/sub component operates within a single Dapr sidecar. This is primarily meant for development purposes. State is not replicated across multiple sidecars and is lost when the Dapr sidecar is restarted.
 
 ## Component format
 
@@ -25,6 +25,7 @@ spec:
 > Note: in-memory does not require any specific metadata for the component to work, however spec.metadata is a required field.
 
 ## Related links
+
 - [Basic schema for a Dapr component]({{< ref component-schema >}}) in the Related links section
 - Read [this guide]({{< ref "howto-publish-subscribe.md#step-2-publish-a-topic" >}}) for instructions on configuring pub/sub components
 - [Pub/Sub building block]({{< ref pubsub >}})

daprdocs/content/en/reference/components-reference/supported-state-stores/setup-inmemory.md

@@ -1,20 +1,16 @@
 ---
 type: docs
-title: "In Memory"
-linkTitle: "In Memory"
-description: "Detailed documentation on the In Memory state component"
+title: "In-memory"
+linkTitle: "In-memory"
+description: "Detailed documentation on the in-memory state component"
 aliases:
   - "/operations/components/setup-state-store/supported-state-stores/setup-inmemory/"
 ---
 
-The In Memory state store component is useful for development purposes and works inside of a single machine boundary.
-
-{{% alert title="Warning" color="warning" %}}
- This component **shouldn't be used for production**. It is developer only and will never be stable. If you come across a scenario and want to use it in production, you can submit an issue and discuss it with the community.
-
-{{% /alert %}}
+The in-memory state store component maintains state in the Dapr sidecar's memory. This is primarily meant for development purposes. State is not replicated across multiple sidecars and is lost when the Dapr sidecar is restarted.
 
 ## Component format
+
 To setup in-memory state store, create a component of type `state.in-memory`. See [this guide]({{< ref "howto-get-save-state.md#step-1-setup-a-state-store" >}}) on how to create and apply a state store configuration.
 
 ```yaml
@@ -31,6 +27,7 @@ spec:
 > Note: While in-memory does not require any specific metadata for the component to work, `spec.metadata` is a required field.
 
 ## Related links
+
 - [Basic schema for a Dapr component]({{< ref component-schema >}})
 - Learn [how to create and configure state store components]({{< ref howto-get-save-state.md >}}) 
 - Read more about the [state management building block]({{< ref state-management >}})

daprdocs/data/components/pubsub/generic.yaml

@@ -1,6 +1,6 @@
 - component: In-memory
   link: setup-inmemory
-  state: Beta
+  state: Stable
   version: v1
   since: "1.7"
   features:

daprdocs/data/components/state_stores/generic.yaml

@@ -77,9 +77,9 @@
     query: false
 - component: In-memory
   link: setup-inmemory
-  state: Developer-only
+  state: Stable
   version: v1
-  since: "1.8"
+  since: "1.9"
   features:
     crud: true
     transactions: true