Imported gcc-4.4.3

[msp430-gcc.git] / gcc / config / arm / README-interworking

diff --git a/gcc/config/arm/README-interworking b/gcc/config/arm/README-interworking
index 46b76c9924251d6369ff8b7456515df7a4d23b89..d221e1555760ea7e9c472e2e9b3e97c08a195665 100644 (file)
--- a/gcc/config/arm/README-interworking
+++ b/gcc/config/arm/README-interworking
@@ -78,7 +78,7 @@ then the following rules must be obeyed:
 
        * All externally visible functions which should be entered in
        Thumb mode must have the .thumb_func pseudo op specified just
-       before their entry point.  eg:
+       before their entry point.  e.g.:
 
                        .code 16
                        .global function
@@ -235,7 +235,7 @@ processing is enabled.
 When the -mthumb-interwork command line switch is specified, gcc
 arranges for all functions to return to their caller by using the BX
 instruction.  Thus provided that the return address has the bottom bit
-correctly initialised to indicate the instruction set of the caller,
+correctly initialized to indicate the instruction set of the caller,
 correct operation will ensue.
 
 When a function is called explicitly (rather than via a function
@@ -404,7 +404,7 @@ Instead the pseudo op is attached to a new label .real_start_of_<name>
 (where <name> is the name of the function) which indicates the start
 of the Thumb code.  This does have the interesting side effect in that
 if this function is now called from a Thumb mode piece of code
-outsside of the current file, the linker will generate a calling stub
+outside of the current file, the linker will generate a calling stub
 to switch from Thumb mode into ARM mode, and then this is immediately
 overridden by the function's header which switches back into Thumb
 mode.