Skip to content

Commit a7337e1

Browse files
Merge pull request #125351 from ArieHein/Spelling-56
Spelling Fixes
2 parents 38795ba + db0a4c8 commit a7337e1

13 files changed

+13
-13
lines changed

articles/operator-nexus/how-to-validate-cables.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ To generate a SAS URL for the container to provide write access to the Nexus Fab
9494
> [!NOTE]
9595
> The operation takes roughly 20~40 minutes to complete based on the number of racks.
9696
97-
1. Download and read the validated results from the `<CABLING_REPORT_STORAGE_URL>` retuned from the completed command.
97+
1. Download and read the validated results from the `<CABLING_REPORT_STORAGE_URL>` returned from the completed command.
9898
9999
Example output is shown in the following sections.
100100

articles/operator-nexus/howto-cluster-metrics-configuration-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Azure Operator Nexus: How to configure cluster metrics configuration management"
3-
description: This docuemnt provides instructions on how to create, list, update, retrieve, and delete cluster metrics configurations.
3+
description: This document provides instructions on how to create, list, update, retrieve, and delete cluster metrics configurations.
44
author: bryan-strassner
55
ms.author: bstrassner
66
ms.service: azure-operator-nexus

articles/operator-nexus/howto-configure-cluster.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,7 @@ az networkcloud cluster update --name "<clusterName>" /
200200
az networkcloud cluster show --resource-group "<resourceGroup>" --name "<clusterName>" | grep -a3 computeDeploymentThreshold
201201
202202
"clusterType": "MultiRack",
203-
"clusterVersion": "<CLUSER_VERSION>",
203+
"clusterVersion": "<CLUSTER_VERSION>",
204204
"computeDeploymentThreshold": {
205205
"grouping": "PerCluster",
206206
"type": "PercentSuccess",

articles/operator-nexus/howto-configure-network-packet-broker.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -450,7 +450,7 @@ Network TAP allows Operators to define destinations and encapsulation mechanism
450450
| destinationTapRuleId| ARMID of the Tap rule, which needs to be applied | |True |
451451

452452
> [!NOTE]
453-
> Network Tap rules and Neighbor Groups must be created prior to refrencing them in Network Tap
453+
> Network Tap rules and Neighbor Groups must be created prior to referencing them in Network Tap
454454
455455
### NetworkTAP device programming naming conventions/ best practices:
456456

articles/reliability/reliability-postgresql-flexible-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Reliability and high availability in PostgreSQL - Flexible Server
3-
titleSufffix: Azure Database for PostgreSQL - Flexible Server
3+
titleSuffix: Azure Database for PostgreSQL - Flexible Server
44
description: Find out about reliability and high availability in Azure Database for PostgreSQL - Flexible Server
55
author: sunilagarwal
66
ms.author: anaharris

articles/remote-rendering/tutorials/modeling/3dsmax-material-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ You might notice that not all of your textures are listed in the Asset Tracking
175175
1. In the **Specify Asset Path** box, select the local path to your textures and replace it with `.\`. Select **OK**.
176176

177177
The Asset Tracking window will update as shown in the following screenshot. This update might take a while, depending on how many textures are in your scene and on how large your scene is.
178-
![Screensthot that shows the updated Asset Tracking window.](media/3dsmax/resolve-textures.jpg)
178+
![Screenshot that shows the updated Asset Tracking window.](media/3dsmax/resolve-textures.jpg)
179179

180180
Notice that the **Full Path** column is now blank. This means that the scene is no longer looking for the relevant textures in a specific (absolute) location. It will always find them as long as the .max file or related FBX file is in the same folder as the textures.
181181

articles/remote-rendering/tutorials/unity/security/security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -353,7 +353,7 @@ With the Azure side of things in place, we now need to modify how your code conn
353353
>[!NOTE]
354354
> This code is by no means complete and is not ready for a commercial application. For example, at a minimum you'll likely want to add the ability to sign out too. This can be done using the `Task RemoveAsync(IAccount account)` method provided by the client application. This code is only intended for tutorial use, your implementation will be specific to your application.
355355

356-
The code first tries to get the token silently using **AquireTokenSilent**. This is successful if the user has previously authenticated this application. If it's not successful, move on to a more user-involved strategy.
356+
The code first tries to get the token silently using **AcquireTokenSilent**. This is successful if the user has previously authenticated this application. If it's not successful, move on to a more user-involved strategy.
357357

358358
For this code, we're using the [device code flow](../../../../active-directory/develop/v2-oauth2-device-code.md) to obtain an Access Token. This flow allows the user to sign in to their Azure account on a computer or mobile device and have the resulting token sent back to the HoloLens application.
359359

articles/sap/center-sap-solutions/deploy-s4hana.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In this how-to guide, you'll learn how to deploy S/4HANA infrastructure in *Azur
1919
- An Azure [subscription](/azure/cost-management-billing/manage/create-subscription#create-a-subscription)
2020
- [Register](/azure/azure-resource-manager/management/resource-providers-and-types#azure-portal) the **Microsoft.Workloads** Resource Provider on the subscription in which you are deploying the SAP system.
2121
- An Azure account with **Contributor** [role](/azure/role-based-access-control/role-assignments-portal-subscription-admin) access to the subscriptions and resource groups in which you'll create the Virtual Instance for SAP solutions (VIS) resource.
22-
- A **User-assigned managed** [identity](/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity) which has Contributor role access on the Subscription or atleast all resource groups (Compute, Network,Storage). If you wish to install SAP Software through the Azure Center for SAP solutions, also provide Storage Blob data Reader, Reader and Data Access roles to the identity on SAP bits storage account where you would store the SAP Media.
22+
- A **User-assigned managed** [identity](/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity) which has Contributor role access on the Subscription or at least all resource groups (Compute, Network,Storage). If you wish to install SAP Software through the Azure Center for SAP solutions, also provide Storage Blob data Reader, Reader and Data Access roles to the identity on SAP bits storage account where you would store the SAP Media.
2323
- A [network set up for your infrastructure deployment](prepare-network.md).
2424
- Availability of minimum 4 cores of either Standard_D4ds_v4 or Standard_E4s_v3 SKUS which will be used during Infrastructure deployment and Software Installation
2525
- [Review the quotas for your Azure subscription](/azure/quotas/view-quotas). If the quotas are low, you might need to create a support request before creating your infrastructure deployment. Otherwise, you might experience deployment failures or an **Insufficient quota** error.

articles/sap/center-sap-solutions/get-sap-installation-media.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Get SAP installation media
3-
description: Learn how to download the necessary SAP media for installing the SAP software and upload it for use with Azure Center for SAP solutions. Please note this is an *optional* step and media and BOM can be obtained with a method preffered by customer.
3+
description: Learn how to download the necessary SAP media for installing the SAP software and upload it for use with Azure Center for SAP solutions. Please note this is an *optional* step and media and BOM can be obtained with a method preferred by customer.
44
ms.service: sap-on-azure
55
ms.subservice: center-sap-solutions
66
ms.topic: how-to

articles/sap/workloads/businessobjects-deployment-guide-windows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ The next step is to create Azure files in the storage account. Azure files use a
126126

127127
1. Go to the storage account **azusbobi** > **File shares**.
128128
1. Select **New file share**.
129-
1. Enter the **Name** of the file share. For example, enter **frsinput** or **frsouput**.
129+
1. Enter the **Name** of the file share. For example, enter **frsinput** or **frsoutput**.
130130
1. Insert the required file share size in **Provisioned capacity**. For example, enter **256 GB**.
131131
1. Choose **SMB** as **Protocol**.
132132
1. Select **Create**.

0 commit comments

Comments
 (0)