diff --git a/daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md b/daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md
index 695d27033aa..fdde091390d 100644
--- a/daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md
+++ b/daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md
@@ -52,6 +52,12 @@ You would use Dapr Workflow when you need to define and orchestrate complex work
 
 [Learn more about Dapr Workflow and how to use workflows in your application.]({{< ref workflow-overview.md >}})
 
+## Actor types and actor IDs
+
+Actors are uniquely defined as an instance of an actor type, similar to how an object is an instance of a class. For example, you might have an actor type that implements the functionality of a calculator. There could be many actors of that type distributed across various nodes in a cluster.
+
+Each actor is uniquely identified by an actor ID. An actor ID can be _any_ string value you choose. If you do not provide an actor ID, Dapr generates a random string for you as an ID.
+
 ## Features
 
 ### Actor lifetime