spelling

yinwang0 · May 4, 2016 · f558aa0 · f558aa0
1 parent eb2b1fd
commit f558aa0
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/c/gcwrapper.c b/c/gcwrapper.c
@@ -130,7 +130,7 @@ void S_gc_init() {
     S_G.countof_size[countof_guardian] = 0;
   for (i = 0; i < countof_types; i += 1) {
     if (Svector_ref(S_G.countof_names, i) == FIX(0)) {
-      fprintf(stderr, "unitialized countof_name at index %d\n", i);
+      fprintf(stderr, "uninitialized countof_name at index %d\n", i);
       S_abnormal_exit();
     }
   }

diff --git a/c/scheme.c b/c/scheme.c
@@ -620,7 +620,7 @@ static IBOOL find_boot(name, ext, errorp) const char *name, *ext; IBOOL errorp;
                   Sschemeheapdirs, Sdefaultheapdirs);
           S_abnormal_exit();
         } else {
-          if (verbose) fprintf(stderr, "no compatable %s%s found\n", name, ext);
+          if (verbose) fprintf(stderr, "no compatible %s%s found\n", name, ext);
           return 0;
         }
       }

diff --git a/scheme.1.in b/scheme.1.in
@@ -605,7 +605,7 @@ At optimize-levels 0, 1, and 2, code generated by the compiler is
 At optimize-level 3, code generated by the compiler is \fIunsafe\fP,
 i.e., may omit these checks.
 Unsafe code is usually faster, but optimize-level 3 should be used only
-for well-tested code since the absense of type and bounds checks may
+for well-tested code since the absence of type and bounds checks may
 result in invalid memory references, corruption of the Scheme heap (which
 may cause seemingly unrelated problems later), system crashes, or other
 undesirable behaviors.