Fix "can not" in Documentation and Kconfig

Randy brought it to my attention that in proper english "can not" should always
be written "cannot". I donot see any reason to argue, even if I mightnot
understand why this rule exists.  This patch fixes "can not" in several
Documentation files as well as three Kconfigs.

Signed-off-by: Matt LaPlante <[email protected]>
Acked-by: Randy Dunlap <[email protected]>
Signed-off-by: Adrian Bunk <[email protected]>
This commit is contained in:
Matt LaPlante 2006-10-03 22:53:09 +02:00 • committed by Adrian Bunk
commit 84eb8d0608
24 changed files with 31 additions and 31 deletions

View file

@ -92,7 +92,7 @@ config HAVE_MEMORY_PRESENT
#
# SPARSEMEM_EXTREME (which is the default) does some bootmem
# allocations when memory_present() is called. If this can not
# allocations when memory_present() is called. If this cannot
# be done on your architecture, select this option. However,
# statically allocating the mem_section[] array can potentially
# consume vast quantities of .bss, so be careful.