From b2ac65041f8deedaf87dd108fa3fe5284e7f80e3 Mon Sep 17 00:00:00 2001 From: Aumetra Weisman Date: Tue, 21 May 2024 17:20:25 +0200 Subject: [PATCH] Fix wording --- src/pages/core/architecture/actor-model.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/core/architecture/actor-model.mdx b/src/pages/core/architecture/actor-model.mdx index 763050b1..5d33ab39 100644 --- a/src/pages/core/architecture/actor-model.mdx +++ b/src/pages/core/architecture/actor-model.mdx @@ -16,8 +16,8 @@ While the term "actor model" sounds fancy, it is actually quite simple. Each contract is an "actor" and _plays_ a role in the system (pun intended). Each actor has its own state and can only be interacted with via messages. This -means that when a contract is called, it can only call other contracts via -messages and cannot directly call their code. +means a contract can only interact with the outside world via messages and only +manipulate its own state. Picture two people living in two houses, each house has a mailbox. If person A wants to talk to person B, they write a letter and put it in person B's mailbox.