Modify connector-rest

Author: Clare-Zheng82

articles/data-factory/connector-rest.md

@@ -628,11 +628,11 @@ baseUrl/api/now/table/incident?sysparm_limit=1000&sysparm_offset=10000
 
 **Step 1**: Input `sysparm_offset={offset}` either in **Base URL** or **Relative URL** as shown in the following screenshots:
         
-:::image type="content" source="media/connector-rest/pagination-example-1-rest-linked-service-base-url.png" alt-text="Screenshot showing the configuration step 1 to send multiple requests whose variables are in QueryParameters":::  
+:::image type="content" source="media/connector-rest/pagination-example-1-rest-linked-service-base-url.png" alt-text="Screenshot showing the configuration step 1 to send multiple requests whose variables are in QueryParameters.":::  
     
 or
 
-:::image type="content" source="media/connector-rest/pagination-example-1-rest-linked-service-relative-url.png" alt-text="Screenshot showing the configuration step 2 to send multiple requests whose variables are in QueryParameters"::: 
+:::image type="content" source="media/connector-rest/pagination-example-1-rest-linked-service-relative-url.png" alt-text="Screenshot showing the configuration step 2 to send multiple requests whose variables are in QueryParameters."::: 
         
 **Step 2**: Set **Pagination rules** as either option 1 or option 2：
             
@@ -676,7 +676,7 @@ Request 100: Header(id->100)<br/>
 
 :::image type="content" source="media/connector-rest/pagination-example-3.png" alt-text="Screenshot showing the configuration steps to send multiple requests whose variables are in Headers."::: 
 
-#### Example 4：Variables are in AbsoluteUrl/QueryParameters/Headers, the end variable is not pre-defined and the end condition is based on the response.
+#### Example 4：Variables are in AbsoluteUrl/QueryParameters/Headers, the end variable is not pre-defined and the end condition is based on the response
 
 This example provides configuration steps to send multiple requests whose variables are in AbsoluteUrl/QueryParameters/Headers but the end variable is not defined. For different responses, different end condition rule settings are shown in Example 4.1-4.6.
 
@@ -712,7 +712,7 @@ Data: [
 }
 ```
     
-**Step 1**: Set the range of **Pagination rules** as Example 1 and leave the end of range empty as `"AbsoluteUrl.{offset}": "RANGE:0::1000"`
+**Step 1**: Set the range of **Pagination rules** as Example 1 and leave the end of range empty as `"AbsoluteUrl.{offset}": "RANGE:0::1000"`.
 
 **Step 2**: Set different end condition rules according to different last responses. Six examples are shown below:
 
@@ -737,7 +737,7 @@ Data: [
     {
     }
     ```
-    Set the end condition rule as `"EndCondition:$.data": "NonExist"`
+    Set the end condition rule as `"EndCondition:$.data": "NonExist"`.
         
     :::image type="content" source="media/connector-rest/pagination-example-4-2.png" alt-text="Screenshot showing the EndCondition setting for Example 4.2."::: 
 
@@ -754,11 +754,11 @@ Data: [
             Complete: true
     }
     ```
-    Set the end condition rule as `"EndCondition:$.Complete": "Exist"`
+    Set the end condition rule as `"EndCondition:$.Complete": "Exist"`.
 
     :::image type="content" source="media/connector-rest/pagination-example-4-3.png" alt-text="Screenshot showing the EndCondition setting for Example 4.3."::: 
 
-- **Example 4.4: The pagination will end when the value of the specific node in response is a user-defined const value.**
+- **Example 4.4: The pagination will end when the value of the specific node in response is a user-defined const value**
 
     Last response:
 
@@ -783,7 +783,7 @@ Data: [
             Complete: true
     }
     ```
-    Set the end condition rule as `"EndCondition:$.Complete": "Const:true"`
+    Set the end condition rule as `"EndCondition:$.Complete": "Const:true"`.
         
     :::image type="content" source="media/connector-rest/pagination-example-4-4.png" alt-text="Screenshot showing the EndCondition setting for Example 4.4."::: 
 
@@ -793,7 +793,7 @@ Data: [
     ......<br/>
     Last Response header: header(Complete->1)<br/>
         
-    Set the end condition rule as `"EndCondition:headers.Complete": "Const:1"`
+    Set the end condition rule as `"EndCondition:headers.Complete": "Const:1"`.
         
     :::image type="content" source="media/connector-rest/pagination-example-4-5.png" alt-text="Screenshot showing the EndCondition setting for Example 4.5."::: 
 
@@ -803,7 +803,7 @@ Data: [
     ......<br/>
     Last Response header: header(CompleteTime->20220920)<br/>
         
-    Set the end condition rule as `"EndCondition:headers.CompleteTime": "Exist"`
+    Set the end condition rule as `"EndCondition:headers.CompleteTime": "Exist"`.
 
     :::image type="content" source="media/connector-rest/pagination-example-4-6.png" alt-text="Screenshot showing the EndCondition setting for Example 4.6."::: 
 
@@ -857,7 +857,7 @@ The last response is:
 }
 ```
 
-**Step 1**: Set **Pagination rules** as `"AbsoluteUrl": "$.paging.next"`
+**Step 1**: Set **Pagination rules** as `"AbsoluteUrl": "$.paging.next"`.
 
 **Step 2**: If `next` in the last response is always same with the last request URL and not empty, endless requests will be sent. The end condition can be used to avoid endless requests. Therefore, set the end condition rule refer to Example 4.1-4.6.