From d71bd7334c5c9363d49ddf20645e6041af15fa41 Mon Sep 17 00:00:00 2001 From: Zoffix Znet Date: Fri, 26 Jan 2018 09:18:54 -0500 Subject: [PATCH] Fix typo --- docs/qast.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/qast.markdown b/docs/qast.markdown index 9651312a14..bd93b99512 100644 --- a/docs/qast.markdown +++ b/docs/qast.markdown @@ -206,7 +206,7 @@ There is a variant of QAST::Stmts, which is QAST::Stmt. While the first has no impact on the allocation of temporaries, QAST::Stmt marks a register allocation boundary; beyond it, any temporaries are free to be reused. You do not need to use QAST::Stmt, but it can lead to better code generation if -used correct. Incorrect use can, of course, lead to incorrect code generation. +used correctly. Incorrect use can, of course, lead to incorrect code generation. Like QAST::Stmts, it also can have multiple children and supports resultchild. ## QAST::IVal, QAST::NVal and QAST::SVal