diff --git a/doc/source/appdev-guide/app_migrating/app_migrate_to_newton.rst b/doc/source/appdev-guide/app_migrating/app_migrate_to_newton.rst index 258539f2c..cab73b22e 100644 --- a/doc/source/appdev-guide/app_migrating/app_migrate_to_newton.rst +++ b/doc/source/appdev-guide/app_migrating/app_migrate_to_newton.rst @@ -128,7 +128,7 @@ Previously murano used to load ``Objects`` and ``ObjectsCopy`` sections of the JSON object model independently which cause for objects that were not deleted between deployments to instantiate twice. If deleted object were to cause any changes to such alive objects they were made to the objects loaded from -``ObjectsCopy`` and immidiately discarded before the deployment. +``ObjectsCopy`` and immediately discarded before the deployment. Now this behaviour is changed and there is no more duplicates of the same object. Applications can also make use of the new features. Now it is possible to diff --git a/doc/source/enduser-guide/use_cli.rst b/doc/source/enduser-guide/use_cli.rst index 506084e0b..42dd6a881 100644 --- a/doc/source/enduser-guide/use_cli.rst +++ b/doc/source/enduser-guide/use_cli.rst @@ -569,7 +569,7 @@ appropriate values: Adds an application or multiple applications to the environment template. :command:`murano env-template-del-app ` - Deletes an application from the enviroment template. + Deletes an application from the environment template. :command:`murano env-template-list` Lists the environments templates. @@ -584,4 +584,4 @@ appropriate values: Deletes an environment template. .. seealso:: - `Application Catalog service command-line client `_. \ No newline at end of file + `Application Catalog service command-line client `_. diff --git a/releasenotes/notes/gc-collect-165e73bbaf345d74.yaml b/releasenotes/notes/gc-collect-165e73bbaf345d74.yaml index 8ee5350e6..8ecb6de15 100644 --- a/releasenotes/notes/gc-collect-165e73bbaf345d74.yaml +++ b/releasenotes/notes/gc-collect-165e73bbaf345d74.yaml @@ -9,5 +9,5 @@ features: destroyed before their parents and, when possible, before objects that are subscribed to their destruction notifications. - Internally, both pre-deployment garbage collection (that was done by - comparision of ``Objects`` and ``ObjectsCopy``) and post-deployment + comparison of ``Objects`` and ``ObjectsCopy``) and post-deployment orphan object collection are now done through the new GC.