summaryrefslogtreecommitdiffhomepage
path: root/chapel.html.markdown
diff options
context:
space:
mode:
authorHunter Stevens <onebree@gmail.com>2016-02-15 17:47:35 -0500
committerHunter Stevens <onebree@gmail.com>2016-02-15 17:47:35 -0500
commitd0b067b140d3d351ae9dee0b3e542935b7ca35d4 (patch)
treeb83501b5b82240663029d7382f873fb369ea81c7 /chapel.html.markdown
parentcffb7e6770b517a620115b3a9e1f82ca1dd82a98 (diff)
parentcd16626c8f64a29d8235bd0ab21c7a32e248928f (diff)
Resolve conflicts from merge
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;