summaryrefslogtreecommitdiffhomepage
path: root/chapel.html.markdown
diff options
context:
space:
mode:
authorCY Lim <cylim@CYs-Macbook-2015.local>2015-11-02 11:18:19 +1100
committerCY Lim <cylim@CYs-Macbook-2015.local>2015-11-02 11:18:19 +1100
commit094761f6936e9fbe625a9175a6404e2dca7d6504 (patch)
tree0999371c1f48011acdfabe8eb3b0e01760833e06 /chapel.html.markdown
parent44ca091c73afe13ec8760021cfed1d77afc5e4a5 (diff)
parent463cec82d08a58c6452b5b2beec5ee3b99e33ba6 (diff)
Merge remote-tracking branch 'adambard/master'
Diffstat (limited to 'chapel.html.markdown')
-rw-r--r--chapel.html.markdown4
1 files changed, 2 insertions, 2 deletions
diff --git a/chapel.html.markdown b/chapel.html.markdown
index 7252a3e4..866e92d2 100644
--- a/chapel.html.markdown
+++ b/chapel.html.markdown
@@ -629,7 +629,7 @@ for (i, j) in zip( toThisArray.domain, -100..#5 ){
}
writeln( toThisArray );
-// This is all very important in undestanding why the statement
+// This is all very important in understanding why the statement
// var iterArray : [1..10] int = [ i in 1..10 ] if ( i % 2 == 1 ) then j;
// exhibits a runtime error.
// Even though the domain of the array and the loop-expression are
@@ -914,7 +914,7 @@ proc main(){
[ val in myBigArray ] val = 1 / val; // Parallel operation
// Atomic variables, common to many languages, are ones whose operations
- // occur uninterupted. Multiple threads can both modify atomic variables
+ // occur uninterrupted. Multiple threads can both modify atomic variables
// and can know that their values are safe.
// Chapel atomic variables can be of type bool, int, uint, and real.
var uranium: atomic int;