Thanks, applied as 945f720225974b71819a7a940886e7d23ef29b1d. Michael
[sent from post-receive hook] On Tue, 03 Jun 2025 12:38:48 +0200, Markus Heidelberg <[email protected]> wrote: > Signed-off-by: Markus Heidelberg <[email protected]> > Reviewed-by: Alexander Dahl <[email protected]> > Message-Id: <[email protected]> > Signed-off-by: Michael Olbrich <[email protected]> > > diff --git a/doc/daily_work.inc b/doc/daily_work.inc > index b335b2e6b174..f16cd490c614 100644 > --- a/doc/daily_work.inc > +++ b/doc/daily_work.inc > @@ -98,7 +98,7 @@ config file**). > Work Flow > ~~~~~~~~~ > > -Now its up to ourself working on the GIT based kernel source tree and > +Now it's up to ourself working on the GIT based kernel source tree and > using PTXdist to include the kernel into the root filesystem. > > To configure the kernel source tree, we simply run: > @@ -1479,7 +1479,7 @@ be built at the same time but should contain a > different packages list each > (refer :ref:`multi_image_individual_root_filesystems` for details). > > Marking a menu file based dependency with ``if BUILDTIME`` limits the > dependency > -to compile-time only. In this case its possible to have the package in one > +to compile-time only. In this case it's possible to have the package in one > image's list, but not its dependency. > > Run-Time only Dependency > diff --git a/doc/ref_make_variables.rst b/doc/ref_make_variables.rst > index e89c0e56c5fb..807ed5db051d 100644 > --- a/doc/ref_make_variables.rst > +++ b/doc/ref_make_variables.rst > @@ -376,7 +376,7 @@ Build Environment for all Stages > wrappers. The specified flags are added to the command line when > appropriate. In most cases this it the preferred way to add additional > flags. Adding them via environment variables or ``make`` arguments can > - have unexpected side effects, such as as overwriting existing defaults. > + have unexpected side effects, such as overwriting existing defaults. > > ``<PKG>_FLAGS_BLACKLIST`` > A list of arbitrary flags. If any one of these flags is found as an > @@ -536,7 +536,7 @@ different. > ptxdist packages (the lowercase name of the packages). PTXdist will add > the necessary dependencies. > > - Note that this will not ensure that the packages are enabled or that all > + Note that this will not ensure that the packages are enabled or that > all package dependencies are satisfied. ``$(PTX_PACKAGES_INSTALL)`` can > be used to specify all enabled packages. Or ``$(call ptx/collection, > $(PTXDIST_WORKSPACE)/configs/<collection-file-name>)`` can be used to > diff --git a/doc/ref_rule_file_layout.rst b/doc/ref_rule_file_layout.rst > index 222ee46a7b29..19b8dae52b22 100644 > --- a/doc/ref_rule_file_layout.rst > +++ b/doc/ref_rule_file_layout.rst > @@ -117,7 +117,7 @@ which looks like this: > What ``world/prepare`` does depends on some variable settings. > > If the package’s rule file defines ``<PKG>_CONF_TOOL`` to ``NO``, > -this stage is simply does nothing. > +this stage simply does nothing. > > All rules files can create the ``<PKG>_CONF_ENV`` variable and should > define it at least to ``$(CROSS_ENV)`` (the default) if the prepare stage > diff --git a/scripts/lib/ptxd_make_image_archive.sh > b/scripts/lib/ptxd_make_image_archive.sh > index 053020fa4859..f4c689d58964 100644 > --- a/scripts/lib/ptxd_make_image_archive.sh > +++ b/scripts/lib/ptxd_make_image_archive.sh > @@ -7,7 +7,7 @@ > # > > # > -# extract ipkg an generate a tgz image > +# extract ipkg and generate a tgz image > # > ptxd_make_image_archive_impl() { > ptxd_make_image_init && > diff --git a/scripts/lib/ptxd_make_image_genimage.sh > b/scripts/lib/ptxd_make_image_genimage.sh > index cd7058bfcb96..58804a743fe0 100644 > --- a/scripts/lib/ptxd_make_image_genimage.sh > +++ b/scripts/lib/ptxd_make_image_genimage.sh > @@ -48,7 +48,7 @@ ptxd_make_image_genimage_config() { > export -f ptxd_make_image_genimage_config > > # > -# extract ipkg an generate a tgz image > +# extract ipkg and generate a tgz image > # > ptxd_make_image_genimage_impl() { > local tmpdir configdir file
