Skip to content

Commit a9da43f

Browse files
authored
Apply suggestions from PR review
1 parent 380785b commit a9da43f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/communication-services/how-tos/event-grid/local-testing-event-grid.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,15 +20,15 @@ Testing Event Grid triggered Azure Functions locally can be complicated. You don
2020
- Install [Postman](https://www.postman.com/downloads/).
2121
- Have a running Azure Function that can be triggered by Event Grid. If you don't have one, you can follow the [quickstart](../../../azure-functions/functions-bindings-event-grid-trigger.md?tabs=in-process%2Cextensionv3&pivots=programming-language-javascript) to create one.
2222

23-
The Azure Function can be running either in Azure if you want to test it with some test events or if you want to test the entire flow locally (press `F5` in Visual Studio Code to run it locally). If you want to test the entire flow with externally triggered webhook, you need to use [ngrok](https://ngrok.com/) to expose your locally running Azure Function
24-
to public allowing it being triggered by internet sources (as example from Azure Event WebHooks). Configure ngrok by running the command:
23+
The Azure Function can be running either in Azure if you want to test it with some test events or if you want to test the entire flow locally (press `F5` in Visual Studio Code to run it locally). If you want to test the entire flow with an externally triggered webhook, you need to use [ngrok](https://ngrok.com/) to expose your locally running Azure Function
24+
to the public, allowing it to be triggered by internet sources (as an example from Azure Event WebHooks). Configure ngrok by running the command:
2525

2626
```bash
2727

2828
ngrok http 7071
2929

3030
```
31-
It is worth to remember that exposing development resources publicly may not be considered as secure. That is why you can also run entire workflow locally without ngrok by invoking requests to:
31+
It is worth remembering that exposing development resources publicly might not be considered as secure. That is why you can also run the entire workflow locally without ngrok by invoking requests to:
3232
```
3333
http://localhost:7071/runtime/webhooks/EventGrid?functionName={functionname}
3434
```

0 commit comments

Comments
 (0)