Skip to content

Commit 8980bc5

Browse files
Address PR feedback on manage-calls-web.md
1 parent 758fc41 commit 8980bc5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/communication-services/how-tos/calling-sdk/includes/manage-calls/manage-calls-web.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ To hold the call
125125
await call.hold();
126126
```
127127
When `hold` API resolves, the call state is set to `LocalHold`. In a 1:1 call, the other participant is also put on hold, and state of the call from the perspective of that participant is set to 'RemoteHold'. Later, the other participant might put its call on hold, which would result in a state change to `LocalHold`.
128-
In a group call - the `hold` is a local operation, it doesn't hold the call for other call participants.
128+
In a group call or meeting - the `hold` is a local operation, it doesn't hold the call for other call participants.
129129
To resume the call all users who initiated hold must resume it.
130130

131131
To resume call from hold:
@@ -158,7 +158,7 @@ await call.muteIncomingAudio();
158158
await call.unmuteIncomingAudio();
159159
```
160160

161-
When incoming audio is muted, the participant client SDK still receives the call audio (remote participant's audio). The call audio isn't heard in the speaker and the participant isn't able to listen until 'call.unmuteIncomingAudio()' is called. However, we can apply filter on call audio and play the filtered audio.
161+
When incoming audio is muted, the participant client SDK still receives the call audio (remote participant's audio). The call audio isn't heard in the speaker and the participant isn't able to listen until 'call.unmuteIncomingAudio()' is called. However, we can apply filter on call audio and play the filtered audio.
162162

163163
## Mute other participants
164164
> [!NOTE]

0 commit comments

Comments
 (0)