[patch] fortran/*.texi: Fix typos.

[Kazu Hirata]

Hi,

Attached is a patch to fix typos.

Committed as obvious.

Kazu Hirata

2009-12-16  Kazu Hirata  <kazu@codesourcery.com>

	* gfc-internals.texi, gfortran.texi, invoke.texi: Fix typos.
	Follow spelling conventions.

Index: fortran/gfc-internals.texi
===================================================================
--- fortran/gfc-internals.texi	(revision 155276)
+++ fortran/gfc-internals.texi	(working copy)
@@ -425,7 +425,7 @@ the type, rank and, if applicable, shape
 tree of which the current structure is the root.  @code{where} is the locus of
 this expression in the source code.
 
-Depending on the flavour of the expression being described by the object
+Depending on the flavor of the expression being described by the object
 (that is, the value of its @code{expr_type} member), the corresponding structure
 in the @code{value} union will usually contain additional data describing the
 expression's value in a type-specific manner.  The @code{ref} member is used to
Index: fortran/gfortran.texi
===================================================================
--- fortran/gfortran.texi	(revision 155276)
+++ fortran/gfortran.texi	(working copy)
@@ -1911,7 +1911,7 @@ all C features have a Fortran equivalent
 neither C's unsigned integers nor C's functions with variable number
 of arguments have an equivalent in Fortran.
 
-Note that array dimensions are reversely orded in C and that arrays in
+Note that array dimensions are reversely ordered in C and that arrays in
 C always start with index 0 while in Fortran they start by default with
 1. Thus, an array declaration @code{A(n,m)} in Fortran matches
 @code{A[m][n]} in C and accessing the element @code{A(i,j)} matches
Index: fortran/invoke.texi
===================================================================
--- fortran/invoke.texi	(revision 155276)
+++ fortran/invoke.texi	(working copy)
@@ -761,7 +761,7 @@ check that the declared interfaces are c
 Warn if @command{gfortran} finds a procedure named like an intrinsic not
 available in the currently selected standard (with @option{-std}) and treats
 it as @code{EXTERNAL} procedure because of this.  @option{-fall-intrinsics} can
-be used to never trigger this behaviour and always link to the intrinsic
+be used to never trigger this behavior and always link to the intrinsic
 regardless of the selected standard.
 
 @item -Wsurprising