From 444575e6628948ca0ccfc70a24c42e2cb7de0d8a Mon Sep 17 00:00:00 2001 From: Jonathan Powers Date: Fri, 5 Jan 2024 12:24:20 -0500 Subject: [PATCH] Update repetition.mdx (#425) --- pages/docs/scheduling/repetition.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/docs/scheduling/repetition.mdx b/pages/docs/scheduling/repetition.mdx index 04f425a4c..845c2c15e 100644 --- a/pages/docs/scheduling/repetition.mdx +++ b/pages/docs/scheduling/repetition.mdx @@ -31,9 +31,9 @@ Effect.repeat(action, policy) ## repeatOrElse -There is another version of `repeat` that helps us to have a fallback strategy in case of erros, -if something goes wrong we can handle that by using the `Effect.repeatOrElse` function, -which helps up to add an `orElse` callback that will run in case of repetition failure. +There is another version of `repeat` that helps us to have a fallback strategy in case of errors. +If something goes wrong we can handle that by using the `Effect.repeatOrElse` function, +which helps us to add an `orElse` callback that will run in case of repetition failure. The basic syntax of `repeatOrElse` is as follows: