Skip to content
Browse files

Fix typos (spelling errors) in README*.

# New Ticket Created by  (Peter J. Acklam)
# Please include the string:  [perl #81912]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=81912 >

Signed-off-by: Abigail <abigail@abigail.be>
  • Loading branch information...
1 parent 486ec47 commit f858446f8d2c74c0a4665f0be04b65fe90e1b08c Peter J. Acklam) (via RT committed with Abigail Jan 6, 2011
Showing with 19 additions and 19 deletions.
  1. +1 −1 README.bs2000
  2. +2 −2 README.ce
  3. +1 −1 README.cygwin
  4. +1 −1 README.dgux
  5. +1 −1 README.linux
  6. +1 −1 README.macos
  7. +2 −2 README.macosx
  8. +1 −1 README.netware
  9. +1 −1 README.openbsd
  10. +3 −3 README.os2
  11. +1 −1 README.os390
  12. +2 −2 README.solaris
  13. +1 −1 README.symbian
  14. +1 −1 README.vms
View
2 README.bs2000
@@ -206,7 +206,7 @@ Perl, that it should use the native IO layer:
Now your IO would be ASCII on ASCII partitions and EBCDIC on EBCDIC
partitions. See the documentation of PerlIO (without C<Encode::>!)
-for further posibilities.
+for further possibilities.
=head1 AUTHORS
View
4 README.ce
@@ -132,7 +132,7 @@ archive.
NOTE: during a build there could be created a number (or one) of C<Config.pm>
for cross-compilation ("foreign" C<Config.pm>) and those are hidden inside
-C<../xlib/$(CROSS_NAME)> with other auxilary files, but, and this is important to
+C<../xlib/$(CROSS_NAME)> with other auxiliary files, but, and this is important to
note, there should be B<no> C<Config.pm> for host miniperl.
If you'll get an error that perl could not find Config.pm somewhere in building
process this means something went wrong. Most probably you forgot to
@@ -160,7 +160,7 @@ works on non-hpc devices.
The simple stdio implementation creates the files C<stdin.txt>,
C<stdout.txt> and C<stderr.txt>, so you might examine them if your
-console has only a liminted number of cols.
+console has only a limited number of cols.
When exitcode is non-zero, a message box appears, otherwise the
console closes, so you might have to catch an exit with
View
2 README.cygwin
@@ -673,7 +673,7 @@ be kept as clean as possible.
lib/CPANPLUS/Internals/Constants/Report.pm
- OS classifications
lib/CPANPLUS/Internals/Constants.pm
- - Contants for Cygwin
+ - Constants for Cygwin
lib/CPANPLUS/Internals/Report.pm
- Example of Cygwin report
lib/CPANPLUS/Module.pm
View
2 README.dgux
@@ -102,7 +102,7 @@ Run the command "make install"
=head1 AUTHOR
Takis Psarogiannakopoulos
-Universirty of Cambridge
+University of Cambridge
Centre for Mathematical Sciences
Department of Pure Mathematics
Wilberforce road
View
2 README.linux
@@ -13,7 +13,7 @@ version 5 (hereafter just Perl) is compiled and/or runs.
=head2 Experimental Support for Sun Studio Compilers for Linux OS
-Sun Microsystems has released a port of their Sun Studio compiliers for
+Sun Microsystems has released a port of their Sun Studio compilers for
Linux. As of November 2005, only an alpha version has been released.
Until a release of these compilers is made, support for compiling Perl with
these compiler experimental.
View
2 README.macos
@@ -20,7 +20,7 @@ Mac OS X.
=head1 DESCRIPTION
The port of Perl to to Mac OS was officially removed as of Perl 5.12,
-though the last offical production release of MacPerl corresponded to
+though the last official production release of MacPerl corresponded to
Perl 5.6. While Perl 5.10 included the port to Mac OS, ExtUtils::MakeMaker,
a core part of Perl's module installation infrastructure officially dropped support for Mac OS in April 2004.
View
4 README.macosx
@@ -93,7 +93,7 @@ omitted or buggy. Note the messages output by F<Configure> for further
information. Please use C<perlbug> to submit a problem report in the
event that you encounter difficulties.
-When building 64-bit modules, it is your responsiblity to ensure that linked
+When building 64-bit modules, it is your responsibility to ensure that linked
external libraries and frameworks provide 64-bit support: if they do not,
module building may appear to succeed, but attempts to use the module will
result in run-time dynamic linking errors, and subsequent test failures.
@@ -179,7 +179,7 @@ but remember that there's a startup cost to pay in that case (see above
Starting with Tiger (Mac OS X 10.4), Apple shipped broken locale files for
the eu_ES locale (Basque-Spain). In previous releases of Perl, this resulted in
-failures in the C<lib/locale> test. These failures have been supressed
+failures in the C<lib/locale> test. These failures have been suppressed
in the current release of Perl by making the test ignore the broken locale.
If you need to use the eu_ES locale, you should contact Apple support.
View
2 README.netware
@@ -64,7 +64,7 @@ Example:
The make process runs only under WinNT shell. The NetWare makefile is
located under the NetWare folder. This makes use of miniperl.exe to
run some of the Perl scripts. To create miniperl.exe, first set the
-required paths for Visual c++ compilier (specify vcvars32 location) at
+required paths for Visual c++ compiler (specify vcvars32 location) at
the command prompt. Then run nmake from win32 folder through WinNT
command prompt. The build process can be stopped after miniperl.exe
is created. Then run nmake from NetWare folder through WinNT command
View
2 README.openbsd
@@ -14,7 +14,7 @@ version 5 (hereafter just Perl) is compiled and/or runs.
=head2 OpenBSD core dumps from getprotobyname_r and getservbyname_r with ithreads
When Perl is configured to use ithreads, it will use re-entrant library calls
-in preference to non-re-entrant versions. There is an incompatability in
+in preference to non-re-entrant versions. There is an incompatibility in
OpenBSD's C<getprotobyname_r> and C<getservbyname_r> function in versions 3.7
and later that will cause a SEGV when called without doing a C<bzero> on
their return structs prior to calling these functions. Current Perl's
View
6 README.os2
@@ -487,7 +487,7 @@ DPMI is required for RSX.
The whole idea of the "standard C API to start applications" is that
the forms C<foo> and C<"foo"> of program arguments are completely
-interchangable. F<find> breaks this paradigm;
+interchangeable. F<find> breaks this paradigm;
find "pattern" file
find pattern file
@@ -1649,7 +1649,7 @@ leaves drive as it is.
=item C<Cwd::change_drive(name)>
-chanes the "current" drive.
+changes the "current" drive.
=item C<Cwd::sys_is_absolute(name)>
@@ -1896,7 +1896,7 @@ _DLLInitTerm() (e.g., F<TCP32IP>). This means that even if you do not I<call>
any function in the DLL, just the act of loading this DLL will reset your
flags. What is worse, the same compiler was used to compile some HOOK DLLs.
Given that HOOK dlls are executed in the context of I<all> the applications
-in the system, this means a complete unpredictablity of floating point
+in the system, this means a complete unpredictability of floating point
flags on systems using such HOOK DLLs. E.g., F<GAMESRVR.DLL> of B<DIVE>
origin changes the floating point flags on each write to the TTY of a VIO
(windowed text-mode) applications.
View
2 README.os390
@@ -260,7 +260,7 @@ from an account with write access to the directory entry for /tmp.
Out of Memory!
-Recent perl test suite is quite memory hunrgy. In addition to the comments
+Recent perl test suite is quite memory hungry. In addition to the comments
above on memory limitations it is also worth checking for _CEE_RUNOPTS
in your environment. Perl now has (in miniperlmain.c) a C #pragma
to set CEE run options, but the environment variable wins.
View
4 README.solaris
@@ -39,7 +39,7 @@ these modules is available on CPAN under the Sun::Solaris:: namespace.
Solaris may include two versions of perl, e.g. Solaris 9 includes
both 5.005_03 and 5.6.1. This is to provide stability across Solaris
releases, in cases where a later perl version has incompatibilities
-with the version included in the preceeding Solaris release. The
+with the version included in the preceding Solaris release. The
default perl version will always be the most recent, and in general
the old version will only be retained for one Solaris release. Note
also that the default perl will NOT be configured to search for modules
@@ -213,7 +213,7 @@ details.
=head3 GNU as and GNU ld
The following information applies to gcc version 2. Volunteers to
-update it as appropropriate for gcc version 3 would be appreciated.
+update it as appropriately for gcc version 3 would be appreciated.
The versions of as and ld supplied with Solaris work fine for building
perl. There is normally no need to install the GNU versions to
View
2 README.symbian
@@ -243,7 +243,7 @@ the "Oneliner" allows one to type in Perl code, and the "Run"
opens a file chooser for selecting a Perl file to run.
The PerlApp also is started when the "Perl recognizer" (also included
-and installed) detects a Perl file being activated througg the GUI,
+and installed) detects a Perl file being activated through the GUI,
and offers either to install it under \Perl (if the Perl file is in
the inbox of the messaging application) or to run it (if the Perl file
is under \Perl).
View
2 README.vms
@@ -152,7 +152,7 @@ underscores and the tests will have difficulty finding them. So your
best bet is to unpack the Perl source kit on an ODS-5 volume using
recent versions of vmstar (e.g. V3.4 or later). Contrary to advice
provided with previous versions of Perl, do I<not> use the ODS-2
-compatability qualifier. Instead, use a command like the following:
+compatibility qualifier. Instead, use a command like the following:
vmstar -xvf perl-5^.13^.8.tar

0 comments on commit f858446

Please sign in to comment.
Something went wrong with that request. Please try again.