Update snowflake upgrade section

Author: Clare Zheng (Shanghai Wicresoft Co Ltd)

articles/data-factory/connector-snowflake.md

@@ -696,63 +696,63 @@ To perform a side-by-side upgrade, complete the following steps:
 
 ### In-place upgrade
 
-To perform an in-place upgrade, you need to edit the existing linked service payload.
+To perform an in-place upgrade, you need to edit the existing linked service payload and update dataset to use the new linked service.
 
-1. Update the type from ‘Snowflake’ to ‘SnowflakeV2’.
-1. Modify the linked service payload from its legacy format to the new pattern. You can either fill in each field from the user interface after changing the type mentioned above, or update the payload directly through the JSON Editor. Refer to the [Linked service properties](#linked-service-properties) section in this article for the supported connection properties.  The following examples show the differences in payload for the legacy and new Snowflake connectors:
+1. Update the type from **Snowflake** to **SnowflakeV2**.
+1. Modify the linked service payload from its legacy format to the new pattern. You can either fill in each field from the user interface after changing the type mentioned above, or update the payload directly through the JSON Editor. Refer to the [Linked service properties](#linked-service-properties) section in this article for the supported connection properties. The following examples show the differences in payload for the legacy and new Snowflake connectors:
 
    **Legacy Snowflake connector JSON payload:**
    ```json
-   { 
-       "name": "Snowflake1", 
-       "type": "Microsoft.DataFactory/factories/linkedservices", 
-       "properties": { 
-           "annotations": [], 
-           "type": "Snowflake", 
-           "typeProperties": { 
-               "authenticationType": "Basic", 
-               "connectionString": "jdbc:snowflake://<fake_account>.snowflakecomputing.com/?user=FAKE_USER&db=FAKE_DB&warehouse=FAKE_DW&schema=PUBLIC", 
-               "encryptedCredential": "<your_encrypted_credential_value>" 
-           }, 
-           "connectVia": { 
-               "referenceName": "AzureIntegrationRuntime", 
-               "type": "IntegrationRuntimeReference" 
-           } 
-       }
-   } 
+     {
+        "name": "Snowflake1",
+        "type": "Microsoft.DataFactory/factories/linkedservices",
+        "properties": {
+            "annotations": [],
+            "type": "Snowflake",
+            "typeProperties": {
+                "authenticationType": "Basic",
+                "connectionString": "jdbc:snowflake://<fake_account>.snowflakecomputing.com/?user=FAKE_USER&db=FAKE_DB&warehouse=FAKE_DW&schema=PUBLIC",
+                "encryptedCredential": "<your_encrypted_credential_value>"
+            },
+            "connectVia": {
+                "referenceName": "AzureIntegrationRuntime",
+                "type": "IntegrationRuntimeReference"
+            }
+        }
+    }
    ```
 
    **New Snowflake connector JSON payload:**
    ```json
-   { 
-       "name": "Snowflake2", 
-       "type": "Microsoft.DataFactory/factories/linkedservices", 
-       "properties": { 
-           "parameters": { 
-              "schema": { 
-                   "type": "string", 
-                   "defaultValue": "PUBLIC" 
-               } 
-           }, 
-           "annotations": [], 
-           "type": "SnowflakeV2", 
-           "typeProperties": { 
-               "authenticationType": "Basic", 
-               "accountIdentifier": "<FAKE_Account", 
-               "user": "FAKE_USER", 
-               "database": "FAKE_DB", 
-               "warehouse": "FAKE_DW", 
-               "encryptedCredential": "<placeholder>" 
-           }, 
-           "connectVia": { 
-               "referenceName": "AutoResolveIntegrationRuntime", 
-               "type": "IntegrationRuntimeReference" 
-           } 
-       } 
-   } 
+    {
+        "name": "Snowflake2",
+        "type": "Microsoft.DataFactory/factories/linkedservices",
+        "properties": {
+            "parameters": {
+                "schema": {
+                    "type": "string",
+                    "defaultValue": "PUBLIC"
+                }
+            },
+            "annotations": [],
+            "type": "SnowflakeV2",
+            "typeProperties": {
+                "authenticationType": "Basic",
+                "accountIdentifier": "<FAKE_Account>",
+                "user": "FAKE_USER",
+                "database": "FAKE_DB",
+                "warehouse": "FAKE_DW",
+                "encryptedCredential": "<placeholder>"
+            },
+            "connectVia": {
+                "referenceName": "AutoResolveIntegrationRuntime",
+                "type": "IntegrationRuntimeReference"
+            }
+        }
+    }
    ```
 
-   1. Update dataset to use the new linked service. You can either create a new dataset based on the newly created linked service, or update an existing dataset's type property from _SnowflakeTable_ to _SnowflakeV2Table_. 
+1. Update dataset to use the new linked service. You can either create a new dataset based on the newly created linked service, or update an existing dataset's type property from **SnowflakeTable** to **SnowflakeV2Table**. 
 
 ## Differences between Snowflake and Snowflake (legacy)