Fix Spelling Errors (backport #152)

Migration.md

@@ -1,4 +1,4 @@
-# Note on deprecations
+# Note on deprecation
 A tick-tock release cycle allows easy migration to new software versions.
 Obsolete code is marked as deprecated for one major release.
 Deprecated code produces compile-time warnings. These warning serve as

cmake/run_test.cmake

@@ -4,7 +4,7 @@ execute_process(COMMAND ruby ${IGN_SCRIPT}
   OUTPUT_VARIABLE TEST_OUTPUT
   ERROR_VARIABLE TEST_ERROR)
 
-# Copy failure result everytime we run test so we don't accidentally use
+# Copy failure result every time we run test so we don't accidentally use
 # previous results.
 execute_process(COMMAND
   ${CMAKE_COMMAND} -E copy

etc/ign.bash_completion.sh

@@ -29,7 +29,7 @@ function _ign
 
   # Look for the first command that is not an option (-*)
   # COMP_WORDS: array of words in current command line COMP_LINE
-  # COMP_CWORD: index of word containing current cursur location
+  # COMP_CWORD: index of word containing current cursor location
   # COMP_LINE: line entered so far
   for ((i=1; $i<=$COMP_CWORD; i++)); do
     if [[ ${COMP_WORDS[i]} != -* ]]; then

src/Backward/README.md

@@ -104,7 +104,7 @@ following libraries:
 
 Unwind comes from libgcc, but there is an equivalent inside clang itself. With
 unwind, the stacktrace is as accurate as it can possibly be, since this is
-used by the C++ runtine in gcc/clang for stack unwinding on exception.
+used by the C++ runtime in gcc/clang for stack unwinding on exception.
 
 Normally libgcc is already linked to your program by default.
 

src/Backward/backward.hpp

@@ -102,7 +102,7 @@
 // #define BACKWARD_HAS_UNWIND 1
 //  - unwind comes from libgcc, but I saw an equivalent inside clang itself.
 //  - with unwind, the stacktrace is as accurate as it can possibly be, since
-//  this is used by the C++ runtine in gcc/clang for stack unwinding on
+//  this is used by the C++ runtime in gcc/clang for stack unwinding on
 //  exception.
 //  - normally libgcc is already linked to your program by default.
 //
@@ -272,7 +272,7 @@
 // #define BACKWARD_HAS_UNWIND 1
 //  - unwind comes from libgcc, but I saw an equivalent inside clang itself.
 //  - with unwind, the stacktrace is as accurate as it can possibly be, since
-//  this is used by the C++ runtine in gcc/clang for stack unwinding on
+//  this is used by the C++ runtime in gcc/clang for stack unwinding on
 //  exception.
 //  - normally libgcc is already linked to your program by default.
 //
@@ -713,7 +713,7 @@ struct ResolvedTrace : public Trace {
 
 /*************** STACK TRACE ***************/
 
-// default implemention.
+// default implementation.
 template <typename TAG> class StackTraceImpl {
 public:
   size_t size() const { return 0; }
@@ -828,7 +828,7 @@ template <typename F> class Unwinder {
     uintptr_t ip = _Unwind_GetIPInfo(ctx, &ip_before_instruction);
 
     if (!ip_before_instruction) {
-      // calculating 0-1 for unsigned, looks like a possible bug to sanitiziers,
+      // calculating 0-1 for unsigned, looks like a possible bug to sanitizers,
       // so let's do it explicitly:
       if (ip == 0) {
         ip = std::numeric_limits<uintptr_t>::max(); // set it to 0xffff... (as
@@ -1481,7 +1481,7 @@ class TraceResolverLinuxImpl<trace_resolver_tag::libbfd>
         // this time we get the name of the function where the code is
         // located, instead of the function were the address is
         // located. In short, if the code was inlined, we get the
-        // function correspoding to the code. Else we already got in
+        // function corresponding to the code. Else we already got in
         // trace.function.
         trace.source.function = demangle(details_selected->funcname);