summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--Cross/Makefile-cross-SH4
-rw-r--r--Cross/README2
-rw-r--r--Cross/README.new2
-rw-r--r--Cross/build-arm-n770-sh2
-rwxr-xr-xCross/warp2
5 files changed, 6 insertions, 6 deletions
diff --git a/Cross/Makefile-cross-SH b/Cross/Makefile-cross-SH
index 6e792e197f..21f83275eb 100644
--- a/Cross/Makefile-cross-SH
+++ b/Cross/Makefile-cross-SH
@@ -12,7 +12,7 @@ Makefile=Makefile-cross-$CROSS_NAME
# H.Merijn Brand [17 Feb 2004]
# This comment is just to ensure that Configure will find variables that
# are removed/replaced in patches on blead, but are still needed in the
-# 5.8.x, 5.6.x and 5.005.x maintainance tracks.
+# 5.8.x, 5.6.x and 5.005.x maintenance tracks.
# metaconfig -m will scan all .SH files on this level (not deeper), and
# not in x2p and other subfolders. This file is as good as any .SH
# patch references
@@ -1269,7 +1269,7 @@ etags: TAGS
TAGS: emacs/cperl-mode.elc
sh emacs/ptags
-# Let's hope make will not go into an infinite loop on case-unsensitive systems
+# Let's hope make will not go into an infinite loop on case-insensitive systems
# This may also fail if . is in the head of the path, since perl will
# require -Ilib
tags: TAGS
diff --git a/Cross/README b/Cross/README
index 23a4ce8627..7b8ef48113 100644
--- a/Cross/README
+++ b/Cross/README
@@ -47,7 +47,7 @@ Other Targets (For Developers)
------------------------------
It is possible to extend the cross-compilation to other targets.
-We have sucessfully compiled for the target solaris2.8/x86
+We have successfully compiled for the target solaris2.8/x86
on linux/x86 build system.
To attempt a cross-compile for another target using the methods
diff --git a/Cross/README.new b/Cross/README.new
index bbdeeb4963..bcfa3b3e23 100644
--- a/Cross/README.new
+++ b/Cross/README.new
@@ -9,7 +9,7 @@ README.new - Cross-compilation for linux
=head1 DESCRIPTION
This is second approach to linux cross-compilation, which should allow
-building full perl and entensions for target platform. Cross-compilation
+building full perl and extensions for target platform. Cross-compilation
for linux uses similar approach and shares the same files as
cross-compilation for WinCE.
diff --git a/Cross/build-arm-n770-sh b/Cross/build-arm-n770-sh
index b3e6a67ca3..e8c9179df2 100644
--- a/Cross/build-arm-n770-sh
+++ b/Cross/build-arm-n770-sh
@@ -6,7 +6,7 @@
# to skip Configure/build for HOST miniperl, pass "noconf" argument to this script
# some trick is different, however - the file extension for objects files
-# are choosen to be .${CROSS_NAME}, .armo in our case
+# are chosen to be .${CROSS_NAME}, .armo in our case
# note how invoked Makefile.PL for cross-compilation:
# miniperl -MCross Makefile.PL
diff --git a/Cross/warp b/Cross/warp
index 69cffeeada..fe928deff0 100755
--- a/Cross/warp
+++ b/Cross/warp
@@ -1,7 +1,7 @@
#!/bin/sh -x
## This script contains an rm -rf. This may alarm you.
-## These directories need to be reccursively deleted.
+## These directories need to be recursively deleted.
## I don't see any method of making "Bad Things"[tm]
## Happen. But we don't run buildroot as root do we? :-)