diff --git a/daprdocs/content/en/operations/components/component-schema.md b/daprdocs/content/en/operations/components/component-schema.md
index 09fd461ea..0e4ab7822 100644
--- a/daprdocs/content/en/operations/components/component-schema.md
+++ b/daprdocs/content/en/operations/components/component-schema.md
@@ -67,6 +67,9 @@ spec:
       value: "false"
 ```
 
+The consumerID metadata values can also contain a `{podName}` tag that is replaced with the Kubernetes POD's name when the Dapr sidecar starts up. This can be used to have a persisted behavior where the ConsumerID does not change on restart when using StatefulSets in Kubernetes.
+
+
 ## Further reading
 - [Components concept]({{< ref components-concept.md >}})
 - [Reference secrets in component definitions]({{< ref component-secrets.md >}})
diff --git a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md
index 6ce033b3e..add1f9aa3 100644
--- a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md
+++ b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md
@@ -20,8 +20,11 @@ metadata:
 spec:
   type: pubsub.in-memory
   version: v1
+  metadata: []
 ```
 
+> 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