- list defaults for BR2_GNU_TARGET_SUFFIX in help text

- fix a few typos

diff --git a/Config.in b/Config.in
index 5b73918bcec3ab261766f6d8e5e8aad69ec96eef..4376364987081987b7603c29a7a23a0873b70864 100644 (file)
--- a/Config.in
+++ b/Config.in
@@ -41,7 +41,7 @@ config BR2_x86_64
 endchoice
 
 #
-# Keep the variants seperate, there's no need to clutter everything else.
+# Keep the variants separate, there's no need to clutter everything else.
 # sh is fairly "special" in this regard, as virtually everyone else has
 # things kept down to a _sensible_ number of target variants. No such
 # luck for sh..
@@ -259,11 +259,15 @@ config BR2_GNU_TARGET_SUFFIX
            other users (most notably ARM EABI) like to add on to this in
            order to stay in line with gcc conventions.
 
+           Default options are:
+             linux-uclibcgnueabi for ARM EABI
+             linux-uclibc for the rest
+
 config BR2_JLEVEL
        int "Number of jobs to run simultaneously"
        default "1"
        help
-           Number of jobs to run simultanesouly
+           Number of jobs to run simultaneously
 
 endmenu
 

diff --git a/package/config/Kconfig-language.txt b/package/config/Kconfig-language.txt
index da51c0e7c19b9c46e6688da8ec447acccf7c8115..d78969e32cf154ce00109eacf101eb597840fcbb 100644 (file)
--- a/package/config/Kconfig-language.txt
+++ b/package/config/Kconfig-language.txt
@@ -110,7 +110,7 @@ applicable everywhere (see syntax).
   the indentation level, this means it ends at the first line which has
   a smaller indentation than the first line of the help text.
   "---help---" and "help" do not differ in behaviour, "---help---" is
-  used to help visually seperate configuration logic from help within
+  used to help visually separate configuration logic from help within
   the file as an aid to developers.
 
 

diff --git a/target/device/Sharp/LNode80/kernel-patches/001-patch-2.4.26-vrs1 b/target/device/Sharp/LNode80/kernel-patches/001-patch-2.4.26-vrs1
index 1e19599098a84d199980c90ff06469a22031f470..590da35f2ed1c78a440dc944f528bb5aafe5c7fb 100644 (file)
--- a/target/device/Sharp/LNode80/kernel-patches/001-patch-2.4.26-vrs1
+++ b/target/device/Sharp/LNode80/kernel-patches/001-patch-2.4.26-vrs1
@@ -1515,7 +1515,7 @@ diff -urN linux-2.4.26/Documentation/cpufreq-old linux-2.4.26-vrs1/Documentation
 +
 +CPUFreq architecture drivers are the pieces of kernel code that
 +actually perform CPU frequency transitions. These need to be
-+initialised seperately (seperate initcalls), and may be
++initialised separately (separate initcalls), and may be
 +modularized. They interact with the CPUFreq core in the following way:
 +
 +
@@ -20140,7 +20140,7 @@ diff -urN linux-2.4.26/drivers/char/clps711x_keyb.c linux-2.4.26-vrs1/drivers/ch
 + * Basic Function:
 + *
 + * Basicly the driver is interrupt driven. It sets all column drivers 
-+ * high. If any key is pressed, a interrupt occures. Now a seperate scan of
++ * high. If any key is pressed, a interrupt occures. Now a separate scan of
 + * each column is done. This scan is timer based, because we use a keyboard 
 + * interface with decoupling capacitors (neccecary if you want to survive 
 + * EMC compliance tests). Always one line is set high. When next timer event 
@@ -20150,7 +20150,7 @@ diff -urN linux-2.4.26/drivers/char/clps711x_keyb.c linux-2.4.26-vrs1/drivers/ch
 + * pressed. If any is pressed we reschedule the scan within a programmable
 + * delay. If we would switch back to interrupt mode as long as a key is pressed,
 + * we come right back to the interrupt, because the int. is level triggered !
-+ * The timer based scan of the seperate columns can also be done in one
++ * The timer based scan of the separate columns can also be done in one
 + * timer event (set fastscan to 1).
 + *
 + * Summary: