This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
more doc typos
- From: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- To: gcc-patches at gcc dot gnu dot org
- Date: Thu, 24 Jan 2008 19:18:05 +0100
- Subject: more doc typos
Again, I have no commit privileges for GCC.
Thanks,
Ralf
libjava/classpath/ChangeLog:
2008-01-24 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* doc/README.jaxp: Fix typos.
gcc/ada/ChangeLog:
2008-01-24 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* gnat_ugn.texi (Calling Conventions, Notes on the Command Line)
(Basic Syntax, Using gnatkr): Fix typos.
* gnat_rm.texi (Implementation Defined Characteristics):
Likewise.
Index: libjava/classpath/doc/README.jaxp
===================================================================
--- libjava/classpath/doc/README.jaxp (Revision 131766)
+++ libjava/classpath/doc/README.jaxp (Arbeitskopie)
@@ -155,7 +155,7 @@
When using libxmlj, the libxmlj shared library must be available.
In general it is picked up by the runtime using GNU Classpath. If not you
might want to try adding the directory where libxmlj.so is installed
-(by default ${prefix}/lib/classpath/) with ldconfig or specifing in the
+(by default ${prefix}/lib/classpath/) with ldconfig or specifying in the
LD_LIBRARY_PATH environment variable. Additionally, you may need to specify
the location of your shared libraries to the runtime environment using the
java.library.path system property.
@@ -174,7 +174,7 @@
using thread context variables.
Update: thread context variables have been introduced. This is very
-untested though, libxmll therefore still has the single thread
+untested though, libxmlj therefore still has the single thread
bottleneck.
Index: gcc/ada/gnat_rm.texi
===================================================================
--- gcc/ada/gnat_rm.texi (Revision 131766)
+++ gcc/ada/gnat_rm.texi (Arbeitskopie)
@@ -7157,7 +7157,7 @@
length. See 2.2(15).
@end cartouche
@noindent
-The maximum line length is 255 characters an the maximum length of a
+The maximum line length is 255 characters and the maximum length of a
lexical element is also 255 characters.
@sp 1
Index: gcc/ada/gnat_ugn.texi
===================================================================
--- gcc/ada/gnat_ugn.texi (Revision 131766)
+++ gcc/ada/gnat_ugn.texi (Arbeitskopie)
@@ -2738,7 +2738,7 @@
Note that in the case of GNAT running
on a platform that supports HP Ada 83, a higher degree of compatibility
-can be guaranteed, and in particular records are layed out in an identical
+can be guaranteed, and in particular records are laid out in an identical
manner in the two compilers. Note also that if output from two different
compilers is mixed, the program is responsible for dealing with elaboration
issues. Probably the safest approach is to write the main program in the
@@ -9175,7 +9175,7 @@
@item
Using @command{gnatmake} along with the
@option{^-m (minimal recompilation)^/MINIMAL_RECOMPILATION^}
-switch provides a mechanism for avoiding unnecessary rcompilations. Using
+switch provides a mechanism for avoiding unnecessary recompilations. Using
this switch,
you can update the comments/format of your
source files without having to recompile everything. Note, however, that
@@ -11943,7 +11943,7 @@
@end itemize
@noindent
-Comments in project files have the same syntax as in Ada, two consecutives
+Comments in project files have the same syntax as in Ada, two consecutive
hyphens through the end of the line.
@node Packages
@@ -17074,7 +17074,7 @@
@noindent
@var{name} is the uncrunched file name, derived from the name of the unit
-in the standard manner described in the previous section (i.e. in particular
+in the standard manner described in the previous section (i.e., in particular
all dots are replaced by hyphens). The file name may or may not have an
extension (defined as a suffix of the form period followed by arbitrary
characters other than period). If an extension is present then it will