From c009897aeec4ac3265498664937b2b86870b9984 Mon Sep 17 00:00:00 2001 From: "Yann E. MORIN\"" Date: Sun, 17 Jul 2011 16:53:40 +0200 Subject: misc: fix more typos here and there... Reported-by: "Antony N. Pavlov" Signed-off-by: "Yann E. MORIN" --- scripts/crosstool-NG.sh.in | 6 +++--- scripts/patch-rework.sh | 2 +- scripts/populate.in | 2 +- scripts/showSamples.sh | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) (limited to 'scripts') diff --git a/scripts/crosstool-NG.sh.in b/scripts/crosstool-NG.sh.in index be51e074..509a74ba 100644 --- a/scripts/crosstool-NG.sh.in +++ b/scripts/crosstool-NG.sh.in @@ -25,7 +25,7 @@ . .config.2 # Yes! We can do full logging from now on! -# Overide the locale early, in case we ever translate crosstool-NG messages +# Override the locale early, in case we ever translate crosstool-NG messages if [ -z "${CT_NO_OVERIDE_LC_MESSAGES}" ]; then export LC_ALL=C export LANG=C @@ -79,12 +79,12 @@ esac # Check the user is using an existing SHELL to be used by ./configure and Makefiles CT_TestOrAbort "The CONFIG_SHELL '${CT_CONFIG_SHELL}' (${CT_SHELL}) is not valid" -f "${CT_SHELL}" -a -x "${CT_SHELL}" -# Create the bin-overide early +# Create the bin-override early # Contains symlinks to the tools found by ./configure # Note: CT_DoLog and CT_DoExecLog do not use any of those tool, so # they can be safely used CT_TOOLS_OVERIDE_DIR="${CT_WORK_DIR}/tools" -CT_DoLog DEBUG "Creating bin-overide for tools in '${CT_TOOLS_OVERIDE_DIR}'" +CT_DoLog DEBUG "Creating bin-override for tools in '${CT_TOOLS_OVERIDE_DIR}'" CT_DoExecLog DEBUG mkdir -p "${CT_TOOLS_OVERIDE_DIR}/bin" cat "${CT_LIB_DIR}/paths.mk" |while read trash line; do tool="${line%%=*}" diff --git a/scripts/patch-rework.sh b/scripts/patch-rework.sh index 9b9f9127..3d97795d 100755 --- a/scripts/patch-rework.sh +++ b/scripts/patch-rework.sh @@ -123,7 +123,7 @@ $1=="+++" && mark==1 { nextfile; } read -p " --> enter patch depth (or Ctrl-C to abort): " d fi - # Store the original list of fiels touched by the patch, + # Store the original list of files touched by the patch, # removing the $d leading components sed -r -e "s:^([^/]+/){${d}}::;" "../diffstat.orig" >"${dst}/${pname}.diffstat.orig" diff --git a/scripts/populate.in b/scripts/populate.in index 02b17972..5d8f5956 100644 --- a/scripts/populate.in +++ b/scripts/populate.in @@ -83,7 +83,7 @@ OPTIONS If the destination root directory exists, then the content of the source root directory is copied in there, and the result is populated as usual. - It can be usefull if constructing a rootfs incrementally from many + It can be useful if constructing a rootfs incrementally from many smaller source root directories, or if your destination root directory is an NFS export that your target mounts as / (and you don't want to re-run exportfs -av everytime). USE WITH CARE! diff --git a/scripts/showSamples.sh b/scripts/showSamples.sh index d96d0c59..e510b3da 100755 --- a/scripts/showSamples.sh +++ b/scripts/showSamples.sh @@ -184,7 +184,7 @@ for sample in "${@}"; do done if [ "${opt}" = -w ]; then - printf "^ Total: ${#@} samples || **X**: sample uses features marked as being EXPERIMENTAL.\\\\\\\\ **B**: sample is curently BROKEN. |||||||||||||" + printf "^ Total: ${#@} samples || **X**: sample uses features marked as being EXPERIMENTAL.\\\\\\\\ **B**: sample is currently BROKEN. |||||||||||||" echo "" elif [ -z "${opt}" ]; then echo ' L (Local) : sample was found in current directory' -- cgit v1.2.3