fixed blocking errors

Author: vac0224

articles/communication-services/how-tos/calling-sdk/includes/dominant-speaker/dominant-speaker-android.md

@@ -17,7 +17,7 @@ DominantSpeakersFeature dominantSpeakersFeature = call.feature(Features.DOMINANT
 The Dominant Speakers feature object has the following structure:
 
 - `OnDominantSpeakersChanged`: Event for listening for changes in the dominant speakers list.
-- `getDominantSpeakersInfo()`: Gets the `DominantSpeakersInfo` object, this object has:
+- `getDominantSpeakersInfo()`: Gets the `DominantSpeakersInfo` object. This object has:
     - `getSpeakers()`: A list of participant identifiers representing the dominant speakers list.
     - `getLastUpdatedAt()`: The date when the dominant speakers list was updated. 
 

articles/communication-services/how-tos/calling-sdk/includes/dominant-speaker/dominant-speaker-ios.md

@@ -18,7 +18,7 @@ let dominantSpeakersFeature = call.feature(Features.dominantSpeakers)
 The Dominant Speakers feature object has the following structure:
 
 - `didChangeDominantSpeakers`: Event for listening for changes in the dominant speakers list.
-- `dominantSpeakersInfo`: Which gets the `DominantSpeakersInfo` object, this object has:
+- `dominantSpeakersInfo`: Which gets the `DominantSpeakersInfo` object. This object has:
     - `speakers`: A list of participant identifiers representing the dominant speakers list.
     - `lastUpdatedAt`: The date when the dominant speakers list was updated.
 

articles/communication-services/how-tos/calling-sdk/includes/dominant-speaker/dominant-speaker-windows.md

@@ -19,7 +19,7 @@ DominantSpeakersCallFeature dominantSpeakersFeature = call.Features.DominantSpea
 The Dominant Speakers feature object has the following structure:
 
 - `OnDominantSpeakersChanged`: Event for listening for changes in the dominant speakers list.
-- `DominantSpeakersInfo`: Gets the `DominantSpeakersInfo` object, this object has:
+- `DominantSpeakersInfo`: Gets the `DominantSpeakersInfo` object. This object has:
     - `Speakers`: A list of participant identifiers representing the dominant speakers list.
     - `LastUpdatedAt`: The date when the dominant speakers list was updated. 
 

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

@@ -437,7 +437,7 @@ The `videoStreamsUpdated` when a remote participant adds or removes a VideoStrea
 
 **How does your application react to the event?**
 
-If your application was processing a stream that is removed, yYour application must stop the processing. When a new stream is added, we recommend that your application start to render or process it.
+If your application was processing a stream that is removed, your application must stop the processing. When a new stream is added, we recommend that your application start to render or process it.
 
 **Code Sample:**
 

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

@@ -194,7 +194,7 @@ call.remoteParticipants
 
 ### Add a participant to a call
 
-To add a participant to a call as either a user or a phone number, call the`addParticipant` operation. This operation synchronously returns a remote participant instance.
+To add a participant to a call as either a user or a phone number, call the `addParticipant` operation. This operation synchronously returns a remote participant instance.
 
 ```swift
 let remoteParticipantAdded: RemoteParticipant = call.add(participant: CommunicationUserIdentifier(identifier: "userId"))

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

@@ -239,9 +239,10 @@ Remote participants have a set of associated properties and collections:
   const callEndReasonSubCode = callEndReason.subCode // (number) subCode associated with the reason
   ```
 
-  Notes:
-  - This property is only set when adding a remote participant via the Call.addParticipant() API, and the remote participant declines for example.
-  - In the scenario, where UserB kicks UserC, from UserA's perspective, UserA doesn't see this flag get set for UserC. In other words, UserA doesn't see UserC's callEndReason property get set at all.
+  > [!NOTE]
+  > This property is only set when adding a remote participant via the Call.addParticipant() API, and the remote participant declines for example.
+  >
+  > In the scenario, where UserB kicks UserC, from UserA's perspective, UserA doesn't see this flag get set for UserC. In other words, UserA doesn't see UserC's callEndReason property get set at all.
 
 - `isMuted` status: To find out if a remote participant is muted, check the `isMuted` property. It returns `Boolean`.
 
@@ -272,7 +273,8 @@ Remote participants have a set of associated properties and collections:
   const endpointDetails: EndpointDetails[] = remoteParticipant.endpointDetails;
   ```
 
-  Note: A remote participant could be in the call from many possible endpoints, and each endpoint has its own unique `participantId`. `participantId` is different from the `RemoteParticipant` identifier's raw ID.
+  > [!NOTE]
+  > A remote participant could be in the call from many possible endpoints, and each endpoint has its own unique `participantId`. `participantId` is different from the `RemoteParticipant` identifier's raw ID.
 
 ### Mute other participants
 
@@ -309,7 +311,8 @@ Get the local participant ID:
 const participantId: string = call.info.participantId;
 ```
 
-Note: An Azure Communication Services identity can use the web calling SDK in many endpoints, and each endpoint has its own unique `participantId`. `participantId` is different from the Azure Communication Services identity raw ID.
+> [!NOTE]
+> An Azure Communication Services identity can use the web calling SDK in many endpoints, and each endpoint has its own unique `participantId`. `participantId` is different from the Azure Communication Services identity raw ID.
 
 Retrieve the thread ID if joining a Teams meeting:
 

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

@@ -80,7 +80,7 @@ const defaultSpeaker = deviceManager.selectedSpeaker;
 await deviceManager.selectSpeaker(localCameras[0]);
 ```
 
-Each `CallAgent` can choose its own microphone and speakers on its associated `DeviceManager`. We recommend that different `CallAgents` use different microphones and speakers. They shouldn't share the same microphones nor speakers. If sharing happens, then Microphone User Facing Diagnostics (UFD) might be triggered and the microphone stops working depending on the browser and os.
+Each `CallAgent` can choose its own microphone and speakers on its associated `DeviceManager`. We recommend that different `CallAgents` use different microphones and speakers. They shouldn't share the same microphones nor speakers. If sharing happens, then Microphone User Facing Diagnostics (UFD) might be triggered and the microphone stops working depending on the browser and OS.
 
 ### Local video stream
 
@@ -155,7 +155,7 @@ console.log(result.video);
 #### Notes
 - `videoDevicesUpdated` event fires when video devices are plugging-in/unplugged.
 - `audioDevicesUpdated` event fires when audio devices are plugged.
-- When you first create `DeviceManager`, it doesn't know about any devices if permissions aren't granted yet. Initially its device name is empty and it doesn't contain detailed device information. You need to call `DeviceManager.askPermission()`, which prompts the user for device access. When the user selects allows access, the device manager learns about the devices on the system, updates device lists and sends the `audioDevicesUpdated` and `videoDevicesUpdated` events. If a user refreshes the page and creates a device manager, the device manager is able to learn about devices because user granted access previously. It has its device lists filled initially and it doesn't emit 'audioDevicesUpdated' nor 'videoDevicesUpdated' events.
+- When you first create `DeviceManager`, it doesn't know about any devices if permissions aren't granted yet. Initially its device name is empty and it doesn't contain detailed device information. You need to call `DeviceManager.askPermission()`, which prompts the user for device access. When the user allows access, the device manager learns about the devices on the system, updates device lists, and sends the `audioDevicesUpdated` and `videoDevicesUpdated` events. If a user refreshes the page and creates a device manager, the device manager learns about devices because the user previously granted access. It has its device lists filled initially and it doesn't emit `audioDevicesUpdated` nor `videoDevicesUpdated` events.
 - Speaker enumeration/selection isn't supported on Android Chrome, iOS Safari, nor macOS Safari.
 
 ## Place a call with video camera
@@ -588,6 +588,6 @@ await callObj2.mute();
 Limitations:
 - Sending video streams must be done with two different `CallAgent` instances using different identities. The code snippet shows two call agents being used, each with its own Call object.
 - In the code example, both CallAgents are joining the same call (same call IDs). You can also join different calls with each agent and send one video on one call and a different video on the other call. 
-- Sending the same camera in both CallAgent, isn't supported. They must be two different cameras.
+- Sending the same camera in both CallAgents isn't supported. They must be two different cameras.
 - Sending two different cameras with one CallAgent is currently not supported.
 - On macOS Safari, background blur video effects (from @azure/communication-effects), can only be applied to one camera, and not both at the same time.

articles/communication-services/how-tos/calling-sdk/includes/raise-hand/raise-hand-android.md

@@ -91,5 +91,5 @@ The `participantsWithRaisedHands` variable contains an array of participant obje
 
 - `identifier`: the communication identifier of the participant.
 - `order`: the order in which the participant raised their hand.
-- 
+
 You can use this information to display a list of participants with the Raise Hand state and their order in the queue.

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

@@ -48,7 +48,7 @@ The following table show support for individual APIs in the Calling SDK related
 |Start a call to Microsoft 365 user	| ✔️ | ✔️ | 		
 |Start a call to phone number | ✔️ | ✔️ | 		
 |Join a room |✔️ | | 
-|Joina a Teams meeting | ✔️	| ✔️ |
+|Join a Teams meeting | ✔️	| ✔️ |
 |Join a call based on groupId | ✔️ | |
 |Accept or reject incoming call | ✔️ | ✔️ |
 |Hold and resume call | ✔️ | ✔️ |