From 29843f42ee03e40ded4cb0b523ddad9d61c7bdb4 Mon Sep 17 00:00:00 2001 From: Chase Fleming Date: Wed, 8 Nov 2023 09:20:03 -0800 Subject: [PATCH] Update docs/build/advanced-concepts/randomness.md Co-authored-by: Tarak Ben Youssef <50252200+tarakby@users.noreply.github.com> --- docs/build/advanced-concepts/randomness.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/build/advanced-concepts/randomness.md b/docs/build/advanced-concepts/randomness.md index 801f8de996..1bfa51493f 100644 --- a/docs/build/advanced-concepts/randomness.md +++ b/docs/build/advanced-concepts/randomness.md @@ -59,7 +59,7 @@ In other words, transactions submitted by a non-trusted party are able to reject 💡 **Post-selection** - the ability for transactions to reject results they don't like - is inherent to any smart contract platform that allows transactions to roll back atomically. See this very similar [Ethereum example](https://consensys.github.io/smart-contract-best-practices/development-recommendations/general/public-data/). -The central aspect that you as a developer have to think about is the following scenario: +The central aspect that a contract developer needs to think about is the following scenario: - Imagine an adversarial user that is sending a transaction that calls your smart contract. - The transaction includes code that runs after your smart contract returns and inspects the outcome.