Spelling Fixes

Author: ArieHein

articles/communication-services/concepts/analytics/logs/email-logs.md

@@ -108,7 +108,7 @@ By tracking these logs, you can ensure full visibility into your email delivery
 | `Category` | The log category of the event. The category is the granularity at which you can enable or disable logs on a particular resource. The properties that appear within the properties blob of an event are the same within a particular log category and resource type. |
 | `CorrelationID` | The ID for correlated events. Can be used to identify correlated events between multiple tables. For all Email operational logs, the CorrelationId is mapped to the MessageId, which is returned from a successful SendMail request. |
 | `RecipientId` | The email address for the targeted recipient. It is only present for recipient-level events. If this is a message-level event, the property will be empty. |
-| `DeliveryStatus` | The terminal status of the message. Possible valuse for message-level event are: `Dropped`, `OutForDelivery`, `Queued`. Possible valuse for a recipient-level event are: `Delivered`, `Expanded`, `Failed`, `Quarantined`, `FilteredSpam`, `Suppressed`, `Bounced`. |
+| `DeliveryStatus` | The terminal status of the message. Possible values for message-level event are: `Dropped`, `OutForDelivery`, `Queued`. Possible values for a recipient-level event are: `Delivered`, `Expanded`, `Failed`, `Quarantined`, `FilteredSpam`, `Suppressed`, `Bounced`. |
 | `SmtpStatusCode` | SMTP status code returned from the recipient email server in response to a send mail request.
 | `EnhancedSmtpStatusCode` | Enhanced SMTP status code returned from the recipient email server.
 | `SenderDomain` | The domain portion of the SenderAddress used in sending emails.

articles/communication-services/concepts/analytics/logs/voice-and-video-logs.md

@@ -84,7 +84,7 @@ The call summary log contains data to help you identify key properties of all ca
 | `osVersion` | A string representing the operating system and version of each endpoint device. |
 | `participantTenantId` | The ID of the Microsoft tenant associated with the identity of the participant. The tenant can either be the Azure tenant that owns the Azure Communication Services resource or the Microsoft tenant of a Microsoft 365 identity. This field is used to guide cross-tenant redaction. |
 | `participantType` | Description of the participant as a combination of its client (Azure Communication Services or Teams), and its identity (Azure Communication Services or Microsoft 365). Possible values include: Azure Communication Services (Azure Communication Services identity and Azure Communication Services SDK), Teams (Teams identity and Teams client), Azure Communication Services as Teams external user (Azure Communication Services identity and Azure Communication Services SDK in Teams call or meeting), Azure Communication Services as Microsoft 365 user (Microsoft 365 identity and Azure Communication Services client), and Teams Voice Apps. |
-| `pstnPartcipantCallType` | Represents the type and direction of PSTN participants including Emergency calling, direct routing, transfer, forwarding, and so on. | 
+| `pstnParticipantCallType` | Represents the type and direction of PSTN participants including Emergency calling, direct routing, transfer, forwarding, and so on. | 
 | `ParticipantEndSubCode `| Represents the Calling SDK error subcode that the SDK emits (when relevant) for each `participantId` value. | 
 | `ResultCategory `| Represents the category of the participant ending the call. It can be one of these 4 values: Success, ExpectedError, UnexpectedClientError, UnexpectedServerError. |
 

articles/communication-services/concepts/call-automation/azure-communication-services-azure-cognitive-services-integration.md

@@ -51,7 +51,7 @@ You'll need to connect your Azure Communication Services resource with the Azure
    [![Screenshot of Enable Managed Identity button.](./media/enabled-identity.png)](./media/enabled-identity.png#lightbox)
 
 4. Enable system assigned identity. This action begins the creation of the identity; A pop-up notification appears notifying you that the request is being processed.
-  [![Screen shot of enable managed identiy.](./media/enable-system-identity.png)](./media/enable-system-identity.png#lightbox)
+  [![Screen shot of enable managed identity.](./media/enable-system-identity.png)](./media/enable-system-identity.png#lightbox)
 
 5. Once the identity is enabled, you should see something similar.
    [![Screenshot of enabled identity.](./media/identity-saved.png)](./media/identity-saved.png#lightbox)

articles/communication-services/concepts/call-automation/real-time-transcription.md

@@ -25,7 +25,7 @@ Out of the box Microsoft utilizes a Universal Language Model as a base model tha
 ### Improved customer experience
 Assist agents better understand customer needs and respond more quickly and accurately, leading to a better overall customer experience.
 
-### Increased efficency 
+### Increased efficiency 
 Help agents focus on the conversation rather than note-taking, allowing them to handle more calls and improve productivity
 
 ### Context for agents

articles/communication-services/concepts/email-metrics.md

@@ -40,12 +40,12 @@ The following dimensions are available on the `Email Service Delivery Status Upd
 | MessageStatus       | Terminal state of the Delivered, Failed, Suppressed. Emails are suppressed when a user sends an email to an email address that is known not to exist. Sending emails to addresses that don't exist trigger a hard bounce. |
 | IsHardBounce       | True when a message delivery failed due to a hard bounce or if an item was suppressed due to a previous hard bounce. |
 | SenderDomain       | The domain portion of the senders email address. |
-| SmtpStatusCode       | Smpt error code from for failed deliveries. |
+| SmtpStatusCode       | Smtp error code from for failed deliveries. |
 | EnhancedSmtpStatusCode       | The EnhancedSmtpStatusCode status code will be emitted if it's available. This status code provides other details not available with the SmtpStatusCode. |
 
 :::image type="content" source="./media/acs-email-delivery-status-hardbounce-metrics.png" alt-text="Screenshot showing the Email delivery status update metric - IsHardBounce.":::
 
-:::image type="content" source="./media/acs-email-delivery-status-smtp-metrics.png" alt-text="Screenshot showing the Email delivery status update metric - SmptStatusCode.":::
+:::image type="content" source="./media/acs-email-delivery-status-smtp-metrics.png" alt-text="Screenshot showing the Email delivery status update metric - SmtpStatusCode.":::
 
 ### Email Service API requests
 

articles/communication-services/concepts/includes/enable-interoperability-for-teams-tenant.md

@@ -37,7 +37,7 @@ You'll be informed about the modules that will be installed, which you can confi
 
 ### 2. Connect to Microsoft Teams module
 
-When the module is installed and ready, you can connect to the MicrosftTeams module with the following command. You'll be prompted with an interactive window to log in. The user account that you're going to use needs to have Teams administrator permissions. Otherwise, you might get an `access denied` response in the next steps.
+When the module is installed and ready, you can connect to the MicrosoftTeams module with the following command. You'll be prompted with an interactive window to log in. The user account that you're going to use needs to have Teams administrator permissions. Otherwise, you might get an `access denied` response in the next steps.
 
 ```script
 Connect-MicrosoftTeams

articles/communication-services/concepts/includes/identifiers/identifiers-android.md

@@ -132,7 +132,7 @@ else if (communicationIdentifier instanceof PhoneNumberIdentifier) {
     Log.i(tag, "Phone number: " + ((PhoneNumberIdentifier)communicationIdentifier).getPhoneNumber());
 }
 else if (communicationIdentifier instanceof UnknownIdentifier) {
-    Log.i(tag, "Unkown user: " + ((UnknownIdentifier)communicationIdentifier).getId());
+    Log.i(tag, "Unknown user: " + ((UnknownIdentifier)communicationIdentifier).getId());
 }
 else {
     // be careful here whether you want to throw because a new SDK version

articles/communication-services/concepts/includes/identifiers/identifiers-java.md

@@ -132,7 +132,7 @@ else if (communicationIdentifier instanceof PhoneNumberIdentifier) {
     System.out.println("Phone number: " + ((PhoneNumberIdentifier)communicationIdentifier).getPhoneNumber());
 }
 else if (communicationIdentifier instanceof UnknownIdentifier) {
-    System.out.println("Unkown user: " + ((UnknownIdentifier)communicationIdentifier).getId());
+    System.out.println("Unknown user: " + ((UnknownIdentifier)communicationIdentifier).getId());
 }
 else {
     // be careful here whether you want to throw because a new SDK version

articles/communication-services/concepts/interop/guest/teams-administration.md

@@ -89,7 +89,7 @@ Teams administrators can use meeting templates to control meeting settings that
 ||Enable Watermarks|Specifies if watermarks are used for camera feeds and content that's shared on screen in the meeting.
 |Audio and video|Enable mic for attendees? |	When off, you can unmute individual attendees as needed.
 ||Enable camera for attendees? | When on, meeting attendees can turn on video.
-|Recording and transcription|Record meetings automatically|	 Speficy if the meeting is recorded automatically.
+|Recording and transcription|Record meetings automatically|	 Specify if the meeting is recorded automatically.
 ||Who can record meetings?| Specifies who can record the meeting.
 |Roles|Notify when callers join and leave|A sound plays when someone calling in by phone joins or leaves the meeting.
 |Meeting engagement|Allow meeting chat|	Specifies if the meeting chat is available. It can also be used to prevent chatting before and after the meeting.

articles/communication-services/concepts/notifications.md

@@ -28,7 +28,7 @@ Learn more about [event handling in Azure Communication Services](../../event-gr
 ## Deliver push notifications via Azure Notification Hubs
 
 > [!IMPORTANT]
-> Azure Notification Hubs has announced that Firebase Cloud Messaging (FCM) legacy API will be deprecated in July 2024. This will affect all Azure Communiation Services Calling and Chat applications who send Android push notifications. Customers impacted will need to migrate their registrations from FCM legacy to FCM v1, and can start doing so in March 2024. For more information including migration steps, please see [Notifcation Hub documentation](../../notification-hubs/notification-hubs-gcm-to-fcm.md).
+> Azure Notification Hubs has announced that Firebase Cloud Messaging (FCM) legacy API will be deprecated in July 2024. This will affect all Azure Communication Services Calling and Chat applications who send Android push notifications. Customers impacted will need to migrate their registrations from FCM legacy to FCM v1, and can start doing so in March 2024. For more information including migration steps, please see [Notification Hub documentation](../../notification-hubs/notification-hubs-gcm-to-fcm.md).
 
 You can connect an Azure Notification Hub to your Communication Services resource in order to automatically send push notifications to a user's mobile device when they receive an incoming call or to notify them about missed chat activity. You should use these push notifications to wake up your application from the background and display UI that lets the user accept or decline the call or read the newly received chat message. 
 

articles/communication-services/concepts/sms/sms-faq.md

@@ -179,7 +179,7 @@ New limits are as follows:
 
 After submission of the form, we coordinate with our downstream peer to get the application verified by the toll-free messaging aggregator. While we're reviewing your application, we may reach out to you for more information.
 - From Application Submitted to Pending = **1-5 business days** 
-- From Pending to Verdict (Verfied/Rejected/More info needed) = **4-5 weeks**. The toll-free aggregator is currently facing a high volume of applications, so new applications can take around eight weeks to be approved.
+- From Pending to Verdict (Verified/Rejected/More info needed) = **4-5 weeks**. The toll-free aggregator is currently facing a high volume of applications, so new applications can take around eight weeks to be approved.
 
 The whole toll-free verification process takes about **5-6 weeks**. These timelines are subject to change depending on the volume of applications to the toll-free messaging aggregator and the [quality](#what-is-considered-a-high-quality-toll-free-verification-application) of your application. The toll-free aggregator is currently facing a high volume of applications due to which applications can take around eight weeks to get approved.
 
@@ -203,7 +203,7 @@ Pointers to ensure you're submitting a high quality application:
 
 ### What are the ineligible use cases for toll-free verification?
 
-| High-Risk Financial Services    | Get Rich Quick Schemes            | Debt Forgiveness                 | Illegal Substances/Activites | General                  |
+| High-Risk Financial Services    | Get Rich Quick Schemes            | Debt Forgiveness                 | Illegal Substances/Activities | General                  |
 |---------------------------------|-----------------------------------|----------------------------------|------------------------------|--------------------------|
 | Payday loans                    | Debt consolidation                | Work from home programs          | Cannabis                     | Phishing                 |
 | Short-term, high-interest loans | Debt reduction                    | Risk investment opportunities    | Alcohol                      | Fraud or scams           |

articles/communication-services/concepts/telephony/emergency-calling-concept.md

@@ -15,7 +15,7 @@ ms.subservice: pstn
 
 [!INCLUDE [Emergency Calling Notice](../../includes/emergency-calling-notice-include.md)]
 
-You can use the Azure Communication Services Calling SDK to add Enhanced Emergency dialing and Public Safety Answering Point (PSAP) callback support to your applications in the United States (US), Puerto Rico (PR), the United Kingdom (GB), Canada (CA), Denmark (DK) and Australiua (AU). The capability to dial 911 (in US, PR, and CA), to dial 112 (in DK), to dial 000 (in AU) and to dial 999 or 112 (in GB) and receive a callback might be a requirement for your application. Verify the emergency calling requirements with your legal counsel.
+You can use the Azure Communication Services Calling SDK to add Enhanced Emergency dialing and Public Safety Answering Point (PSAP) callback support to your applications in the United States (US), Puerto Rico (PR), the United Kingdom (GB), Canada (CA), Denmark (DK) and Australia (AU). The capability to dial 911 (in US, PR, and CA), to dial 112 (in DK), to dial 000 (in AU) and to dial 999 or 112 (in GB) and receive a callback might be a requirement for your application. Verify the emergency calling requirements with your legal counsel.
 
 Calls to an emergency number are routed over the Microsoft network. Microsoft assigns a temporary phone number as the Call Line Identity (CLI) when a user places an emergency call from US, PR, GB, CA, DK or AU. Microsoft temporarily maintains a mapping of the phone number to the caller's identity.
 

articles/communication-services/concepts/telephony/trial-phone-numbers-faq.md

@@ -49,7 +49,7 @@ Verifying the recipient phone number is a security measure that ensures the tria
 The verification process involves sending a one-time passcode via SMS to the recipient phone number. The recipient needs to enter this code in the Azure portal to complete the verification. 
 
 ### From where can I verify phone numbers?
-Currently, only phone numbers that originate from the United States (i.e., have a +1 preffix) can be verified for use with trial phone numbers. 
+Currently, only phone numbers that originate from the United States (i.e., have a +1 prefix) can be verified for use with trial phone numbers. 
 
 ### Can I verify multiple recipient phone numbers for the same trial phone number?
 Currently the trial phone number can be verified for up to three recipient phone numbers. If you need to make calls to more numbers, then you'll need to [purchase a phone number](../../quickstarts/telephony/get-phone-number.md)

articles/communication-services/concepts/voice-video-calling/about-call-types.md

@@ -50,7 +50,7 @@ We support H.264 (MPEG-4) video codec.
 | **Sending video**    | 720P  | 720P  | 720P    | 1080P   |
 | **Sending screen share**    | 1080P  | 1080P  | 1080P    | 1080P   |
 
-The resolution can vary depending on the number of participants on a call, the amount of bandwidth available to the client, hardware capabilities of local participant who renders remote video streans and other overall call parameters.
+The resolution can vary depending on the number of participants on a call, the amount of bandwidth available to the client, hardware capabilities of local participant who renders remote video streams and other overall call parameters.
 
 ## Next steps
 

articles/communication-services/concepts/voice-video-calling/calling-sdk-features.md

@@ -177,13 +177,13 @@ The Azure Communication Services Calling SDK supports the following streaming co
 
 
 \* Starting from Azure Communication Services Web Calling SDK version [1.16.3](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1163-stable-2023-08-24)
-While the Calling SDK doesn't enforce these limits, your users might experience performance degradation if they're exceeded. Use the API of [Optimal Video Count](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#remote-video-quality) to determine how many current incoming video streams your web environment can support. To properly support 16 incoming videos the computer should have a mimimum of 16GB RAM and a 4-core or greater CPU that is no older than 3 years old
+While the Calling SDK doesn't enforce these limits, your users might experience performance degradation if they're exceeded. Use the API of [Optimal Video Count](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#remote-video-quality) to determine how many current incoming video streams your web environment can support. To properly support 16 incoming videos the computer should have a minimum of 16GB RAM and a 4-core or greater CPU that is no older than 3 years old
 
 ## Supported video resolutions
 The Azure Communication Services Calling SDK automatically adjusts resolutions of video and screen share streams during the call.
 
 > [!NOTE]
-> The resolution can vary depending on the number of participants on a call, the amount of bandwidth available to the client, hardware capabilities of local participant who renders remote video streans and other overall call parameters.
+> The resolution can vary depending on the number of participants on a call, the amount of bandwidth available to the client, hardware capabilities of local participant who renders remote video streams and other overall call parameters.
 
 The Azure Communication Services Calling SDK supports sending following video resolutions
 

articles/communication-services/concepts/voice-video-calling/includes/media-stats/media-stats-android.md

@@ -45,7 +45,7 @@ mediaStatisticsCallFeature.addOnReportReceivedListener(handleReportReceivedListe
 // Optionally, set the interval for media statistics report generation
 mediaStatisticsCallFeature.updateReportIntervalInSeconds(15);
 
-private void handleReportReceivedListener(MediaStatisticssReportEvent args) {
+private void handleReportReceivedListener(MediaStatisticsReportEvent args) {
     // Obtain the media statistics report instance
     MediaStatisticsReport report = args.getReport();
 

articles/communication-services/concepts/voice-video-calling/includes/media-stats/media-stats-web.md

@@ -237,7 +237,7 @@ Compared to the previous beta versions, we also made some minor changes to the A
 
 In the previous beta versions, `pairRttInMs`, `availableBitrate` were included in audio, video, and screenShare statistics. Now these metrics are separated into transport metrics.
 
-We introduced `packets` and `packetsLost` metric fields in audio, video, screenShare statistics. These metrics are useful for calculating the total number of packets sent or recieved between two different time points.
+We introduced `packets` and `packetsLost` metric fields in audio, video, screenShare statistics. These metrics are useful for calculating the total number of packets sent or received between two different time points.
 
 The `frameRateOutput` in video and screenShare statistics is removed. You can use `frameRateDecoded` instead.