diff options
Diffstat (limited to 'config/global')
| -rw-r--r-- | config/global/download.in | 6 | ||||
| -rw-r--r-- | config/global/extract.in | 10 | ||||
| -rw-r--r-- | config/global/paths.in | 6 |
3 files changed, 11 insertions, 11 deletions
diff --git a/config/global/download.in b/config/global/download.in index d128866..b678374 100644 --- a/config/global/download.in +++ b/config/global/download.in @@ -23,7 +23,7 @@ config FORCE_DOWNLOAD help Force downloading tarballs, even if one already exists. - Usefull if you suspect a tarball to be damaged. + Useful if you suspect a tarball to be damaged. config USE_MIRROR bool @@ -43,7 +43,7 @@ config PREFER_MIRROR bool prompt "Prefer the mirror" help - Say 'Y' here if you prefer the LAN miror over the upstream sources. + Say 'Y' here if you prefer the LAN mirror over the upstream sources. config MIRROR_BASE_URL string @@ -93,6 +93,6 @@ config ONLY_DOWNLOAD help Only download the tarballs. Exit once it done. - Usefull to pre-retrieve the tarballs before going off-line. + Useful to pre-retrieve the tarballs before going off-line. endif # ! FORBID_DOWNLOAD diff --git a/config/global/extract.in b/config/global/extract.in index 3f45ec0..2599faa 100644 --- a/config/global/extract.in +++ b/config/global/extract.in @@ -6,9 +6,9 @@ config FORCE_EXTRACT bool prompt "Force extractions" help - Force extraction of already exctracted tarballs. + Force extraction of already extracted tarballs. - Usefull if you suspect a previous extract did not complete (eg. broken + Useful if you suspect a previous extract did not complete (eg. broken tarball), or you added a new set of patches for this component. config OVERIDE_CONFIG_GUESS_SUB @@ -37,7 +37,7 @@ config ONLY_EXTRACT help Exit after unpacking and patching tarballs. - Usefull to look at the code before doing the build itself. + Useful to look at the code before doing the build itself. choice prompt "Patches origin" @@ -97,7 +97,7 @@ config PATCH_NONE help Don't use any patch at all. - Please be carefull if you select this. Most components do require + Please be careful if you select this. Most components do require patches to properly build. It can happen, however, that support for your architecture is clean enough that you can build a toolchain with no patch. But most probably, this is *not* the case. @@ -128,5 +128,5 @@ config LOCAL_PATCH_DIR help Enter the custom patch directory here. - Note that you must ensure that the directory contianing your custom + Note that you must ensure that the directory containing your custom patches is arranged the same way the official directory is. diff --git a/config/global/paths.in b/config/global/paths.in index 2a1fa67..f7766da 100644 --- a/config/global/paths.in +++ b/config/global/paths.in @@ -69,12 +69,12 @@ config RM_RF_PREFIX_DIR If you say 'y' here, then PREFIX_DIR (above) will be eradicated prior to the toolchain is built. - This can be usefull when you are trying different settings (due + This can be useful when you are trying different settings (due to build failures or feature tests). In this case, to avoid using a potentially broken previous toolchain, the install location is removed, to start afresh. - On the oher hand, if you are building a final toolchain, and install + On the other hand, if you are building a final toolchain, and install it into a directory with pre-install, unrelated programs, it would be damageable to remove that directory. In this case, you may want to say 'n' here. @@ -98,7 +98,7 @@ config INSTALL_DIR_RO Render the directory of the toolchain (and its sub-directories) read-only. - Usefull for toolchains destined for production. + Useful for toolchains destined for production. config STRIP_ALL_TOOLCHAIN_EXECUTABLES bool |