Update README to add info about types and version

Author: joeluong-sfcc

README.md

@@ -24,6 +24,7 @@ An auto-generated [documentation site](https://salesforcecommercecloud.github.io
 1. **Type Access**: API class types are accessible through the `<api_class>Types` namespace (e.g., `ShopperProductsTypes`). Individual types can be accessed as `ShopperProductsTypes.Product`.
 2. **Type References**: The `References` section under API classes in the generated documentation may show duplicate entries. This occurs because types are exported both at their original definition and under the API class namespace. Both references point to the same underlying type definition.
 3. **V4 Migration Guide**: Starting in v5, API classes will no longer be exported under API family namespaces. See the [Sample Code](#sample-code) section for migration examples.
+4. **Supporting Files**: The SDK includes additional supporting modules beyond the `helpers` SLAS functions. The `types` module provides common type definitions shared across API classes, while the `version` module automatically implements user agent headers for all requests. The user agent value follows the format `commerce-sdk@<version>` based on the current SDK version.
 
 ## :warning: Planned API Changes :warning:
 

docs/index.html

@@ -90,6 +90,7 @@ <h3>Navigating the Documentation</h3>
 					<li><strong>Type Access</strong>: API class types are accessible through the <code>&lt;api_class&gt;Types</code> namespace (e.g., <code>ShopperProductsTypes</code>). Individual types can be accessed as <code>ShopperProductsTypes.Product</code>.</li>
 					<li><strong>Type References</strong>: The <code>References</code> section under API classes in the generated documentation may show duplicate entries. This occurs because types are exported both at their original definition and under the API class namespace. Both references point to the same underlying type definition.</li>
 					<li><strong>V4 Migration Guide</strong>: Starting in v5, API classes will no longer be exported under API family namespaces. See the <a href="#sample-code">Sample Code</a> section for migration examples.</li>
+					<li><strong>Supporting Files</strong>: The SDK includes additional supporting modules beyond the <code>helpers</code> SLAS functions. The <code>types</code> module provides common type definitions shared across API classes, while the <code>version</code> module automatically implements user agent headers for all requests. The user agent value follows the format <code>commerce-sdk@&lt;version&gt;</code> based on the current SDK version.</li>
 				</ol>
 				<a href="#warning-planned-api-changes-warning" id="warning-planned-api-changes-warning" style="color: inherit; text-decoration: none;">
 					<h2>:warning: Planned API Changes :warning:</h2>
@@ -622,7 +623,7 @@ <h2>Security</h2>
 				<p>For more information about security considerations related to developing headless commerce applications, see
 					<a href="https://developer.salesforce.com/docs/commerce/commerce-api/guide/security-considerations-for-headless-commerce.html">Security Considerations for Headless Commerce</a> on the
 				<a href="https://developer.salesforce.com/developer-centers/commerce-cloud">Commerce Cloud Developer Center</a>.</p>
-				<p>If you discover any potential security issues, please report them to <a href="mailto:&#115;&#101;&#99;&#117;&#114;&#105;&#x74;&#121;&#x40;&#115;&#97;&#x6c;&#x65;&#115;&#x66;&#111;&#x72;&#99;&#101;&#x2e;&#x63;&#111;&#109;">&#115;&#101;&#99;&#117;&#114;&#105;&#x74;&#121;&#x40;&#115;&#97;&#x6c;&#x65;&#115;&#x66;&#111;&#x72;&#99;&#101;&#x2e;&#x63;&#111;&#109;</a> as soon as possible.</p>
+				<p>If you discover any potential security issues, please report them to <a href="mailto:&#x73;&#101;&#x63;&#117;&#114;&#105;&#116;&#121;&#64;&#x73;&#x61;&#x6c;&#x65;&#115;&#x66;&#111;&#x72;&#99;&#x65;&#x2e;&#x63;&#x6f;&#x6d;">&#x73;&#101;&#x63;&#117;&#114;&#105;&#116;&#121;&#64;&#x73;&#x61;&#x6c;&#x65;&#115;&#x66;&#111;&#x72;&#99;&#x65;&#x2e;&#x63;&#x6f;&#x6d;</a> as soon as possible.</p>
 				<a href="#additional-documentation" id="additional-documentation" style="color: inherit; text-decoration: none;">
 					<h2>Additional Documentation</h2>
 				</a>