Skip to content

Commit a86e52d

Browse files
committed
Spelling Fixes
1 parent b269a01 commit a86e52d

16 files changed

+17
-17
lines changed

articles/api-management/azure-openai-enable-semantic-caching.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Configure a [backend](backends.md) resource for the embeddings API deployment wi
6262
https://my-aoai.openai.azure.com/openai/deployments/embeddings-deployment/embeddings
6363
```
6464
* **Authorization credentials** - Go to **Managed Identity** tab.
65-
* **Client indentity** - Select *System assigned identity* or type in a User assigned managed identity client ID.
65+
* **Client identity** - Select *System assigned identity* or type in a User assigned managed identity client ID.
6666
* **Resource ID** - Enter `https://cognitiveservices.azure.com/` for Azure OpenAI Service.
6767

6868
### Test backend

articles/api-management/migrate-stv1-to-stv2-no-vnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.author: danlep
1616

1717
This article provides steps to migrate an API Management instance hosted on the `stv1` compute platform in-place to the `stv2` platform when the instance *is not* injected (deployed) in an external or internal VNet. For this scenario, migrate your instance using the Azure portal or the [Migrate to stv2](/rest/api/apimanagement/current-ga/api-management-service/migratetostv2) REST API. [Find out if you need to do this](compute-infrastructure.md#how-do-i-know-which-platform-hosts-my-api-management-instance).
1818

19-
If you need to migrate a *VNnet-injected* API Management hosted on the `stv1` platform, see [Migrate a VNet-injected API Management instance to the stv2 platform](migrate-stv1-to-stv2-vnet.md).
19+
If you need to migrate a *VNet-injected* API Management hosted on the `stv1` platform, see [Migrate a VNet-injected API Management instance to the stv2 platform](migrate-stv1-to-stv2-vnet.md).
2020

2121
[!INCLUDE [api-management-migration-alert](../../includes/api-management-migration-alert.md)]
2222

articles/api-management/migrate-stv1-to-stv2-vnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ For a VNet-inject instance, you have the following migration options:
2727

2828
Under certain, less frequent conditions, migration in the same subnet may not be possible or behaves differently. For more information, see [Special conditions and scenarios](#special-conditions-and-scenarios).
2929

30-
If you need to migrate a *non-VNnet-injected* API Management hosted on the `stv1` platform, see [Migrate a non-VNet-injected API Management instance to the stv2 platform](migrate-stv1-to-stv2-no-vnet.md).
30+
If you need to migrate a *non-VNet-injected* API Management hosted on the `stv1` platform, see [Migrate a non-VNet-injected API Management instance to the stv2 platform](migrate-stv1-to-stv2-no-vnet.md).
3131

3232
[!INCLUDE [api-management-migration-alert](../../includes/api-management-migration-alert.md)]
3333

articles/app-service/app-service-sql-asp-github-actions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ az group create --name {resource-group-name} --location {resource-group-location
6161
1. Create [two new secrets](https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository) in your GitHub repository for `SQLADMIN_PASS` and `SQLADMIN_LOGIN`. Make sure you choose a complex password, otherwise the create step for the SQL database server will fail. You won't be able to access this password again so save it separately.
6262

6363
2. Create an `AZURE_SUBSCRIPTION_ID` secret for your Azure subscription ID. If you do not know your subscription ID, use this command in the Azure Shell to find it. Copy the value in the `SubscriptionId` column.
64-
```azurecliu
64+
```azurecli
6565
az account list -o table
6666
```
6767

articles/app-service/tutorial-java-jboss-mysql-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -727,7 +727,7 @@ A few considerations:
727727
728728
#### How do I get a valid access token for the MySQL connection using Microsoft Entra authentication?
729729
730-
For a Microsoft Entra user, a system-assigned managed identity, or a user-asssigned managed identity that's authorized to access the MySQL database, Azure CLI can help you generate an access token. In case of a managed identity, the identity must be configured on the App Service app or VM where you run Azure CLI.
730+
For a Microsoft Entra user, a system-assigned managed identity, or a user-assigned managed identity that's authorized to access the MySQL database, Azure CLI can help you generate an access token. In case of a managed identity, the identity must be configured on the App Service app or VM where you run Azure CLI.
731731
732732
```azurecli-interactive
733733
# Sign in as a Microsoft Entra user

articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ In this example, you create a new virtual network. You can create a virtual netw
6767
13. Select **Add**.
6868
14. Select **Next:Configuration**.
6969
15. Under **Routing rules**, select **Add a routing rule**.
70-
16. For **Rule name**, type *Rrule-01*.
70+
16. For **Rule name**, type *Rule-01*.
7171
17. For **Listener name**, type *Listener-01*.
7272
18. For **Frontend IP**, select **Private**.
7373
19. Accept the remaining defaults and select the **Backend targets** tab.

articles/application-gateway/for-containers/how-to-cert-manager-lets-encrypt-gateway-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This guide demonstrates how to use cert-manager to automatically issue and renew
1515

1616
For the purposes of this example, we have cert-manager configure certificates issued from Let's Encrypt to demonstrate an end-to-end deployment, where Application Gateway for Containers is providing TLS offloading.
1717

18-
![A figure showing cert-manager retrieving a certificate from Let's Encrypt and storing it into Kubernete's secret store for TLS with Application Gateway for Containers.](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg)
18+
![A figure showing cert-manager retrieving a certificate from Let's Encrypt and storing it into Kubernetes' secret store for TLS with Application Gateway for Containers.](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg)
1919

2020
For certificates to be issued by Let's Encrypt, a challenge is required by the authority to validate domain ownership. This validation happens by allowing cert-manager to create a pod and HTTPRoute resource that exposes an endpoint during certificate issuance, proving your ownership of the domain name.
2121

articles/automanage/how-to-disable-automanage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ You may decide one day to disable Automanage on certain VMs. For instance, your
1717

1818
## How to disable Automanage through the Azure portal
1919

20-
To do that in the Azure portal, go to the **Automanage – Azure machine best practices** page that lists all of your auto-managed VMs. Select the checkbox next to the virtual machine you want to disable from Automanage, then click on the **Disable automanagment** button.
20+
To do that in the Azure portal, go to the **Automanage – Azure machine best practices** page that lists all of your auto-managed VMs. Select the checkbox next to the virtual machine you want to disable from Automanage, then click on the **Disable automanagement** button.
2121

2222
[ ![Screenshot of disabling Automanage on a virtual machine.](./media/automanage-virtual-machines/disable-step-1.png) ](./media/automanage-virtual-machines/disable-step-1.png#lightbox)
2323

articles/automanage/quick-create-virtual-machines-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ Quickly stop using Azure Automanage for virtual machines by disabling automanage
7171

7272
1. Go to the **Automanage – Azure virtual machine best practices** page that lists all of your auto-managed VMs.
7373
1. Select the checkbox next to the virtual machine you want to disable.
74-
1. Click on the **Disable automanagent** button.
74+
1. Click on the **Disable automanagement** button.
7575
1. Read carefully through the messaging in the resulting pop-up before agreeing to **Disable**.
7676

7777

articles/azure-functions/functions-bindings-azure-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -258,7 +258,7 @@ Azure SQL bindings for Azure Functions have a required property for the connecti
258258
- This binding requires connectivity to an Azure SQL or SQL Server database.
259259
- Output bindings against tables with columns of data types `NTEXT`, `TEXT`, or `IMAGE` aren't supported and data upserts will fail. These types [will be removed](/sql/t-sql/data-types/ntext-text-and-image-transact-sql) in a future version of SQL Server and aren't compatible with the `OPENJSON` function used by this Azure Functions binding.
260260
- Use [managed identities](/azure/azure-sql/database/authentication-azure-ad-user-assigned-managed-identity) instead of usernames and passwords.
261-
- Concider using an [Azure Key Value](/azure/app-service/app-service-key-vault-references) to store application settings.
261+
- Consider using an [Azure Key Value](/azure/app-service/app-service-key-vault-references) to store application settings.
262262

263263
## Samples
264264

0 commit comments

Comments
 (0)