Merge pull request #24251 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to main to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: huypub

azure-sql/virtual-machines/windows/availability-group-dnn-interoperability.md

@@ -121,7 +121,7 @@ Configure the linked server using the AG DNN listener name and port. If the port
 
 - Does DNN support multiple-subnet clusters?
 
-   Yes. The cluster binds the DNN in DNS with the physical IP addresses of all replicas in the availability regardless of the subnet. The SQL client tries all IP addresses of the DNS name regardless of the subnet. 
+   Yes. The cluster binds the DNN in DNS with the physical IP addresses of all replicas in the availability group regardless of the subnet. The SQL client tries all IP addresses of the DNS name regardless of the subnet. 
 
 - Does the availability group DNN listener support read-only routing? 
 

docs/connect/python/pyodbc/step-3-proof-of-concept-connecting-to-sql-using-pyodbc.md

@@ -37,7 +37,7 @@ cursor = cnxn.cursor()
 
 ## Run query  
 
-The cursor.executefunction can be used to retrieve a result set from a query against SQL Database. This function accepts a query and returns a result set, which can be iterated over with the use of cursor.fetchone().
+The cursor.execute function can be used to retrieve a result set from a query against SQL Database. This function accepts a query and returns a result set, which can be iterated over with the use of cursor.fetchone().
 
 ```python
 #Sample select query

docs/sql-server/synapse-link/synapse-link-sql-server-change-feed.md

@@ -54,7 +54,7 @@ Capturing changes for Azure Synapse Link is similar to the existing Change Data
 CDC works by harvesting the transaction log to capture all modifications performed on the source table(s). 
 
 - In CDC, the change data is populated internally to a sibling table in the database.
-- In Azure Synapse Link, the data will read directly from the database transaction log, cached in memory, and eventually written to the landing zone in Azure Storage. 
+- In Azure Synapse Link, the data will be read directly from the database transaction log, cached in memory, and eventually written to the landing zone in Azure Storage. 
 
 If a storage outage occurs, it can cause the landing zone to become unavailable, which will block publications to that landing zone. Similar to the behavior if the SQL Server CDC log reader agent fails or is not running, the source database transaction log cannot be truncated. In the case of a prolonged storage outage or storage configuration change that causes it to become inaccessible, stop the Synapse Link through the Synapse Studio.