From 48bd2a9d01a2527085006876a89f801840793bb9 Mon Sep 17 00:00:00 2001 From: Akhilesh Singhania Date: Wed, 28 Feb 2024 09:34:47 +0100 Subject: [PATCH] Update neps/nep-519-yield-execution.md Co-authored-by: Michael Birch --- neps/nep-519-yield-execution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/neps/nep-519-yield-execution.md b/neps/nep-519-yield-execution.md index 485959d54..a1f97f3b1 100644 --- a/neps/nep-519-yield-execution.md +++ b/neps/nep-519-yield-execution.md @@ -30,7 +30,7 @@ Today, the NEAR protocol has no sensible way to defer replying to the caller in - `promise_yield_create`: this can be called by a contract to indicate to the protocol that it is not ready yet to reply to its caller. - `promise_yield_resume`: a contract can use this mechanism to indicate to a protocol that it is now ready to reply to a caller that it had deferred earlier. -If these two host functions were available, then `yield` would be used in step 2 above and `resume` would be used in step 4 above. +If these two host functions were available, then `promise_yield_create` would be used in step 2 above and `promise_yield_resume` would be used in step 4 above. ## Specification