Skip to content

Commit 0cea774

Browse files
authored
Fix pluralization
1 parent e0ba629 commit 0cea774

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Samples/PublicSamples/RecordingBot/docs/explanations/recording-bot-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,8 @@ and encryption, metadata and media events are transferred via the TCP connection
4242
The overhead of the TCP endpoints is completly managed by the Graph Communications SDK, but the
4343
HTTPS endpoints for notifications must be custom implemented by the bot recording application.
4444
ASP.NET Core can be used. After a HTTP request is authorized and notifications are parsed from the
45-
request, the notifications should be forwarded to the SDK. The SDK will process notification and
46-
fire eventss based on these notifications. The event handlers can implement business logic. An
45+
request, the notifications should be forwarded to the SDK. The SDK will process notifications and
46+
fire events based on these notifications. The event handlers can implement business logic. An
4747
event handler that, for example, triggers when a new call notification was received, should be used
4848
for answering calls. Before answering, business logic can decide whether the call should be
4949
accepted. Such an event handler should use the `answer` method of the SDK with the desired

0 commit comments

Comments
 (0)