Skip to content

Commit bd4c778

Browse files
authored
Apply suggestion from @briandoyle81
1 parent 897e506 commit bd4c778

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/blockchain-development-tutorials/forte/scheduled-transactions/scheduled-transactions-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ As a result, most blockchain computers, including EVM and Solana, aren't [Turing
3333

3434
While this limitation prevents infinite loops, it makes it so that you can't do anything 100% onchain if you need it to happen at a later time or after a trigger. As a result, developers must often build products that involve a fair amount of traditional infrastructure and requires users to give those developers a great amount of trust that their backend will execute the promised task.
3535

36-
Flow fixes this problem with **scheduled transactions**. Scheduled Transactions let smart contracts execute code at, or after, a chosen time without an external transaction. You schedule work now and the network executes it later. This allows recurring jobs, deferred actions, and autonomous workflows.
36+
Flow fixes this problem with _scheduled transactions_. Scheduled Transactions let smart contracts execute code at, or after, a chosen time without an external transaction. You schedule work now and the network executes it later. This allows recurring jobs, deferred actions, and autonomous workflows.
3737

3838
## Learning Objectives
3939

0 commit comments

Comments
 (0)