docs(developer): add custom file format reference for crowdinType (#673)

Author: rohalskyy

src/content/docs/developer/modules/file-processing-modules/custom-file-format.mdx

@@ -61,11 +61,11 @@ For Crowdin Enterprise:
       </td>
     </tr>
     <tr>
-      <td><code>type</code></td>
+      <td><code id="custom-file-format-type-example">type</code></td>
       <td>
         <p><strong>Type:</strong> <code>string</code></p>
         <p><strong>Required:</strong> yes</p>
-        <p><strong>Description:</strong> The custom file format identifier. Can be used in API to force the processing of the files by the Custom file format app. If the <code>type</code> parameter is used in API, the <code>signaturePatterns</code> will be ignored.</p>
+        <p><strong>Description:</strong> The custom file format identifier. Can be used in API to force the processing of the files by the Custom file format app. If the <code>type</code> parameter is used in API, the <code>signaturePatterns</code> will be ignored. Values defined via this property can also be referenced by other modules, for example through <code>attributes.crowdinType</code> in the [File Post-Import Processing module](/developer/crowdin-apps-module-file-post-import-processing/).</p>
       </td>
     </tr>
     <tr>

src/content/docs/developer/modules/file-processing-modules/file-post-import-processing.mdx

@@ -301,8 +301,8 @@ Properties:
       <td><code class="whitespace-nowrap">attributes.crowdinType</code></td>
       <td>
         <p><strong>Type:</strong> <code>string</code></p>
-        <p><strong>Allowed values:</strong> Mostly match the <code>type</code> values accepted by the <a href="/developer/api/v2/#operation/api.projects.files.post">Add File API method</a>, excluding the following: <code>auto</code>, <code>xml</code>, <code>csv</code>, <code>docx</code>, <code>xlsx</code>, <code>dita</code>, <code>idml</code>, <code>mif</code>, <code>svg</code>.</p>
-        <p><strong>Description:</strong> Used to specify the file format type for a string when post-processing is needed. For example, if a JSON file contains strings with embedded HTML, setting <code>crowdinType</code> to <code>html</code> allows to re-parse the string using the HTML parser. This helps ensure correct rendering and prevents unwanted tags from being displayed. The value must match one of the supported Crowdin file types.</p>
+        <p><strong>Allowed values:</strong> Mostly match the <code>type</code> values accepted by the <a href="/developer/api/v2/#operation/api.projects.files.post">Add File API method</a>, excluding the following: <code>auto</code>, <code>xml</code>, <code>csv</code>, <code>docx</code>, <code>xlsx</code>, <code>dita</code>, <code>idml</code>, <code>mif</code>, <code>svg</code>. Additionally, custom values defined via the <a href="/developer/crowdin-apps-module-custom-file-format/#custom-file-format-type-example"><code>type</code> property</a> in the Custom File Format module are also supported.</p>
+        <p><strong>Description:</strong> Used to specify the file format type for a string when post-processing is needed. For example, if a JSON file contains strings with embedded HTML, setting <code>crowdinType</code> to <code>html</code> allows to re-parse the string using the HTML parser. This helps ensure correct rendering and prevents unwanted tags from being displayed. The value must match one of the supported Crowdin file types or a custom file format identifier.</p>
       </td>
     </tr>
   </tbody>