From 7068ab6d3ea3c3ce18fac432b42db27a432c04f1 Mon Sep 17 00:00:00 2001 From: Dmytro Shevtsov Date: Mon, 22 Feb 2021 10:05:00 -0600 Subject: [PATCH] Fix Markdown --- src/guides/v2.3/frontend-dev-guide/themes/theme-inherit.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/guides/v2.3/frontend-dev-guide/themes/theme-inherit.md b/src/guides/v2.3/frontend-dev-guide/themes/theme-inherit.md index 3c908585589..ac72d9d3bc2 100644 --- a/src/guides/v2.3/frontend-dev-guide/themes/theme-inherit.md +++ b/src/guides/v2.3/frontend-dev-guide/themes/theme-inherit.md @@ -134,8 +134,8 @@ The layouts processing mechanism does not involve fallback. The system collects 1. Ancestor theme layouts, starting from the most distant ancestor, recursively until a theme with no parent is reached: `/_/layout/` 1. All module layout files in sequence, defined in `app/etc/config.php` respecting the component load order. For each module: - * Layout files for the `base` area: `/view/base/layout/` - * Layout files for the `frontend` area: `/view/frontend/layout/` + * Layout files for the `base` area: `/view/base/layout/` + * Layout files for the `frontend` area: `/view/frontend/layout/` Unlike templates or images, layout can be not only overridden, but also extended. And the recommended way to customize layout is to extend it by creating theme extending layout files.