20250227 edit pass

Author: WilliamDAssafMSFT

articles/synapse-analytics/spark/apache-spark-handle-livy-error.md

@@ -31,10 +31,10 @@ The following section lists some error types that are currently supported. We're
 
 Each error code falls under one of the following four buckets:
 
-1. **User** - Indicating a user error
-1. **System** - Indicating a system error
-1. **Ambiguous** - Could be either user or system error
-1. **Unknown** - No classification yet, most probably because the error type isn't included in the model
+- **User** - Indicating a user error
+- **System** - Indicating a system error
+- **Ambiguous** - Could be either user or system error
+- **Unknown** - No classification yet, most probably because the error type isn't included in the model
 
 ## Error code examples for each classification type
 

articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md

@@ -992,7 +992,7 @@ This is a public preview limitation. Drop and re-create the Delta table in Spark
 
 ### Query timeout or performance degradation on a table
 
-When the original table in Spark or Dataverse is modified, the corresponding tables in the serverless pool is automatically recreated. This process results in the loss of existing statistics on the table. Without these statistics, queries on the table may experience delays or even timeouts.
+When the original table in Spark or Dataverse is modified, the corresponding tables in the serverless pool are automatically recreated. This process results in the loss of existing statistics on the table. Without these statistics, queries on the table may experience delays or even timeouts.
 
 If you encounter this issue, consider setting up a job to recreate statistics on the tables after changes in Spark/Dataverse or on a regular schedule.
 

articles/synapse-analytics/troubleshoot/media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-2a.png

@@ -20,23 +20,21 @@ If your storage account lacks the proper permissions, you aren't able to expand
 
 The detailed error message might vary, but the general meaning of the error message is: "This request isn't authorized to perform this operation.".
 
-In the linked storage node:  
-:::image type="content" source="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-1.png" alt-text="Storage connectivity issue 1.":::
+In the linked storage node:
 
-In the storage container node:  
-:::image type="content" source="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-1a.png" alt-text="Storage connectivity issue 1a." lightbox="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-1a.png":::
+:::image type="content" source="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-1.png" alt-text="Screenshot from the Azure portal of the permissions storage connectivity issue.":::
+
+In the storage container node:
+
+:::image type="content" source="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-1a.png" alt-text="Screenshot from the Azure portal of the storage permissions error message." lightbox="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-1a.png":::
 
 **SOLUTION**: To assign your account to the proper role, see [Assign an Azure role for access to blob data](../../storage/blobs/assign-azure-role-data-access.md)
 
 ## Case #2: Failed to send the request to storage server
 
-When selecting the arrow to expand the storage structure in "Data" --> "Linked" in Synapse Studio, you might see the "REQUEST_SEND_ERROR" issue in the left panel. See the issue symptom screenshot:
-
-In the linked storage node:  
-:::image type="content" source="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-2.png" alt-text="Storage connectivity issue 2.":::
+When selecting the arrow to expand the storage structure in "Data" --> "Linked" in Synapse Studio, you might see the "REQUEST_SEND_ERROR" issue in the linked storage node or the storage container node. For example, in the linked storage node:  
 
-In the storage container node:  
-:::image type="content" source="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-2a.png" alt-text="Storage connectivity issue 2a." lightbox="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-2a.png":::
+:::image type="content" source="media/troubleshoot-synapse-studio-and-storage-connectivity/storage-connectivity-issue-2.png" alt-text="Screenshot from the Azure portal of the REQUEST_SEND_ERROR message.":::
 
 There might be several possible reasons behind this issue:
 

articles/synapse-analytics/troubleshoot/troubleshoot-synapse-studio-and-storage-connectivity.md

@@ -145,7 +145,7 @@ If possible, please try to switch your network environment, such as inside/outsi
 
 + If you can run notebook on a different workstation but in the same network environment, ensure you didn't install any browser plugin that might block the WebSocket request. 
 
-Otherwise, contact your network administrator and ensure the outbound WebSocket requests with the following URL pattern is allowed and their request header is not redacted: `wss://{workspace}.dev.azuresynapse.net/{path}`
+Otherwise, contact your network administrator and ensure the outbound WebSocket requests with the following URL pattern are allowed and their request header is not redacted: `wss://{workspace}.dev.azuresynapse.net/{path}`
 
 - `{workspace}` is the Synapse workspace name
 - `{path}` indicates any sub-path (for example, slash character is included) in URI