fixing broken bookmark

paulth1 · paulth1 · commit 4816acd3b116 · 2025-05-14T17:54:28.000-07:00
diff --git a/articles/app-service/configure-custom-container.md b/articles/app-service/configure-custom-container.md
@@ -581,4 +581,4 @@ The following lists show supported and unsupported Docker Compose configuration
 Or, see more resources:
 
 - [Environment variables and app settings reference](reference-app-settings.md)
-- [Load certificate in Windows/Linux containers](configure-ssl-certificate-in-code.md#load-certificate-in-linuxwindows-containers)
+- [Load certificates in Windows/Linux containers](configure-ssl-certificate-in-code.md#load-certificates-in-linuxwindows-containers)
diff --git a/articles/app-service/configure-ssl-app-service-certificate.md b/articles/app-service/configure-ssl-app-service-certificate.md
@@ -13,7 +13,7 @@ author: msangapu-msft
 
 # Buy and manage App Service certificates
 
-This article shows how to create an Azure App Service certificate and perform management tasks like renewing, synchronizing, and deleting certificates. After you have an App Service certificate, you can then import it into an App Service app. An App Service certificate is a private certificate that Azure manages. It combines the simplicity of automated certificate management and the flexibility of renewal and export options.
+This article shows you how to create an Azure App Service certificate and perform management tasks like renewing, synchronizing, and deleting certificates. After you have an App Service certificate, you can then import it into an App Service app. An App Service certificate is a private certificate that Azure manages. It combines the simplicity of automated certificate management and the flexibility of renewal and export options.
 
 If you purchase an App Service certificate from Azure, Azure manages the following tasks:
 
@@ -53,7 +53,7 @@ Currently, App Service certificates aren't supported in Azure national clouds.
    | **Certificate name** | The friendly name for your App Service certificate. |
    | **Enable auto renewal** | Select whether to automatically renew the certificate before expiration. Each renewal extends the certificate expiration by one year. The cost is charged to your subscription. |
 
-1. When deployment is finished, select **Go to resource**.
+1. After the deployment is finished, select **Go to resource**.
 
 #### Store the certificate in Azure Key Vault
 
@@ -63,7 +63,7 @@ Currently, App Service certificates aren't supported in Azure national clouds.
 
     :::image type="content" source="media/configure-ssl-certificate/configure-key-vault.png" alt-text="Screenshot that shows the Certificate Configuration pane with Step 1: Store selected.":::
 
-1. On the **Key Vault Status** page, select **Select from Key Vault**.
+1. On the **Key Vault Status** page, choose **Select from Key Vault**.
 
 1. If you create a new vault, set up the vault based on the following table. Make sure to use the same subscription and resource group as your App Service app.
 
@@ -206,7 +206,7 @@ Set-Content -Path appservicecertificate.pfx -Value $CertBytes -AsByteStream
 
 ---
 
-The downloaded .pfx file is a raw PKCS12 file that contains both the public and private certificates and has an import password that's an empty string. You can locally install the file by leaving the password field empty. You can't [upload the file as-is into App Service](configure-ssl-certificate.md#upload-a-private-certificate) because the file isn't [password protected](configure-ssl-certificate.md#private-certificate-requirements).
+The downloaded .pfx file is a raw PKCS12 file that contains both the public and private certificates and has an import password that's an empty string. You can locally install the file by leaving the password field empty. You can't [upload the file as it is into App Service](configure-ssl-certificate.md#upload-a-private-certificate) because the file isn't [password protected](configure-ssl-certificate.md#private-certificate-requirements).
 
 ## Use Azure Advisor for App Service certificates
 
@@ -220,7 +220,7 @@ To view Advisor recommendations for the App Service certificate:
 
 1. On the left pane, select **Recommendations** > **Reliability**.
 
-1. Select the filter option **Type equals** and search for **App Service Certificates** from the dropdown list. If the value doesn't exist on the dropdown menu, that means no recommendation was generated for your App Service certificate resources because none of them requires domain ownership verification.
+1. Select the filter option **Type equals** and search for **App Service Certificates** in the dropdown list. If the value doesn't exist in the dropdown list, that means no recommendation was generated for your App Service certificate resources because none of them requires domain ownership verification.
 
 ### Create Advisor alerts
 
diff --git a/articles/app-service/configure-ssl-bindings.md b/articles/app-service/configure-ssl-bindings.md
@@ -46,9 +46,9 @@ In the <a href="https://portal.azure.com" target="_blank">Azure portal</a>:
 1. In **TLS/SSL type**, select either **SNI SSL** or **IP based SSL**:
 
     - [SNI SSL](https://en.wikipedia.org/wiki/Server_Name_Indication): You can add multiple Server Name Indication (SNI) Secure Sockets Layer (SSL) bindings. This option allows multiple Transport Layer Security (TLS)/SSL certificates to help secure multiple domains on the same IP address. Most modern browsers (including Microsoft Edge, Chrome, Firefox, and Opera) support SNI. (For more information, see [Server Name Indication](https://wikipedia.org/wiki/Server_Name_Indication).)
-    - **IP based SSL**: You can add only one IP SSL binding. This option allows only one TLS/SSL certificate to help secure a dedicated public IP address. After you configure the binding, follow the steps in [Remap records for IP-based SSL](#remap-records-for-ip-based-ssl).<br/>IP-based SSL is supported only in the Standard tier or higher.
+    - **IP based SSL**: You can add only one IP SSL binding. This option allows only one TLS/SSL certificate to help secure a dedicated public IP address. After you configure the binding, follow the steps in [Remap records for IP-based SSL](#remap-records-for-ip-based-ssl). IP-based SSL is supported only in the Standard tier or higher.
 
-1. When you add a new certificate, validate the new certificate by selecting **Validate**.
+1. When you add a new certificate, select **Validate** to validate the new certificate.
 
 1. Select **Add**.
 
@@ -86,7 +86,7 @@ If your app gives you certificate validation errors, you're probably using a sel
 
 #### How do I make sure that the app's IP address doesn't change when I make changes to the certificate binding?
 
-Your inbound IP address can change when you delete a binding, even if that binding is IP SSL. This behavior is especially important when you renew a certificate that's already in an IP SSL binding. To avoid a change in your app's IP address, follow these steps, in order:
+Your inbound IP address can change when you delete a binding, even if that binding is IP SSL. This behavior is especially important when you renew a certificate that's already in an IP SSL binding. To avoid a change in your app's IP address, follow these steps:
 
 1. Upload the new certificate.
 1. Bind the new certificate to the custom domain that you want without deleting the old one. This action replaces the binding instead of removing the old one.
diff --git a/articles/app-service/configure-ssl-certificate-in-code.md b/articles/app-service/configure-ssl-certificate-in-code.md
@@ -14,7 +14,7 @@ author: msangapu-msft
 
 In your application code, you can access the [public or private certificates that you add to Azure App Service](configure-ssl-certificate.md). Your app code might act as a client and access an external service that requires certificate authentication. It might also need to perform cryptographic tasks. This article shows how to use public or private certificates in your application code.
 
-This approach to using certificates in your code makes use of the Transport Layer Security (TLS) functionality in App Service, which requires your app to be in the Basic tier or higher. If your app is in the Free or Shared tier, you can [include the certificate file in your app repository](#load-certificate-from-file).
+This approach to using certificates in your code makes use of the Transport Layer Security (TLS) functionality in App Service, which requires your app to be in the Basic tier or higher. If your app is in the Free or Shared tier, you can [include the certificate file in your app repository](#load-a-certificate-from-a-file).
 
 When you let App Service manage your TLS/Secure Sockets Layer (SSL) certificates, you can maintain the certificates and your application code separately and safeguard your sensitive data.
 
diff --git a/articles/app-service/configure-ssl-certificate.md b/articles/app-service/configure-ssl-certificate.md
@@ -116,7 +116,7 @@ To import an App Service certificate, first [buy and configure an App Service ce
 1. On the left pane of your app, select **Certificates** > **Bring your own certificates (.pfx)** > **Add certificate**.
 
 1. Under **Source**, select **Import App Service Certificate**.
-1. Under **App Service certificate**, select the certificate you created.
+1. Under **App Service certificate**, select the certificate that you created.
 1. Under **Certificate friendly name**, give the certificate a name in your app.
 1. Select **Validate**. When validation succeeds, select **Add**.
 
