Update project paths article

Author: ilyaspiridonov

project_paths.md

@@ -3,48 +3,83 @@
 To make sure GitLocalize knows where to look for translatable files and where to put translations, you should configure Project Paths correctly.
 
 
-## Default Paths Configuation
+## Default Configuation for the Project Paths
 
 The default paths offered when creating a project look as follows:
 
-Source Path:
+*Source Path:*
 
 ```
 [repo_name]/
 ```
 
-Target Path:
+*Target Path:*
 
 ```
 [repo_name]/%lang%
 ```
-Where `%lang` is the placeholder for the target language code.
+...where `%lang` is the placeholder for the target language code.
 
-With this configuration GitLocalize will scan all folders in the repository starting from the root folder
-(including subfolders) to look for translatable files. Translation files will be created in the respective folders for each target language. For example, Korean translations will be stored in `/ko/...` German translations will be stored in `/de/...` etc.
-Additionally, GitLocalize will look for existing translations in the same folders (scanning `/ko/...` for Korean translations, `/de/...` for German etc.)
+With this configuration GitLocalize will scan all folders starting from the root folder
+(including subfolders) to look for translatable files. Output translation files will be created in the respective folders for each target language. For example, Korean translations will be stored under `/ko/...`, German translations will be stored under `/de/...` etc.
+
+GitLocalize will additionally look for existing translations in the same language locations (will scan `/ko/...` for Korean translations, `/de/...` for German etc.)
 
 ## Custom Project Paths
 
-You can specify one or multiple custom paths to make GitLocalize look for files in specific locations. Below are some examples.
+To make GitLocalize look for translatable files in specific locations, you can specify one or more custom paths.
+
+### Directory-Based Paths
 
-## Directory-Based Paths
-_Examples:_
+_Example:_
 
-Source Path:
+*Source Path:*
 ```
 [repo_name]/src/site/content/en
 ```
 
-Target Path:
+*Target Path:*
 
 ```
 [repo_name]/src/site/content/translations-%lang%
 ```
 
-With this configuration GitLocalize will look for translatable files in `/src/site/content/en`, Korean translations in `/src/site/content/translations-ko`, German translations in `/src/site/content/translations-de` etc. Output translations will be created in the same locations (`/src/site/content/translations-ko`,  `/src/site/content/translations-de` etc.)
+With this configuration GitLocalize will look for translatable files under `/src/site/content/en`, Korean translations under `/src/site/content/translations-ko`, German translations under `/src/site/content/translations-de` etc. Output translations will be created in the same locations (`/src/site/content/translations-ko`,  `/src/site/content/translations-de` etc.)
+
+### File-Based Paths
+
+_Example:_
+
+*Source Path:*
+
+```
+pages/translations/en/LC_MESSAGES/messages.po
+```
+
+*Target Path:*
+
+```
+pages/translations/%lang%/LC_MESSAGES/messages.po
+```
+
+### Mixed-Type Paths
+
+_Example:_
+
+*Source Path:*
+```
+pages/content/amp-dev/documentation/guides-and-tutorials
+```
+
+*Target Path:*
+
+```
+%file_name%@%lang%.%file_ext%
+```
+
+This configuration will sync source files from the `guides-and-tutorials` directory, while output translation files will be created in the same directory with a language code in the filename (e.g. German translation for the file `a4a_spec.md` will be created in the same `guides-and-tutorials` directory under the `a4a_spec@de.md` filename).
 
-# Configuring Custom Language Codes
+## Configuring Custom Language Codes
 
-You can specify custom language codes for each project language when creating a project or later in the Manage Languages section. Language codes will affect the %lang% placeholder in the output paths (location where translation files will be created).
+Custom language codes can be specified for each project language when creating a project or later in the Manage Languages section. Language codes will replace the `%lang%` placeholder in the output paths (locations where translation files will be created).
 ![Project Paths](/assets/img/project_paths/project_paths.gif)