bitbake.conf: Tidy up a few comment typoes; no functional changes.

(From OE-Core rev: 935a7f3847bd86ed78418db5cb6dd98ac0b6e65d)

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 4 insertions, 4 deletions

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 9377ee6ba1..f6d6f7dc3b 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -368,7 +368,7 @@ DEPLOY_DIR_TOOLS = "${DEPLOY_DIR}/tools"
 PKGDATA_DIR = "${TMPDIR}/pkgdata/${MULTIMACH_TARGET_SYS}"
 
 ##################################################################
-# SDK variables, 
+# SDK variables.
 ##################################################################
 
 SDK_NAME_PREFIX ?= "oecore"
@@ -395,9 +395,9 @@ IMAGE_LINK_NAME = "${IMAGE_BASENAME}-${MACHINE}"
 # This option allows for a percentage overage of the actual image size rather than a
 # fixed extra space, this is space needed for initial startup and basic operations.
 IMAGE_OVERHEAD_FACTOR ?= "1.3"
-# This option allow for adding addition space in K above and beyond what the 
+# This option allows for adding additional space in K above and beyond what the 
 # IMAGE_OVERHEAD_FACTOR might add. This space is for additional packages, user data, ...
-# To set a fixed size then overrideing IMAGE_ROOTFS_SIZE with the max size one wants
+# To set a fixed size then overriding IMAGE_ROOTFS_SIZE with the max size one wants
 # should do the trick
 IMAGE_ROOTFS_EXTRA_SPACE ?= "0"
 
@@ -418,7 +418,7 @@ CCACHE ??= ""
 # Disable ccache explicitly if CCACHE is null since gcc may be a symlink
 # of ccache some distributions (e.g., Fedora 17).
 export CCACHE_DISABLE ??= "${@[0,1][d.getVar('CCACHE', True) == '']}"
-# Assign CCACHE_DIR a default vaule to fix a bug of ccache 3.1.7,
+# Assign CCACHE_DIR a default value to fix a bug of ccache 3.1.7,
 # since it would always create CCACHE_DIR/.ccache even if
 # CCACHE_DISABLE = 1.
 export CCACHE_DIR ??= "${@os.getenv('HOME')}"