Fix typos and formatting in documentation.

LHL407 · web-flow · commit 1080db18d8db · 2025-04-01T09:47:31.000-06:00
diff --git a/articles/app-service/app-service-undelete.md b/articles/app-service/app-service-undelete.md
@@ -52,13 +52,13 @@ Get-AzDeletedWebApp -Name <your_deleted_app> -Location <your_deleted_app_locatio
 
 The detailed information includes:
 
-* **`DeletedSiteId`**: Unique identifier for the app, used for scenarios where multiple apps with the same name were deleted
-* **`SubscriptionID`**: Subscription containing the deleted resource
-* **Location**: Location of the original app
-* **`ResourceGroupName`**: Name of the original resource group
-* **Name**: Name of the original app
-* **Slot**: Name of the slot
-* **Deletion Time**: When the app was deleted
+* **DeletedSiteId**: Unique identifier for the app, used for scenarios where multiple apps with the same name were deleted.
+* **SubscriptionID**: Subscription that contains the deleted resource.
+* **Location**: Location of the original app.
+* **ResourceGroupName**: Name of the original resource group.
+* **Name**: Name of the original app.
+* **Slot**: Name of the slot.
+* **Deletion Time**: When the app was deleted.
 
 ## Restore deleted app
 
@@ -69,7 +69,7 @@ The detailed information includes:
 >* By default `Restore-AzDeletedWebApp` restores both your app configuration and any content. If you want to only restore content, you use the `-RestoreContentOnly` flag with this cmdlet.
 >* Custom domains, bindings, or certs that you import to your app aren't restored. You need to add them again after your app is restored.
 
-After identifying the app you want to restore, you can restore it by using `Restore-AzDeletedWebApp`, as shown in the following examples.
+After you identify the app you want to restore, you can restore it by using `Restore-AzDeletedWebApp`, as shown in the following examples.
 
 You can find the full cmdlet reference here: [`Restore-AzDeletedWebApp`](/powershell/module/az.websites/restore-azdeletedwebapp).
 
@@ -111,20 +111,20 @@ Restore-AzDeletedWebApp -ResourceGroupName <original_rg> -Name <original_app> -D
 
 The inputs for command are:
 
-- **`Target Resource Group`**: Target resource group to which you're restoring the app.
-- **`TargetName`**: Target app to which you're restoring the deleted app.
-- **`TargetAppServicePlanName`**: App Service plan linked to the app.
+- **Target Resource Group**: Target resource group to which you're restoring the app.
+- **TargetName**: Target app to which you're restoring the deleted app.
+- **TargetAppServicePlanName**: App Service plan linked to the app.
 - **Name**: Name for the app. We recommend that it's globally unique.
-- **`ResourceGroupName`**: Original resource group for the deleted app. You can get it from `Get-AzDeletedWebApp -Name <your_deleted_app> -Location <your_deleted_app_location>`.
+- **ResourceGroupName**: Original resource group for the deleted app. You can get it from `Get-AzDeletedWebApp -Name <your_deleted_app> -Location <your_deleted_app_location>`.
 - **Slot**: Slot for the deleted app.
-- **`RestoreContentOnly`**: By default `Restore-AzDeletedWebApp` restores both your app configuration as well any content. If you want to only restore content, you can use the `-RestoreContentOnly` flag with this cmdlet.
+- **RestoreContentOnly**: By default `Restore-AzDeletedWebApp` restores both your app configuration as well any content. If you want to only restore content, you can use the `-RestoreContentOnly` flag with this cmdlet.
 
 > [!NOTE]
 > If the app was hosted on and then deleted from an App Service Environment, it can be restored only if the corresponding App Service Environment still exists.
 
 ## Restore deleted Azure Functions app
 
-If a function app was hosted on a **Dedicated app service plan**, it can be restored, as long as it used the default App Service storage.
+If a function app was hosted on a Dedicated App Service plan, it can be restored, as long as it used the default App Service storage.
 
 1. Fetch the `DeletedSiteId` of the app version you want to restore, by using the `Get-AzDeletedWebApp` cmdlet:
 
diff --git a/articles/app-service/app-service-web-app-cloning.md b/articles/app-service/app-service-web-app-cloning.md
@@ -66,7 +66,7 @@ With the App Service Environment's name, and the name of the resource group that
 $destapp = New-AzWebApp -ResourceGroupName DestinationAzureResourceGroup -Name dest-webapp -Location "North Central US" -AppServicePlan DestinationAppServicePlan -ASEName DestinationASE -ASEResourceGroupName DestinationASEResourceGroupName -SourceWebApp $srcapp
 ```
 
-The `Location` parameter is required for legacy reasons, but ignored when you create the app in an App Service Environment.
+The `Location` parameter is required for legacy reasons, but it's ignored when you create the app in an App Service Environment.
 
 ## Clone an existing app slot
 
@@ -116,18 +116,18 @@ $destapp = New-AzWebApp -ResourceGroupName <Resource group name> -Name dest-weba
 
 Here are the known restrictions of app cloning:
 
-* Autoscale settings aren't cloned
-* Backup schedule settings aren't cloned
-* Virtual network settings aren't cloned
-* Application Insights isn't automatically set up on the destination app
-* Easy Auth settings aren't cloned
-* Kudu extensions aren't cloned
-* TiP rules aren't cloned
-* Database content isn't cloned
-* Outbound IP addresses change if you clone to a different scale unit
-* Linux apps: not available
-* Managed identities aren't cloned
-* Function apps: not available
+* Autoscale settings aren't cloned.
+* Backup schedule settings aren't cloned.
+* Virtual network settings aren't cloned.
+* Application Insights isn't automatically set up on the destination app.
+* Easy Auth settings aren't cloned.
+* Kudu extensions aren't cloned.
+* TiP rules aren't cloned.
+* Database content isn't cloned.
+* Outbound IP addresses change if you clone to a different scale unit.
+* Linux apps: not available.
+* Managed identities aren't cloned.
+* Function apps: not available.
 
 ## Related content
 
diff --git a/articles/app-service/configure-language-java-deploy-run.md b/articles/app-service/configure-language-java-deploy-run.md
@@ -66,7 +66,7 @@ find / -name "version.sh"
 
 ::: zone pivot="java-jboss"
 
-To view the JBoss Enterprise Application Platform (EAP) server version in the SSH session:
+To view the JBoss EAP server version in the SSH session:
 ```bash
 $JBOSS_HOME/bin/jboss-cli.sh --connect --commands=:product-info
 ```
@@ -103,7 +103,7 @@ By using the [Maven Plugin for Azure Web Apps](https://github.com/microsoft/azur
 mvn com.microsoft.azure:azure-webapp-maven-plugin:2.13.0:config
 ```
 
-This command adds an `azure-webapp-maven-plugin` plugin and the related configuration by prompting you to select an existing Azure Web App or to create a new one. During configuration, it attempts to detect whether your application should be deployed to Java Standard Edition (SE), Tomcat, or (Linux only) JBoss Enterprise Application Platform (EAP). Then you can deploy your Java app to Azure by using the following command:
+This command adds an `azure-webapp-maven-plugin` plugin and the related configuration by prompting you to select an existing Azure Web App or to create a new one. During configuration, it attempts to detect whether your application should be deployed to Java SE, Tomcat, or (Linux only) JBoss Enterprise Application Platform (EAP). Then you can deploy your Java app to Azure by using the following command:
 
 ```shell
 mvn package azure-webapp:deploy
@@ -324,7 +324,7 @@ Use [FTPS](deploy-ftp.md) to download your JFR file to your local machine. To an
 
 # [Linux](#tab/linux)
 
-To configure App Service to write your application's standard console output and standard console error streams to the local filesystem or Azure Blob Storage, do the following. Enable [application logging](troubleshoot-diagnostic-logs.md#enable-application-logging-linuxcontainer) through the Azure portal or in the [Azure CLI](/cli/azure/webapp/log#az-webapp-log-config). If you need longer retention, configure the application to write output to a Blob storage container.
+To configure App Service to write your application's standard console output and standard console error streams to the local file system or Azure Blob Storage, do the following. Enable [application logging](troubleshoot-diagnostic-logs.md#enable-application-logging-linuxcontainer) through the Azure portal or in the [Azure CLI](/cli/azure/webapp/log#az-webapp-log-config). If you need longer retention, configure the application to write output to a Blob storage container.
 
 ::: zone pivot="java-javase,java-tomcat"
 
@@ -336,7 +336,7 @@ Azure Blob Storage logging for Linux-based apps can be configured only by using
 
 # [Windows](#tab/windows)
 
-To configure App Service to write your application's standard console output and standard console error streams to the local filesystem or Azure Blob Storage, do the following. Enable [application logging](troubleshoot-diagnostic-logs.md#enable-application-logging-windows) through the Azure portal or in the [Azure CLI](/cli/azure/webapp/log#az-webapp-log-config). Twelve hours after you enable application logging, logging to the local App Service filesystem instance is disabled. If you need longer retention, configure the application to write output to a Blob storage container.
+To configure App Service to write your application's standard console output and standard console error streams to the local file system or Azure Blob Storage, do the following. Enable [application logging](troubleshoot-diagnostic-logs.md#enable-application-logging-windows) through the Azure portal or in the [Azure CLI](/cli/azure/webapp/log#az-webapp-log-config). Twelve hours after you enable application logging, logging to the local App Service file system instance is disabled. If you need longer retention, configure the application to write output to a Blob storage container.
 
 ::: zone pivot="java-javase,java-tomcat"
 
diff --git a/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md b/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md
@@ -19,7 +19,7 @@ You can create intelligent apps by using Azure App Service with popular AI frame
 
 For this Blazor web application, we're building off the Blazor [template](https://dotnet.microsoft.com/learn/aspnet/blazor-tutorial/intro) to create a new razor page that can send and receive requests to an Azure OpenAI or OpenAI service by using Semantic Kernel.
 
-1. Right click on the **Pages** folder found under the **Components** folder and add a new item named `OpenAI.razor`.
+1. Right-click on the **Pages** folder found under the **Components** folder and add a new item named `OpenAI.razor`.
 1. Add the following code to the `OpenAI.razor` file and select **Save**.
 
 ```csharp
diff --git a/articles/app-service/troubleshoot-domain-ssl-certificates.md b/articles/app-service/troubleshoot-domain-ssl-certificates.md
@@ -104,10 +104,10 @@ The App Service certificate was renewed, but the app that uses the App Service c
 The key vault used to store the App Service certificate is missing access policy permissions on the key vault for `Microsoft.Azure.Websites` and `Microsoft.Azure.CertificateRegistration`. The service principals and their required permissions for key vault access are:
 </br></br>
 
-  |Service Principal|Secret Permissions|Certificate Permissions|
+  |Service principal|Secret permissions|Certificate permissions|
   |------|------|-----|
   |Microsoft Azure App Service|Get|Get|
-  |Microsoft Azure CertificateRegistration|Get, List, Delete|Get, List|
+  |Microsoft.Azure.CertificateRegistration|Get, List, Delete|Get, List|
 
 #### Solution 1: Modify the access policies for the key vault
 
