* doc/tm.texi, doc/tree-ssa.texi: Fix typos.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@87324 138bc75d-0d04-0410-961f-82ee72b054a4

2 files changed, 2 insertions, 2 deletions

diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index df72053313d..f756012d6a3 100644
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@ -9387,7 +9387,7 @@ that are different from @option{-I}.
 This target hook returns @code{true} if it is safe to use a local alias
 for a virtual function @var{fndecl} when constructing thunks,
 @code{false} otherwise. By default, the hook returns @code{true} for all
-functions, if a target supports aliases (ie. defines
+functions, if a target supports aliases (i.e. defines
 @code{ASM_OUTPUT_DEF}), @code{false} otherwise,
 @end deftypefn
 
diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi
index 1c88e9f021c..c62dcce48f4 100644
--- a/gcc/doc/tree-ssa.texi
+++ b/gcc/doc/tree-ssa.texi
@@ -709,7 +709,7 @@ definitions. For globals, structures, and arrays, we can determine from
 a statement whether a variable of these types has a killing definition. 
 If the variable does, then the statement is marked as having a
 @dfn{must definition} of that variable. However, if a statement is only
-defining a part of the variable (ie. a field in a structure), or if we
+defining a part of the variable (i.e. a field in a structure), or if we
 know that a statement might define the variable but we cannot say for sure,
 then we mark that statement as having a @dfn{may definition}.  For 
 instance, given