docs: kconfig: Fix grammar and formatting

- Remove unnecessary spaces
- Fix grammar s/to solution/solution/

Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
This commit is contained in:
Thorsten Blum 2024-02-10 16:20:04 +01:00 committed by Masahiro Yamada
parent 3b9ab248bc
commit 6388cfd0e6

View File

@ -16,13 +16,13 @@
# that are possible for CORE. So for example if CORE_BELL_A_ADVANCED is 'y', # that are possible for CORE. So for example if CORE_BELL_A_ADVANCED is 'y',
# CORE must be 'y' too. # CORE must be 'y' too.
# #
# * What influences CORE_BELL_A_ADVANCED ? # * What influences CORE_BELL_A_ADVANCED?
# #
# As the name implies CORE_BELL_A_ADVANCED is an advanced feature of # As the name implies CORE_BELL_A_ADVANCED is an advanced feature of
# CORE_BELL_A so naturally it depends on CORE_BELL_A. So if CORE_BELL_A is 'y' # CORE_BELL_A so naturally it depends on CORE_BELL_A. So if CORE_BELL_A is 'y'
# we know CORE_BELL_A_ADVANCED can be 'y' too. # we know CORE_BELL_A_ADVANCED can be 'y' too.
# #
# * What influences CORE_BELL_A ? # * What influences CORE_BELL_A?
# #
# CORE_BELL_A depends on CORE, so CORE influences CORE_BELL_A. # CORE_BELL_A depends on CORE, so CORE influences CORE_BELL_A.
# #
@ -34,7 +34,7 @@
# the "recursive dependency detected" error. # the "recursive dependency detected" error.
# #
# Reading the Documentation/kbuild/Kconfig.recursion-issue-01 file it may be # Reading the Documentation/kbuild/Kconfig.recursion-issue-01 file it may be
# obvious that an easy to solution to this problem should just be the removal # obvious that an easy solution to this problem should just be the removal
# of the "select CORE" from CORE_BELL_A_ADVANCED as that is implicit already # of the "select CORE" from CORE_BELL_A_ADVANCED as that is implicit already
# since CORE_BELL_A depends on CORE. Recursive dependency issues are not always # since CORE_BELL_A depends on CORE. Recursive dependency issues are not always
# so trivial to resolve, we provide another example below of practical # so trivial to resolve, we provide another example below of practical