From f0502e896bbdfa6413c208d6e969acc5060abbd0 Mon Sep 17 00:00:00 2001 From: salaboy Date: Tue, 21 May 2024 13:28:33 +0100 Subject: [PATCH] Update daprdocs/content/en/operations/dapr-shared/dapr-shared.md Co-authored-by: Mark Fussell Signed-off-by: salaboy --- daprdocs/content/en/operations/dapr-shared/dapr-shared.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/dapr-shared/dapr-shared.md b/daprdocs/content/en/operations/dapr-shared/dapr-shared.md index b951cadf6..8f448d4a0 100644 --- a/daprdocs/content/en/operations/dapr-shared/dapr-shared.md +++ b/daprdocs/content/en/operations/dapr-shared/dapr-shared.md @@ -37,7 +37,7 @@ No matter which strategy you choose, it is important to understand that in most ### `DeamonSet` strategy -With Kubernetes `DaemonSet`, you can define workloads that need to be deployed once per node in the cluster. This enables workloads that are running in the same node to communicate with local daprd APIs, no matter where the Kubernetes `Scheduler` schedules your workload. +With Kubernetes `DaemonSet`, you can define workloads that need to be deployed once per node in the cluster. This enables workloads that are running on the same node to communicate with local Dapr APIs, no matter where the Kubernetes `Scheduler` schedules your workload.