From 058d4c97e9ee46df2d5a347a5e0e6312672dd51b Mon Sep 17 00:00:00 2001 From: Marián Konček Date: Apr 12 2022 13:10:20 +0000 Subject: Fix typos --- diff --git a/modules/ROOT/pages/core-concepts/module-stream.adoc b/modules/ROOT/pages/core-concepts/module-stream.adoc index e2c8230..eb38d48 100644 --- a/modules/ROOT/pages/core-concepts/module-stream.adoc +++ b/modules/ROOT/pages/core-concepts/module-stream.adoc @@ -19,7 +19,7 @@ There are two basic types of modular metadata. The modulemd yaml file which we a NOTE: For the sake of space, both examples of module streams were shortened. For example a Perl module stream consists of 170-180 components. If you want to check out the un-shortened version please check the link:https://src.fedoraproject.org/modules/perl[Perl module dist-git repository]. -The specification of all the metadata formats used by Modularity can be found in link:https://github.com/fedora-modularity/libmodulemd/tree/main/yaml_specs[the libmodulemd git repository]. `libmodulemd` is a C library which provides an API (with python byndings) which enables us to work with module metadata. +The specification of all the metadata formats used by Modularity can be found in link:https://github.com/fedora-modularity/libmodulemd/tree/main/yaml_specs[the libmodulemd git repository]. `libmodulemd` is a C library which provides an API (with python bindings) which enables us to work with module metadata. === Input modulemd-packager @@ -127,7 +127,7 @@ data: <.> the definition of the type of modulemd yaml document <.> the name of the stream of a module stream <.> definition of context configurations for different releases or build options -<.> each name of a context is defined by the user and uniquely identifies the builtime and runtime configuration combination of a module stream +<.> each name of a context is defined by the user and uniquely identifies the buildtime and runtime configuration combination of a module stream <.> with modular dependencies a module stream can depend on other modules in buildtime or runtime <.> with a context configuration we can set options which we want to be passed done to the build process for all the components of module stream <.> profiles provide us with a feature to be able to install different combinations of components at runtime