From e5b36e2c1c410fe2a7ba1747ebf33f0fbd306cbe Mon Sep 17 00:00:00 2001 From: Tiago Alves Macambira Date: Wed, 8 Feb 2023 15:27:53 -0800 Subject: [PATCH] Update daprdocs/content/en/operations/components/pluggable-components-registration.md Co-authored-by: Phillip Hoff Signed-off-by: Tiago Alves Macambira --- .../operations/components/pluggable-components-registration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/components/pluggable-components-registration.md b/daprdocs/content/en/operations/components/pluggable-components-registration.md index d581414f5..f44077399 100644 --- a/daprdocs/content/en/operations/components/pluggable-components-registration.md +++ b/daprdocs/content/en/operations/components/pluggable-components-registration.md @@ -68,7 +68,7 @@ Define your component using a [component spec]({{< ref component-schema.md >}}). You will need to define one [component spec]({{< ref component-schema.md >}}) for each building block exposed by your pluggable component's [Unix Domain Socket][uds]. From the example above, the UDS `my-component.sock` from the previous example, exposes a pluggable component named `my-component` with both a `state` and a `pubsub` building blocks. Two components specs, each in their own YAML file placed in the resouces-path, will be required, one for `state.my-component` and another for `pubsub.my-component`. -For instance, the component spec for `state.my-component` could be as follow +For instance, the component spec for `state.my-component` could be: ```yaml apiVersion: dapr.io/v1alpha1