Merge pull request #124982 from ArieHein/Spelling-Wave-2

Spelling Fixes - Wave 2

Author: ttorble

articles/analysis-services/analysis-services-addservprinc-admins.md

@@ -95,7 +95,7 @@ The following Resource Manager template deploys an Analysis Services server with
 
 ## Using managed identities
 
-Managed identies that are added to database or server roles will be unable to login to the service or do any operations. Managed identities for service principals are not supported in Azure Analysis Services.
+Managed identities that are added to database or server roles will be unable to login to the service or do any operations. Managed identities for service principals are not supported in Azure Analysis Services.
 
 ## Related information
 

articles/analysis-services/analysis-services-database-users.md

@@ -62,7 +62,7 @@ When adding a **service principal** use `app:appid@tenantid`.
 
 To add roles and users to a deployed model database, you must be connected to the server as a Server administrator or already in a database role with administrator permissions.
 
-1. In Object Exporer, right-click **Roles** > **New Role**.
+1. In Object Explorer, right-click **Roles** > **New Role**.
 
 2. In **Create Role**, enter a role name and description.
 

articles/analysis-services/analysis-services-scale-out.md

@@ -61,7 +61,7 @@ Use SSMS to set ReplicaSyncMode in Advanced Properties. The possible values are:
 - `1` (default): Full replica database rehydration in stages (incremental). 
 - `2`: Optimized synchronization in parallel. 
 
-![RelicaSyncMode setting](media/analysis-services-scale-out/aas-scale-out-sync-mode.png)
+![ReplicaSyncMode setting](media/analysis-services-scale-out/aas-scale-out-sync-mode.png)
 
 When setting **ReplicaSyncMode=2**, depending on how much of the cache needs to be updated, more memory may be consumed by the query replicas. To keep the database online and available for queries, depending on how much of the data has changed, the operation can require up to *double the memory* on the replica because both the old and new segments are kept in memory simultaneously. Replica nodes have the same memory allocation as the primary node, and there's normally extra memory on the primary node for refresh operations, so it may be unlikely that the replicas would run out of memory. Additionally, the common scenario is that the database is incrementally updated on the primary node, and therefore the requirement for double the memory should be uncommon. If the Sync operation does encounter an out of memory error, it retries using the default technique (attach/detach two at a time). 
 

articles/api-center/manage-apis-azure-cli.md

@@ -125,7 +125,7 @@ Use the [az apic api delete](/cli/azure/apic/api#az_apic_api_delete) command to
 
 ```azurecli-interactive
 az apic api delete \
-    --resource-group myResoureGroup --service-name myAPICenter \
+    --resource-group myResourceGroup --service-name myAPICenter \
     --api-id petstore-api
 ```
 

articles/api-management/api-management-howto-api-inspector.md

@@ -149,7 +149,7 @@ For information about customizing trace information, see the [trace](trace-polic
 In this tutorial, you learned how to:
 
 > [!div class="checklist"]
-> * Trace an example call in the test conosle
+> * Trace an example call in the test console
 > * Review request processing steps
 > * Enable tracing for an API
 

articles/api-management/developer-portal-wordpress-plugin.md

@@ -69,7 +69,7 @@ In this step, create a new Microsoft Entra app. In later steps, you configure th
 
     `https://<apim-instance-name>.developer.azure-api.net/signin`
 
-1. Select **+ Add a platform** again. Select **Single-page application** agaain.
+1. Select **+ Add a platform** again. Select **Single-page application** again.
 1. On the **Configure single-page application** page, enter the following redirect URI, substituting the name of your API Management instance, and select **Configure**:
 
     `https://<apim-instance-name>.developer.azure-api.net/`

articles/api-management/http-data-source-policy.md

@@ -128,7 +128,7 @@ type User {
 </http-data-source>
 ```
 
-### Resolver for a GraqhQL query that returns a list, using a liquid template
+### Resolver for a GraphQL query that returns a list, using a liquid template
 
 The following example uses a liquid template, supported for use in the [set-body](set-body-policy.md) policy, to return a list in the HTTP response to a query.  It also renames the `username` field in the response from the REST API to `name` in the GraphQL response.
 

articles/api-management/private-endpoint.md

@@ -166,7 +166,7 @@ If a private endpoint connection is in pending status, an owner of the API Manag
 
 If you have sufficient permissions, approve a private endpoint connection on the API Management instance's **Private endpoint connections** page in the portal. In the connection's context (...) menu, select **Approve**.
 
-You can also use the API Management [Private Endpoint Connection - Create Or Update](/rest/api/apimanagement/private-endpoint-connection/create-or-update) REST API to approve pending private endpoint connectionis.
+You can also use the API Management [Private Endpoint Connection - Create Or Update](/rest/api/apimanagement/private-endpoint-connection/create-or-update) REST API to approve pending private endpoint connections.
 
 ### Optionally disable public network access
 

articles/api-management/validate-jwt-policy.md

@@ -119,7 +119,7 @@ The `validate-jwt` policy enforces existence and validity of a supported JSON we
 * The policy supports both symmetric and asymmetric signing algorithms: 
     * **Symmetric** - The following encryption algorithms are supported: A128CBC-HS256, A192CBC-HS384, A256CBC-HS512.
     	* If used in the policy, the key must be provided inline within the policy in the Base64-encoded form.
-    * **Asymmetric** - The following encryption algortithms are supported: PS256, RS256, RS512, ES256. 
+    * **Asymmetric** - The following encryption algorithms are supported: PS256, RS256, RS512, ES256. 
     	* If used in the policy, the key may be provided either via an OpenID configuration endpoint, or by providing the ID of an uploaded certificate (in PFX format) that contains the public key, or the modulus-exponent pair of the public key.
 * To configure the policy with one or more OpenID configuration endpoints for use with a self-hosted gateway, the OpenID configuration endpoints URLs must also be reachable by the cloud gateway.
 * You can use access restriction policies in different scopes for different purposes. For example, you can secure the whole API with Microsoft Entra authentication by applying the `validate-jwt` policy on the API level, or you can apply it on the API operation level and use `claims` for more granular control.