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: `<parent_theme_dir>/<Vendor>_<Module>/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: `<module_dir>/view/base/layout/`
-    *  Layout files for the `frontend` area: `<module_dir>/view/frontend/layout/`
+   *  Layout files for the `base` area: `<module_dir>/view/base/layout/`
+   *  Layout files for the `frontend` area: `<module_dir>/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.