summaryrefslogtreecommitdiffstats
path: root/docs/language-reference/06-statements.md
diff options
context:
space:
mode:
authorBruce Mitchener <bruce.mitchener@gmail.com>2024-11-29 14:02:19 +0700
committerGitHub <noreply@github.com>2024-11-29 15:02:19 +0800
commitc3557978cf0184aaf75c27c309bc87e84fd6ab79 (patch)
treee7372839055ca3a7f2ad7b3aa7c895e428778533 /docs/language-reference/06-statements.md
parent71f97268789164bd77614636536172ba657c6a57 (diff)
docs: Reduce typo count (#5671)
Co-authored-by: Ellie Hermaszewska <ellieh@nvidia.com>
Diffstat (limited to 'docs/language-reference/06-statements.md')
-rw-r--r--docs/language-reference/06-statements.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/language-reference/06-statements.md b/docs/language-reference/06-statements.md
index 7a4770d99..5c3b77ad4 100644
--- a/docs/language-reference/06-statements.md
+++ b/docs/language-reference/06-statements.md
@@ -3,7 +3,7 @@
Statements
==========
-Statements are used to define the bodies of functions and deterine order of evaluation and control flow for an entire program.
+Statements are used to define the bodies of functions and determine order of evaluation and control flow for an entire program.
Statements are distinct from expressions in that statements do not yield results and do not have types.
This section lists the kinds of statements supported by Slang.
@@ -101,7 +101,7 @@ default:
break;
```
-A _case label_ consists of the keyword `case` followed by an expresison and a colon (`:`).
+A _case label_ consists of the keyword `case` followed by an expressions and a colon (`:`).
The expression must evaluate to a compile-time constant integer.
A _default label_ consists of the keyword `default` followed by a colon (`:`).
@@ -203,7 +203,7 @@ The value returned must be able to coerce to the result type of the lexically en
### Discard Statement
-A `discard` statement can only be used in the context of a fragment shader, in which case it causes the current invocation to terminate and the graphics system to discard the corresponding fragment so that it does not get combined with the framebuffer pixel at its coordintes.
+A `discard` statement can only be used in the context of a fragment shader, in which case it causes the current invocation to terminate and the graphics system to discard the corresponding fragment so that it does not get combined with the framebuffer pixel at its coordinates.
Operations with side effects that were executed by the invocation before a `discard` will still be performed and their results will become visible according to the rules of the platform.