Skip to content

Commit 369f02b

Browse files
authored
Merge pull request #309690 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 3077121 + df4f724 commit 369f02b

24 files changed

Lines changed: 32 additions & 32 deletions

File tree

articles/active-directory-b2c/partner-asignio.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ The following diagram illustrates the implementation.
7676

7777
## Configure an application with Asignio
7878

79-
Configurating an application with Asignio is with the Asignio Partner Administration site.
79+
Configuring an application with Asignio is with the Asignio Partner Administration site.
8080

8181
1. To request access for your organization, go to asignio.com [Asignio Partner Administration](https://partner.asignio.com) page.
8282
2. With credentials, sign into Asignio Partner Administration.

articles/azure-compute-fleet/allocation-strategies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ For Spot VMs, you have the following allocation strategies available for your Co
4040

4141
The **price capacity optimized** allocation strategy is the recommended strategy for Spot VMs.
4242

43-
The Compute Fleet launches qualifying VMs from your selected list of VM types and sizes to fullfil the target capacity. It prioritizes the highest available Spot capacity at the lowest price on Spot VMs in the region. This strategy is not compatible with attribute-based VM selection.
43+
The Compute Fleet launches qualifying VMs from your selected list of VM types and sizes to fulfill the target capacity. It prioritizes the highest available Spot capacity at the lowest price on Spot VMs in the region. This strategy is not compatible with attribute-based VM selection.
4444

4545
If you select multiple VMs that happen to offer the ideal capacity to meet your target, then Compute Fleet prioritizes deploying VMs that offer the lowest price first. Followed by the second and third lowest price if sufficient capacity isn't available with the first lowest price VMs. Compute Fleet considers both price and capacity while configuring this strategy.
4646

articles/azure-netapp-files/azacsnap-tips.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ DATE_TIME OPERATION_NAME STATUS DATABASE_TYPE SID DUR
137137

138138
## Understanding the snapshot name suffix
139139

140-
The AzAcSnap snapshot name has a suffix specifically generated to prevent naming collisions and ensure unique snapshot names. The suffix is based on the time AzAcSnap is run to create the snapshot to the nearest ten-thousandths of a second, which is converted to a hexdecimal to minimize the length of the snapshot name. The following example shell script can be used to convert the hexdecimal suffix to the time the snapshot name was generated.
140+
The AzAcSnap snapshot name has a suffix specifically generated to prevent naming collisions and ensure unique snapshot names. The suffix is based on the time AzAcSnap is run to create the snapshot to the nearest ten-thousandths of a second, which is converted to a hexadecimal to minimize the length of the snapshot name. The following example shell script can be used to convert the hexadecimal suffix to the time the snapshot name was generated.
141141

142142
```bash
143143
#!/bin/sh

articles/azure-resource-manager/templates/template-cloud-consistency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -645,7 +645,7 @@ To retrieve a list of the available versions for a specific VM extension, use th
645645
Get-AzureRmVMExtensionImage -Location myLocation -PublisherName Microsoft.PowerShell -Type DSC | FT
646646
```
647647

648-
To get a list of publishers, use the [Get-AzureRmVmImagePublisher](/powershell/module/az.compute/get-azvmimagepublisher) command. To request type, use the [Get-AzureRmVMExtensionImageType](/powershell/module/az.compute/get-azvmextensionimagetype) commend.
648+
To get a list of publishers, use the [Get-AzureRmVmImagePublisher](/powershell/module/az.compute/get-azvmimagepublisher) command. To request type, use the [Get-AzureRmVMExtensionImageType](/powershell/module/az.compute/get-azvmextensionimagetype) command.
649649

650650
## Tips for testing and automation
651651

articles/communication-services/concepts/voice-video-calling/includes/user-facing-diagnostics-web.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ The following user-facing diagnostics are available:
3737
| networkReconnect | The connection was lost and the client is reconnecting to the network. | - Set to`Bad` when the network is disconnected <br/> - Set to `Poor`when the media transport connectivity is lost <br/> - Set to `Good` when a new session is connected. | Local <br/> Remote | Low bandwidth, no internet | Ensure that the call has a reliable internet connection that can sustain a voice call. For more information, see the [Network bandwidth requirement](../network-requirements.md#network-bandwidth) section. |
3838
| networkReceiveQuality | An indicator regarding incoming stream quality. | - Set to `Bad` when there's a severe problem with receiving the stream. <br/> - Set to `Poor` when there's a mild problem with receiving the stream. <br/> - Set to `Good` when there's no problem with receiving the stream. | Local <br/> Remote | Low bandwidth | Ensure that the call has a reliable internet connection that can sustain a voice call. For more information, see the [Network bandwidth requirement](../network-requirements.md#network-bandwidth) section. Suggest that the end user turn-off their camera to conserve available internet bandwidth. |
3939
| networkSendQuality | An indicator regarding outgoing stream quality. | - Set to `Bad` when there's a severe problem with sending the stream. <br/> - Set to `Poor` when there's a mild problem with sending the stream. <br/> - Set to `Good` when there's no problem with sending the stream. | Local <br/> Remote | Low bandwidth | Ensure that the call has a reliable internet connection that can sustain a voice call. For more information, see the [Network bandwidth requirement](../network-requirements.md#network-bandwidth) section. Also, suggest that the end user turn-off their camera to conserve available internet bandwidth. |
40-
| serverConnection | It shows whether a remote participant has unexpectedly disconnected from the call due to server loosing connection to client. | - Set to `Bad` when there's a severe problem with sending the stream. <br/> - Set to `Good` when there's no problem with sending the stream. | Remote | No internet connection between client and server infrastructure | Ensure that the call has a reliable internet connection that can sustain a voice call. For more information, see the [Network bandwidth requirement](../network-requirements.md#network-bandwidth) section.|
40+
| serverConnection | It shows whether a remote participant has unexpectedly disconnected from the call due to server losing connection to client. | - Set to `Bad` when there's a severe problem with sending the stream. <br/> - Set to `Good` when there's no problem with sending the stream. | Remote | No internet connection between client and server infrastructure | Ensure that the call has a reliable internet connection that can sustain a voice call. For more information, see the [Network bandwidth requirement](../network-requirements.md#network-bandwidth) section.|
4141

4242
### Audio values
4343
| Name | Description | Possible values | Location | Use cases | Mitigation steps |

articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-csharp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ After sending the metadata packet, Azure Communication Services (ACS) will begin
145145
```
146146

147147
#### DTMF example
148-
When DTMF is enabled Azure Communication Servives sends a `DtmfData` type.
148+
When DTMF is enabled Azure Communication Services sends a `DtmfData` type.
149149

150150
``` json
151151
{

articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-java.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ After sending the metadata packet, Azure Communication Services (ACS) will begin
129129
```
130130

131131
#### DTMF example
132-
When DTMF is enabled Azure Communication Servives sends a `DtmfData` type.
132+
When DTMF is enabled Azure Communication Services sends a `DtmfData` type.
133133

134134
``` json
135135
{

articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-js.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,7 @@ After sending the metadata packet, Azure Communication Services (ACS) will begin
170170
}
171171
```
172172
#### DTMF example
173-
When DTMF is enabled Azure Communication Servives sends a `DtmfData` type.
173+
When DTMF is enabled Azure Communication Services sends a `DtmfData` type.
174174

175175
``` json
176176
{

articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-python.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -142,7 +142,7 @@ After sending the metadata packet, Azure Communication Services (ACS) will begin
142142
```
143143

144144
#### DTMF example
145-
When DTMF is enabled Azure Communication Servives sends a `DtmfData` type.
145+
When DTMF is enabled Azure Communication Services sends a `DtmfData` type.
146146

147147
``` json
148148
{

articles/communication-services/tutorials/audio-quality-enhancements/includes/web.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Key traits that noise suppression enables:
2424
- Typically works on the speaker’s end before sending out the audio.
2525

2626
**Echo cancellation** removes echo caused when your microphone picks up audio from your speakers. For example, when someone is on speakerphone and their microphone picks up your voice from their speaker, it can loop back to you as an echo. Echo cancellation predicts and subtracts this returning sound so you don’t hear yourself talking back a fraction of a second later.
27-
Key traits for echo cancelation:
27+
Key traits for echo cancellation:
2828
- Reduces acoustic feedback.
2929
- Essential in open microphone and desktop setups where the microphone picks up audio output from a local speaker.
3030
- Reduces listener fatigue and confusion caused by hearing your own voice returned.
@@ -35,13 +35,13 @@ Key traits for echo cancelation:
3535
> **Noise Suppression** features are available in GA WebJS SDK version `1.28.4` or later, alongside the Azure Communication Services Calling Effects SDK version GA `1.1.2` or later. Alternatively, if you opt to use the public preview version, Calling SDK versions `1.24.2-beta.1` and later also support noise suppression.
3636
3737
> [!IMPORTANT]
38-
> **Echo Cancellation** features are available in GA WebJS SDK version [1.38.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1381-2025-09-02) or later. Also note that to use echo cancelation you must use the audio effects SDK version GA version [1.31.1](https://www.npmjs.com/package/@azure/communication-calling-effects/v/1.3.1) or later. Alternatively, if you opt to use the public preview version, Calling SDK versions [1.38.1-beta.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1381-beta1-2025-07-21) and later also support noise suppression.
38+
> **Echo Cancellation** features are available in GA WebJS SDK version [1.38.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1381-2025-09-02) or later. Also note that to use echo cancellation you must use the audio effects SDK version GA version [1.31.1](https://www.npmjs.com/package/@azure/communication-calling-effects/v/1.3.1) or later. Alternatively, if you opt to use the public preview version, Calling SDK versions [1.38.1-beta.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1381-beta1-2025-07-21) and later also support noise suppression.
3939
4040
> [!NOTE]
4141
> - Utilizing audio effects is available only on Chrome and Edge desktop browsers.
4242
> - The audio effects library isn't a standalone module and can't function independently. To utilize its capabilities the effects package must be integrated with the Azure Communication Services Calling client library for WebJS.
4343
> - If you use the GA version of the Calling SDK, you must use the [GA version](https://www.npmjs.com/package/@azure/communication-calling-effects/v/latest) of the Calling audio effects package.
44-
> - If you use the public preview version of the Calling SDK, you must use the [public prevew version](https://www.npmjs.com/package/@azure/communication-calling-effects/v/latest) of the Calling audio effects package.
44+
> - If you use the public preview version of the Calling SDK, you must use the [public preview version](https://www.npmjs.com/package/@azure/communication-calling-effects/v/latest) of the Calling audio effects package.
4545
4646
## Install the Audio Effects Package
4747
Use the `npm install` command to install the Azure Communication Services Audio Effects SDK for JavaScript.
@@ -158,8 +158,8 @@ if (isNoiseSuppressionSupported) {
158158
}
159159
```
160160

161-
## Bring it all together: Load and start noise suppression and echo cancelation
162-
To initiate a call with both **noise suppression** and **echo cancelation** enabled, create a new `LocalAudioStream` property using `AudioDeviceInfo`. Ensure that the `LocalAudioStream` source isn't set as a raw `MediaStream` property to support audio effects. Then, include this property within `CallStartOptions.audioOptions` when starting the call.
161+
## Bring it all together: Load and start noise suppression and echo cancellation
162+
To initiate a call with both **noise suppression** and **echo cancellation** enabled, create a new `LocalAudioStream` property using `AudioDeviceInfo`. Ensure that the `LocalAudioStream` source isn't set as a raw `MediaStream` property to support audio effects. Then, include this property within `CallStartOptions.audioOptions` when starting the call.
163163

164164
```js
165165
import { EchoCancellationEffect, DeepNoiseSuppressionEffect } from '@azure/communication-calling-effects';
@@ -230,14 +230,14 @@ await audioEffectsFeatureApi.stopEffects({
230230
});
231231
```
232232

233-
#### To start Azure Communication Services echo cancelation
233+
#### To start Azure Communication Services echo cancellation
234234
```js
235235
await audioEffectsFeatureApi.startEffects({
236236
noiseSuppression: echoCancellation
237237
});
238238
```
239239

240-
#### To stop Azure Communication Services echo cancelation
240+
#### To stop Azure Communication Services echo cancellation
241241
```js
242242
await audioEffectsFeatureApi.stopEffects({
243243
echoCancellation: true

0 commit comments

Comments
 (0)