From d091fc3c036a7f71f3f94901b85769c17c6e0d85 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Yann=20C=C3=A9bron?= <yann.cebron@jetbrains.com>
Date: Tue, 3 Dec 2024 14:29:11 +0100
Subject: [PATCH] providing_translations.md: minor

---
 .../localization/providing_translations.md    | 27 +++++++++++++------
 1 file changed, 19 insertions(+), 8 deletions(-)

diff --git a/topics/reference_guide/localization/providing_translations.md b/topics/reference_guide/localization/providing_translations.md
index 96a653fc6..360f468c9 100644
--- a/topics/reference_guide/localization/providing_translations.md
+++ b/topics/reference_guide/localization/providing_translations.md
@@ -75,17 +75,31 @@ Proper localization files will be used at runtime depending on the [IDE language
 
 ### Bundled Translations Structure
 
-Translations for a specific language can be organized in two ways:
-- Language directory: <path>/localization/\$LANGUAGE_CODE\$/\$REGION_CODE\$</path> (`$REGION_CODE$` level is optional).
-  Example:
+Translations for a specific language can be organized in two ways as shown below.
+The proper directory layout/filename suffixes is the only thing needed for the translations to work.
+No additional actions like registering EPs are needed.
+
+#### Language Directory
+
+Translated resources are stored in a dedicated directory structure.
+
+<path>/localization/\$LANGUAGE_CODE\$/\$REGION_CODE\$</path> (`$REGION_CODE$` level is optional).
+
+Example:
   - Original template description:
 
     <path>/fileTemplates/code/JavaDoc Class.java.html</path>
   - Translated template description: <path></path>
 
     <path>/localization/zh/CN/fileTemplates/code/JavaDoc Class.java.html</path>
-- Localization suffix in filename: <path>/intentionDescriptions/QuickEditAction/description_\$LANGUAGE_CODE\$_\$REGION_CODE\$.html</path>.
-  Example:
+
+#### Localization Suffix in Filename
+
+Translated resources are stored in files with dedicated filename.
+
+<path>/intentionDescriptions/QuickEditAction/description_\$LANGUAGE_CODE\$_\$REGION_CODE\$.html</path>
+
+Example:
   - Original template description:
 
     <path>/intentionDescriptions/QuickEditAction/description.html</path>
@@ -93,9 +107,6 @@ Translations for a specific language can be organized in two ways:
 
     <path>/intentionDescriptions/QuickEditAction/description_zh_CN.html</path>
 
-The proper directory layout/filename suffixes is the only thing needed for the translations to work.
-No additional actions like registering EPs are needed.
-
 ## Translated Elements
 
 The following table contains the possible translated elements and information about their support in language packs and IDE/plugins.