diff --git a/common/Datasets/direct-lake-dataset.md b/common/Datasets/direct-lake-dataset.md
index 005c779d..0e6ffefd 100644
--- a/common/Datasets/direct-lake-dataset.md
+++ b/common/Datasets/direct-lake-dataset.md
@@ -1,6 +1,6 @@
 ---
 uid: direct-lake-dataset
-title: Direct Lake Datasets
+title: Direct Lake Semantic Models
 author: Morten Lønskov
 updated: 2023-08-14
 applies_to:
@@ -15,22 +15,25 @@ applies_to:
     - edition: Enterprise
 ---
 
-# Direct Lake Datasets
-Direct Lake datasets connect directly to data sources stored in [Fabric One Lake](https://learn.microsoft.com/en-us/fabric/onelake/onelake-overview). 
+# Direct Lake Semantic Models
+Direct Lake semantic models connect directly to data sources stored in [Fabric One Lake](https://learn.microsoft.com/en-us/fabric/onelake/onelake-overview). 
 
 > [!IMPORTANT]
 > Changing a Direct Lake dataset through the XMLA endpoint will block your ability to change the Direct Lake dataset inside the Fabric Service. Only XMLA endpoint can then edit the Direct Lake This is one of the current limitations of this preview 
 feature.
 
-Tabular Editor 3 can create and connect to this type of dataset. For a tutorial on this please refer to our blog article: [Direct Lake Datasets: How to use them with Tabular Editor](https://blog.tabulareditor.com/2023/08/23/fabric-direct-lake-dataset)
+Tabular Editor 3 can create and connect to this type of dataset. For a tutorial on this please refer to our blog article: [Direct Lake semantic models: How to use them with Tabular Editor](https://blog.tabulareditor.com/2023/08/23/fabric-direct-lake-dataset)
 
-Tabular Editor 2 can connect to Direct Lake datasets, but does not have any built in functionality to create new tables or direct lake datasets. This needs to be done manually or with a C# script. 
+Tabular Editor 2 can connect to Direct Lake semantic models, but does not have any built in functionality to create new tables or direct lake semantic models. This needs to be done manually or with a C# script. 
 
+> [!NOTE]
+> DirectLake models currently use a collation that is different from regular Power BI import semantic models. This may lead to different results when querying the model, or when referencing object names in DAX code.
+ For more information please see this blog post by Kurt Buhler: [Case-sensitive models in Power BI: consequences & considerations](https://data-goblins.com/power-bi/case-specific)
 
 
 <div class="NOTE">
   <h5>FABRIC IN PREVIEW</h5>
-  Fabric is currently in preview and there are therefore several limitations to the changes that can be made to a Direct Lake dataset: [Direct Lake Known Issues and Limitations](https://learn.microsoft.com/en-us/power-bi/enterprise/directlake-overview#known-issues-and-limitations)
+  Fabric is currently in preview and there are therefore several limitations to the changes that can be made to a Direct Lake dataset: <a href="https://learn.microsoft.com/en-us/power-bi/enterprise/directlake-overview#known-issues-and-limitations">Direct Lake Known Issues and Limitations</a>
 </div>
 
 
diff --git a/te3/powerbi-xmla.md b/te3/powerbi-xmla.md
index 40dfac81..82a36c59 100644
--- a/te3/powerbi-xmla.md
+++ b/te3/powerbi-xmla.md
@@ -31,7 +31,7 @@ When connecting to a dataset through the XMLA endpoint, all data modeling operat
 
 > [!WARNING]
 > Once a change is made to a Power BI dataset through the XMLA endpoint, it will not be possible to download the dataset as a .pbix file. [More information](https://docs.microsoft.com/en-us/power-bi/admin/service-premium-connect-tools#power-bi-desktop-authored-datasets).
-> Please see [Creating PBIX File from XMLA Endoint](powerbi-xmla-pbix-workaround) for a workaround
+> Please see [Creating PBIX File from XMLA Endoint](xref:powerbi-xmla-pbix-workaround) for a workaround
 
 ## Workflow