Fix typos
llvm-svn: 202018
diff --git a/openmp/runtime/src/kmp_i18n.c b/openmp/runtime/src/kmp_i18n.c
index 5cca6e8..8a89d0a 100644
--- a/openmp/runtime/src/kmp_i18n.c
+++ b/openmp/runtime/src/kmp_i18n.c
@@ -361,7 +361,7 @@
reinterpret_cast< LPCSTR >( & __kmp_i18n_do_catopen ),
& handle
);
- if ( ! brc ) { // Error occured.
+ if ( ! brc ) { // Error occurred.
status = KMP_I18N_ABSENT; // mark catalog as absent so it will not be re-opened.
goto end;
// TODO: Enable multiple messages (KMP_MSG) to be passed to __kmp_msg; and print
@@ -371,7 +371,7 @@
// Now get path to the our DLL.
for ( ; ; ) {
DWORD drc = GetModuleFileName( handle, path.str, path.size );
- if ( drc == 0 ) { // Error occured.
+ if ( drc == 0 ) { // Error occurred.
status = KMP_I18N_ABSENT;
goto end;
}; // if
@@ -473,7 +473,7 @@
/*
We use FormatMessage() to get strings from catalog, get system error messages, etc.
FormatMessage() tends to return Windows* OS-style end-of-lines, "\r\n". When string is printed,
- printf() also replaces all the occurences of "\n" with "\r\n" (again!), so sequences like
+ printf() also replaces all the occurrences of "\n" with "\r\n" (again!), so sequences like
"\r\r\r\n" appear in output. It is not too good.
Additional mess comes from message catalog: Our catalog source en_US.mc file (generated by
@@ -492,7 +492,7 @@
Thus, stripping all "\r" normalizes string and returns it to canonical form, so printf() will
produce correct end-of-line sequences.
- ___strip_crs() serves for this purpose: it removes all the occurences of "\r" in-place and
+ ___strip_crs() serves for this purpose: it removes all the occurrences of "\r" in-place and
returns new length of string.
*/
static