aboutsummaryrefslogtreecommitdiffstats
path: root/erts/include/internal
diff options
context:
space:
mode:
authorRaimo Niskanen <[email protected]>2018-07-26 14:14:14 +0200
committerRaimo Niskanen <[email protected]>2018-07-27 10:16:17 +0200
commit37c11cda19bd9067a4e094fbde53b276d6ab0d3d (patch)
tree2573bafa6dc9ca3b47c1d4dd974590b4a924bb8b /erts/include/internal
parent1fd03472d3d57e57ae4ebcbf0109f82dce14b90c (diff)
downloadotp-37c11cda19bd9067a4e094fbde53b276d6ab0d3d.tar.gz
otp-37c11cda19bd9067a4e094fbde53b276d6ab0d3d.tar.bz2
otp-37c11cda19bd9067a4e094fbde53b276d6ab0d3d.zip
Change "can not" into "cannot"
I did not find any legitimate use of "can not", however skipped changing e.g RFCs archived in the source tree.
Diffstat (limited to 'erts/include/internal')
-rw-r--r--erts/include/internal/gcc/ethr_membar.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/erts/include/internal/gcc/ethr_membar.h b/erts/include/internal/gcc/ethr_membar.h
index 07960ce040..5cbda5582d 100644
--- a/erts/include/internal/gcc/ethr_membar.h
+++ b/erts/include/internal/gcc/ethr_membar.h
@@ -96,7 +96,7 @@
* issue an aquire memory barrier and an __atomic
* builtin memory acess with the __ATOMIC_RELEASE
* memory model must at least issue a release memory
- * barrier. Otherwise the two can not be paired.
+ * barrier. Otherwise the two cannot be paired.
* 4. All __atomic builtins accessing memory using the
* __ATOMIC_CONSUME builtin can be used for the same
* reason __ATOMIC_ACQUIRE can be used. The ethread