Skip to content

Commit 215a0f9

Browse files
committed
Wording
1 parent b036162 commit 215a0f9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/sql/how-to-configure-cosmos-db-trigger.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This article describes advanced configuration options you can set when using the
1717

1818
The Azure Functions trigger for Cosmos DB uses the [Change Feed Processor Library](change-feed-processor.md) internally, and the library generates a set of health logs that can be used to monitor internal operations for [troubleshooting purposes](./troubleshoot-changefeed-functions.md).
1919

20-
The health logs describe how the Azure Functions trigger for Cosmos DB behaves when attempting operations during load-balancing scenarios or initialization.
20+
The health logs describe how the Azure Functions trigger for Cosmos DB behaves when attempting operations during load-balancing, initialization, and processing scenarios.
2121

2222
### Enabling logging
2323

@@ -37,7 +37,7 @@ To enable logging when using Azure Functions trigger for Cosmos DB, locate the `
3737

3838
After the Azure Function is deployed with the updated configuration, you'll see the Azure Functions trigger for Cosmos DB logs as part of your traces. You can view the logs in your configured logging provider under the *Category* `Host.Triggers.CosmosDB`.
3939

40-
### Which type of logs are exposed?
40+
### Which type of logs are emitted?
4141

4242
Once enabled, there are three levels of log events that will be emitted:
4343

0 commit comments

Comments
 (0)