Commit ed499b9f by Steven G. Kargl Committed by Steven G. Kargl

gfortran.texi: Fix last commit where a "no" was deleted and a grammatical error was introduced.

2006-08-23  Steven G. Kargl  <kargls@comcast.net>

	* gfortran.texi:  Fix last commit where a "no" was deleted and
	a grammatical error was introduced.

From-SVN: r116362
parent deeddce6
2006-08-23 Steven G. Kargl <kargls@comcast.net> 2006-08-23 Steven G. Kargl <kargls@comcast.net>
* gfortran.texi: Fix last commit where a "no" was deleted and
a grammatical error was introduced.
2006-08-23 Steven G. Kargl <kargls@comcast.net>
* gfortran.texi: Spell check. Add a few contributors to * gfortran.texi: Spell check. Add a few contributors to
Chapter 9. Expand the description of BOZ constant handling. Chapter 9. Expand the description of BOZ constant handling.
......
...@@ -1259,7 +1259,7 @@ Most of the interface with GCC was written by @emph{Paul Brook}. ...@@ -1259,7 +1259,7 @@ Most of the interface with GCC was written by @emph{Paul Brook}.
The following individuals have contributed code and/or The following individuals have contributed code and/or
ideas and significant help to the gfortran project ideas and significant help to the gfortran project
(in particular order): (in no particular order):
@itemize @minus @itemize @minus
@item Andy Vaught @item Andy Vaught
...@@ -1303,7 +1303,7 @@ and much needed feedback and encouragement for the ...@@ -1303,7 +1303,7 @@ and much needed feedback and encouragement for the
Many other individuals have helped debug, Many other individuals have helped debug,
test and improve @command{gfortran} over the past few years, test and improve @command{gfortran} over the past few years,
and we welcoming you to do the same! and we welcome you to do the same!
If you already have done so, If you already have done so,
and you would like to see your name listed in the and you would like to see your name listed in the
list above, please contact us. list above, please contact us.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment