bitbake-user-manual: replace "file name" by "filename"
PATCH 1/1 bitbake-user-manual: replace "file name" by "filename"
There are many more instances of "filename" or "filenames" than of "file name" or "file names".
The winner takes it all!
Signed-off-by Michael Opdenacker <[email protected]>
--- doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 2 +- doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
doc/bitbake-user-manual/bitbake-user-manual-metadata.rst +1 -1
@@ -1941,7 +1941,7 @@ Wildcard Support in Variables ============================= Support for wildcard use in variables varies depending on the context in -which it is used. For example, some variables and file names allow +which it is used. For example, some variables and filenames allow limited use of wildcards through the "``%``" and "``*``" characters. Other variables or names support Python's `glob <https://docs.python.org/3/library/glob.html>`_ syntax,
doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst +2 -2
@@ -335,7 +335,7 @@ overview of their function and contents. :term:`BB_LOGFMT` Specifies the name of the log files saved into ``${``\ :term:`T`\ ``}``. By default, the :term:`BB_LOGFMT` - variable is undefined and the log file names get created using the + variable is undefined and the log filenames get created using the following form:: log.{task}.{pid}
@@ -389,7 +389,7 @@ overview of their function and contents. :term:`BB_RUNFMT` Specifies the name of the executable script files (i.e. run files) saved into ``${``\ :term:`T`\ ``}``. By default, the - :term:`BB_RUNFMT` variable is undefined and the run file names get + :term:`BB_RUNFMT` variable is undefined and the run filenames get created using the following form:: run.{task}.{pid}
Signature · 1 line
2.25.1