Skip to content

Commit a6ebc10

Browse files
authored
Update batch-requests.md
1 parent d66461f commit a6ebc10

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

concepts/sdks/batch-requests.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The Microsoft Graph SDK automatically handles batching requests with respect to
2828

2929
## Simple batching example
3030

31-
This example shows how to send multiple requests in a batch that are not dependent on each other. The requests can be run by the service in any order. This example gets the user and gets the user's calendar view for the current day.
31+
This example shows how to send multiple requests in a batch that are not dependent on each other. The service can run the requests in any order. This example gets the user and gets the user's calendar view for the current day.
3232

3333
### [C#](#tab/csharp)
3434

@@ -54,7 +54,7 @@ This example shows how to send multiple requests in a batch that are not depende
5454

5555
## Batches with dependent requests
5656

57-
This example shows how to send multiple requests in a batch that are dependent on each other. The requests are run by the service in the order specified by the dependencies. This example adds an event with a start time during the current day to the user's calendar and gets the user's calendar view for the current day. To make sure that the calendar review returned includes the new event created, the request for the calendar view is configured as dependent on the request to add the new event. This ensures that the add event request runs first.
57+
This example shows how to send multiple requests in a batch that are dependent on each other. The service runs the request in the order specified by the dependencies. This example adds an event with a start time during the current day to the user's calendar and gets the user's calendar view for the current day. To make sure that the calendar review returned includes the new event created, the request for the calendar view is configured as dependent on the request to add the new event. This ensures that the add event request runs first.
5858

5959
> [!NOTE]
6060
> If the add event request fails, the get calendar view request fails with a `424 Failed Dependency` error.

0 commit comments

Comments
 (0)