clarification of obfuscation

te3/other/release-notes/3_15_0.md

@@ -39,7 +39,7 @@ Check out our [release blog](https://blog.tabulareditor.com/) to get a brief ove
 - We now support adding [Data Coverage Definition expressions](https://learn.microsoft.com/en-us/analysis-services/tom/table-partitions?view=asallproducts-allversions#define-the-data-coverage-of-the-directquery-partition) to partitions in DirectQuery mode.
 - Tabular Editor will now add a `__TEdtr` annotation to your model when metadata is saved to disk (either as Model.bim, Database.json or TMDL). This annotation is used by Microsoft for analytics about Tabular Editor usage for semantic models published to a Power BI or Fabric workspace. This annotation may also be required for certain features to work correctly in Power BI / Fabric, when a model was edited using Tabular Editor.
 - The **New Model** dialog now has a **Direct Lake** checkbox*, which will configure the model to use the new Direct Lake storage mode in Fabric. [More information](https://docs.tabulareditor.com/common/Datasets/direct-lake-dataset.html). Moreover, you can now explicitly choose the *Compatibility Mode* when entering the *Compatibility Level* manually.
-- You can now export [obfuscated VPAX files](https://www.sqlbi.com/blog/marco/2024/03/15/vpax-obfuscator-a-library-to-obfuscate-vpax-files/) using Tabular Editor. Find this option in the **VertiPaq Analyzer** view, on the dropdown next to the **Export** button.
+- You can now export [obfuscated VPAX files](https://www.sqlbi.com/blog/marco/2024/03/15/vpax-obfuscator-a-library-to-obfuscate-vpax-files/) using Tabular Editor. This can be helpful when your metadata (object names and DAX expressions) are confidential, but you want to share the VPAX file with a person or service for optimization purposes. Find this option in the **VertiPaq Analyzer** view, on the dropdown next to the **Export** button.
 
 ## Improvements in 3.15.0