Update and lint release notes (#3699)

Author: ErikEJ

release-notes/7.0/7.0.0-preview2.md

@@ -40,19 +40,24 @@ This update brings the following changes since the [7.0.0-preview1](7.0.0-previe
 
 - If your environment might be affected (i.e., you operate a BAG with custom ports, or have experienced failures after failover), you can enable the new switch in your application:
 
-```
+```c#
 AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner", true);
 ```
 
 - Then, ensure your connection string includes your preferred failover partner (with correct `tcp:host,port`) so that the client uses that instead of the server's suggestion.
 - Without enabling this, by default, the client continues to prefer the server-provided partner, maintaining backwards compatibility.
 
-
 #### Other Additions
 
 - Add app context switch for enabling asynchronous multi-packet improvements
   ([#3605](https://github.com/dotnet/SqlClient/pull/3605))
 
+To enable these improvements, set the following switches in your application:
+
+```c#
+AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.UseCompatibilityAsyncBehaviour", false);
+AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.UseCompatibilityProcessSni", false);
+```
 
 ### Changed
 
@@ -64,7 +69,7 @@ AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailov
 
 *Who benefits:*
 
-- Teams moving toward stronger, passwordless or MFA-compliant auth (in line with changes across MSAL/Azure.Identity and Entra MFA enforcement). This aligns Microsoft.Data.SqlClient with Microsoft's direction to avoid username/password (ROPC) flows. See https://learn.microsoft.com/en-us/entra/identity/authentication/concept-mandatory-multifactor-authentication for more explanation of why this change is being made across Microsoft products/services.
+- Teams moving toward stronger, passwordless or MFA-compliant auth (in line with changes across MSAL/Azure.Identity and Entra MFA enforcement). This aligns Microsoft.Data.SqlClient with Microsoft's direction to avoid username/password (ROPC) flows. See [Planning for mandatory multifactor authentication for Azure and other admin portals](https://learn.microsoft.com/entra/identity/authentication/concept-mandatory-multifactor-authentication) for more explanation of why this change is being made across Microsoft products/services.
 
 *Impact:*
 
@@ -73,11 +78,11 @@ AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailov
   - Service to service: `Active Directory Service Principal` (client secret/certificate)
   - Cloud workloads: `Active Directory Managed Identity` or `Active Directory Workload Identity`
   - Headless/Developer flows: `Active Directory Device Code Flow` or `Active Directory Default`
-- See https://learn.microsoft.com/en-us/sql/connect/ado-net/sql/azure-active-directory-authentication for more information on authentication to SQL Server using Microsoft Entra.
+- See [Connect to Azure SQL with Microsoft Entra authentication and SqlClient](https://learn.microsoft.com/sql/connect/ado-net/sql/azure-active-directory-authentication) for more information on authentication to SQL Server using Microsoft Entra.
 
 #### Other changes
 
-- Improve performance in `SqlStatistics` by using `Environment.TickCount` for calculating execution timing 
+- Improve performance in `SqlStatistics` by using `Environment.TickCount` for calculating execution timing
   ([#3609](https://github.com/dotnet/SqlClient/pull/3609))
 
 - Improve performance in Always Encrypted scenarios by using lower-allocation primitives
@@ -131,6 +136,7 @@ AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailov
   - Updated `System.Text.Json` to v8.0.6 (net8), v9.0.9 (net9)
 
 ## Contributors
+
 We thank the following public contributors. Their efforts toward this project are very much appreciated.
 
 - [edwardneal](https://github.com/edwardneal)