From 0389dc4213285c02d0e9e14c6e560c8342c8ee1c Mon Sep 17 00:00:00 2001 From: Aaron Crawfis Date: Thu, 10 Dec 2020 10:45:03 -0800 Subject: [PATCH] Add link to hosting environments --- .../building-blocks/actors/actors-background.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/actors/actors-background.md b/daprdocs/content/en/developing-applications/building-blocks/actors/actors-background.md index 2dd081a99..b2c5f3a3f 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/actors/actors-background.md +++ b/daprdocs/content/en/developing-applications/building-blocks/actors/actors-background.md @@ -67,7 +67,7 @@ When a client calls an actor with a particular id (for example, actor id 123), t * By default, actors are randomly placed into pods resulting in uniform distribution. * Because actors are randomly placed, it should be expected that actor operations always require network communication, including serialization and deserialization of method call data, incurring latency and overhead. -Note: The Dapr actor Placement service is only used for actor placement and therefore is not needed if your services are not using Dapr actors. The Placement service can run in all hosting environments for example, self hosted or Kubernetes. +Note: The Dapr actor Placement service is only used for actor placement and therefore is not needed if your services are not using Dapr actors. The Placement service can run in all [hosting environments]({{< ref hosting >}}), including self-hosted and Kubernetes. ## Actor communication