[gdb] Fix common misspellings

Fix the following common misspellings:
...
accidently -> accidentally
additonal -> additional
addresing -> addressing
adress -> address
agaisnt -> against
albiet -> albeit
arbitary -> arbitrary
artifical -> artificial
auxillary -> auxiliary
auxilliary -> auxiliary
bcak -> back
begining -> beginning
cannonical -> canonical
compatiblity -> compatibility
completetion -> completion
diferent -> different
emited -> emitted
emiting -> emitting
emmitted -> emitted
everytime -> every time
excercise -> exercise
existance -> existence
fucntion -> function
funtion -> function
guarentee -> guarantee
htis -> this
immediatly -> immediately
layed -> laid
noone -> no one
occurances -> occurrences
occured -> occurred
originaly -> originally
preceeded -> preceded
preceeds -> precedes
propogate -> propagate
publically -> publicly
refering -> referring
substract -> subtract
substracting -> subtracting
substraction -> subtraction
taht -> that
targetting -> targeting
teh -> the
thier -> their
thru -> through
transfered -> transferred
transfering -> transferring
upto -> up to
vincinity -> vicinity
whcih -> which
whereever -> wherever
wierd -> weird
withing -> within
writen -> written
wtih -> with
doesnt -> doesn't
...

Tested on x86_64-linux.

gdb/gdbtypes.c

@@ -631,7 +631,7 @@ address_space_name_to_type_instance_flags (struct gdbarch *gdbarch,
 }
 
 /* Identify address space identifier by type_instance_flags and return
-   the string version of the adress space name.  */
+   the string version of the address space name.  */
 
 const char *
 address_space_type_instance_flags_to_name (struct gdbarch *gdbarch,
@@ -733,7 +733,7 @@ make_type_with_address_space (struct type *type,
    If TYPEPTR and *TYPEPTR are non-zero, then *TYPEPTR points to
    storage to hold the new qualified type; *TYPEPTR and TYPE must be
    in the same objfile.  Otherwise, allocate fresh memory for the new
-   type whereever TYPE lives.  If TYPEPTR is non-zero, set it to the
+   type wherever TYPE lives.  If TYPEPTR is non-zero, set it to the
    new type we construct.  */
 
 struct type *
@@ -1371,7 +1371,7 @@ create_array_type_with_stride (type_allocator &alloc,
 	 undefined by setting it to zero.  Although we are not expected
 	 to trust TYPE_LENGTH in this case, setting the size to zero
 	 allows us to avoid allocating objects of random sizes in case
-	 we accidently do.  */
+	 we accidentally do.  */
       result_type->set_length (0);
     }
 
@@ -1553,7 +1553,7 @@ set_type_self_type (struct type *type, struct type *self_type)
 }
 
 /* Smash TYPE to be a type of pointers to members of SELF_TYPE with type
-   TO_TYPE.  A member pointer is a wierd thing -- it amounts to a
+   TO_TYPE.  A member pointer is a weird thing -- it amounts to a
    typed offset into a struct, e.g. "an int at offset 8".  A MEMBER
    TYPE doesn't include the offset (that's the value of the MEMBER
    itself), but does include the structure type into which it points