From 78080fda0fa69d49127a5477c1a574603108e1d9 Mon Sep 17 00:00:00 2001 From: Jacob Overgaard <752371+iOvergaard@users.noreply.github.com> Date: Mon, 13 Jan 2025 15:06:22 +0100 Subject: [PATCH] docs: update the code snippet for localization where `localizations` is the correct property to use --- .../extension-types/localization.md | 10 +++++----- .../extension-types/localization.md | 12 ++++++------ 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/14/umbraco-cms/customizing/extending-overview/extension-types/localization.md b/14/umbraco-cms/customizing/extending-overview/extension-types/localization.md index edc73016968..ce00024f8d4 100644 --- a/14/umbraco-cms/customizing/extending-overview/extension-types/localization.md +++ b/14/umbraco-cms/customizing/extending-overview/extension-types/localization.md @@ -48,7 +48,7 @@ export default { The sections and keys will be formatted into a map in Umbraco with the format `section_key1` and `section_key2.` These form the unique key they are requested. -If you do not have many translations, you can also choose to include them directly in the meta-object: +If you do not have many translations, you can also choose to include them directly in the meta-object using the `localizations` property: {% code title="umbraco-package.json" %} ```json @@ -62,10 +62,10 @@ If you do not have many translations, you can also choose to include them direct "meta": { "culture": "en", "localizations": { - "section": { - "key1": "value1", - "key2": "value2" - } + "section": { + "key1": "value1", + "key2": "value2" + } } }, } diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/localization.md b/15/umbraco-cms/customizing/extending-overview/extension-types/localization.md index a56a00f9a97..ce00024f8d4 100644 --- a/15/umbraco-cms/customizing/extending-overview/extension-types/localization.md +++ b/15/umbraco-cms/customizing/extending-overview/extension-types/localization.md @@ -48,7 +48,7 @@ export default { The sections and keys will be formatted into a map in Umbraco with the format `section_key1` and `section_key2.` These form the unique key they are requested. -If you do not have many translations, you can also choose to include them directly in the meta-object: +If you do not have many translations, you can also choose to include them directly in the meta-object using the `localizations` property: {% code title="umbraco-package.json" %} ```json @@ -61,11 +61,11 @@ If you do not have many translations, you can also choose to include them direct "name": "English", "meta": { "culture": "en", - "translations": { - "section": { - "key1": "value1", - "key2": "value2" - } + "localizations": { + "section": { + "key1": "value1", + "key2": "value2" + } } }, }