summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorJana Trestikova <jana.trestikova@gmail.com>2015-10-23 23:54:45 +0200
committerJana Trestikova <jana.trestikova@gmail.com>2015-10-24 00:01:32 +0200
commit8e4d294227590194285cec139bae5930d470eaf2 (patch)
treeae9425e145cc65392e3cd0d58c3642bd325333b8
parentf4775ea193c6ccd27950c39b46b11c9041fb8bfa (diff)
Fix typos
undestanding -> understanding uninterupted -> uninterrupted
-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;