From d09571a70980ae97a861ebae218727bc06b869e0 Mon Sep 17 00:00:00 2001 From: Mohamad Fadhil Date: Mon, 25 Nov 2024 06:04:27 +0800 Subject: [PATCH] Fix typo in README (#529) Signed-off-by: Mohamad Fadhil --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b24f8656..dbe3d40f 100644 --- a/README.md +++ b/README.md @@ -263,7 +263,7 @@ The choice of protobuf is due to easy serialization over wire and strong schema You can schedule sending messages to actor that will be acted upon in the future. To achieve that you can use the following methods on the [Actor System](./actors/actor_system.go): - `ScheduleOnce` - will send the given message to a local actor _**once**_ after a given interval -- `Schedule` - will sendd the given message to a local actor at a given interval +- `Schedule` - will send the given message to a local actor at a given interval - `RemoteSchedule` - will send the given message to a remote actor at a given interval. This requires remoting to be enabled on the actor system. - `RemoteScheduleOnce` - will send the given message to a remote actor _**once**_ after a given interval. This requires remoting to be enabled on the actor system. - `ScheduleWithCron` - will send the given message to a local actor using a [cron expression](#cron-expression-format). @@ -656,4 +656,4 @@ earthly +test One can run the benchmark test from the [bench package](./bench): - `make bench` to run the benchmark -- `make bench-stats` to see the benchmark stats \ No newline at end of file +- `make bench-stats` to see the benchmark stats