20240320 edit pass

Author: WilliamDAssafMSFT

docs/database-engine/database-mirroring/database-mirroring-sql-server.md

@@ -139,7 +139,7 @@ helpviewer_keywords:
 
  The second operating mode, *high-performance mode*, runs asynchronously. The mirror server tries to keep up with the log records sent by the principal server. The mirror database might lag somewhat behind the principal database. However, typically, the gap between the databases is small. However, the gap can become significant if the principal server is under a heavy work load or the system of the mirror server is overloaded.  
 
- In high-performance mode, as soon as the principal server sends a log record to the mirror server, the principal server sends a confirmation to the client. It does not wait for an acknowledgement from the mirror server. This means that transactions commit without waiting for the mirror server to write the log to disk. Such asynchronous operation enables the principal server to run with minimum transaction latency, at the potential risk of some data loss.  
+ In high-performance mode, as soon as the principal server sends a log record to the mirror server, the principal server sends a confirmation to the client. It does not wait for an acknowledgment from the mirror server. This means that transactions commit without waiting for the mirror server to write the log to disk. Such asynchronous operation enables the principal server to run with minimum transaction latency, at the potential risk of some data loss.  
 
  All database mirroring sessions support only one principal server and one mirror server. This configuration is shown in the following illustration.  
 

docs/sql-server/fabric-mirrored-database/fabric-mirrored-databases.md

@@ -9,7 +9,7 @@ ms.service: fabric
 ms.topic: conceptual
 monikerRange: "=azuresqldb-current||=fabric"
 ---
-# Microsoft Fabric Mirrored databases
+# Microsoft Fabric mirrored databases
 [!INCLUDE [asdb-fabric](../../includes/applies-to-version/asdb-fabric.md)]
 
 You can [mirror databases in Azure SQL Database to Microsoft Fabric](/fabric/database/mirrored-database/overview). You can continuously replicate your existing data estate directly into Fabric's OneLake, including data from Azure SQL Database.
@@ -18,24 +18,24 @@ For more information, see:
 
 - [Microsoft Fabric mirrored databases (Preview)](/fabric/database/mirrored-database/overview)
 - [Microsoft Fabric mirrored databases monitoring](/fabric/database/mirrored-database/monitor)
-- [Explore data in your Mirrored database using Microsoft Fabric](/fabric/database/mirrored-database/explore)
+- [Explore data in your mirrored database using Microsoft Fabric](/fabric/database/mirrored-database/explore)
 
 This feature is not currently available for Azure SQL Managed Instance or SQL Server instances.
 
-## What are Fabric Mirrored Databases?
+## What are Fabric mirrored databases?
 
 Mirroring in Fabric provides an easy experience to speed the time-to-value for insights and decisions, and to break down data silos between technology solutions, without developing expensive Extract, Transform, and Load (ETL) processes to move data.
 
 With the most up-to-date data in a queryable format in OneLake, you can now use all the different services in Fabric, such as running analytics with Spark, executing notebooks, data engineering, visualizing through Power BI Reports, and more.
 
 With Mirroring in Fabric, you don't need to piece together different services from multiple vendors. Instead, you can enjoy a highly integrated, end-to-end, and easy-to-use product that is designed to simplify your analytics needs, and built for openness and collaboration between technology solutions that can read the open-source Delta Lake table format.
 
-## Fabric Mirrored Databases
+## Fabric mirrored databases
 
-The Fabric Mirrored Database feature uses similar change feed technology as the Azure Synapse Link, and shares some system objects.
+The Fabric mirrored database feature uses similar change feed technology as the Azure Synapse Link, and shares some system objects.
 
 > [!NOTE]
-> Enabling Database Mirroring via the Fabric portal will create a `changefeed` database user, a `changefeed` schema, and several tables within the `changefeed` schema in your source database. Do not alter any of these objects, they are system-managed.
+> Enabling Mirroring via the Fabric portal will create a `changefeed` database user, a `changefeed` schema, and several tables within the `changefeed` schema in your source database. Do not alter any of these objects, they are system-managed.
 
 ## Related content