Upgrade snowflake upgrade section content

Clare Zheng (Shanghai Wicresoft Co Ltd) · Clare Zheng (Shanghai Wicresoft Co Ltd) · commit 092e86896f2b · 2024-10-12T14:44:14.000+08:00
diff --git a/articles/data-factory/connector-snowflake.md b/articles/data-factory/connector-snowflake.md
@@ -699,9 +699,9 @@ To perform a side-by-side upgrade, complete the following steps:
 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. 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 linked services:
 
-   **Legacy Snowflake connector JSON payload:**
+   **Legacy Snowflake linked service JSON payload:**
    ```json
      {
         "name": "Snowflake1",
@@ -722,7 +722,7 @@ To perform an in-place upgrade, you need to edit the existing linked service pay
     }
    ```
 
-   **New Snowflake connector JSON payload:**
+   **New Snowflake linked service JSON payload:**
    ```json
     {
         "name": "Snowflake2",

Original file line number	Diff line number	Diff line change
`@@ -699,9 +699,9 @@ To perform a side-by-side upgrade, complete the following steps:`
`699`	`699`	`To perform an in-place upgrade, you need to edit the existing linked service payload and update dataset to use the new linked service.`
`700`	`700`
`701`	`701`	`1. Update the type from Snowflake to SnowflakeV2.`
`702`		`-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:`
	`702`	`+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 linked services:`
`703`	`703`
`704`		`- Legacy Snowflake connector JSON payload:`
	`704`	`+ Legacy Snowflake linked service JSON payload:`
`705`	`705`	```json
`706`	`706`	`{`
`707`	`707`	`"name": "Snowflake1",`
`@@ -722,7 +722,7 @@ To perform an in-place upgrade, you need to edit the existing linked service pay`
`722`	`722`	`}`
`723`	`723`	```
`724`	`724`
`725`		`- New Snowflake connector JSON payload:`
	`725`	`+ New Snowflake linked service JSON payload:`
`726`	`726`	```json
`727`	`727`	`{`
`728`	`728`	`"name": "Snowflake2",`