validation

Author: cephalin

articles/app-service/configure-language-java-data-sources.md

@@ -388,11 +388,11 @@ There are three core steps when [registering a data source with JBoss EAP](https
 
 App Service is a stateless hosting service, so you must put these steps into a startup script and run it each time the JBoss container starts. Using PostgreSQL and MySQL as an examples:
 
-# [PostgreSQL](#tab/jboss_postgresql)
+# [PostgreSQL](#tab/postgresql)
 
 [!INCLUDE [configure-jboss-postgresql](includes/configure-language-java-data-sources/configure-jboss-postgresql.md)]
 
-# [MySQL](#tab/jboss_mysql)
+# [MySQL](#tab/mysql)
 
 [!INCLUDE [configure-jboss-mysql](includes/configure-language-java-data-sources/configure-jboss-mysql.md)]
 

articles/app-service/configure-language-java-deploy-run.md

@@ -461,7 +461,7 @@ For more information about the CLI commands you can run, see the [Red Hat JBoss
 
 ## Clustering
 
-App Service supports clustering for JBoss EAP versions 7.4.1 and greater. To enable clustering, your web app must be [integrated with a virtual network](overview-vnet-integration.md). When the web app is integrated with a virtual network, it restarts, and the JBoss EAP installation automatically starts up with a clustered configuration. When you [run multiple instances with autoscaling](/azure-monitor/autoscale/autoscale-get-started), the JBoss EAP instances communicate with each other over the subnet specified in the virtual network integration, using the ports shown in the `WEBSITES_PRIVATE_PORTS` environment variable at runtime. You can disable clustering by creating an app setting named `WEBSITE_DISABLE_CLUSTERING` with any value.
+App Service supports clustering for JBoss EAP versions 7.4.1 and greater. To enable clustering, your web app must be [integrated with a virtual network](overview-vnet-integration.md). When the web app is integrated with a virtual network, it restarts, and the JBoss EAP installation automatically starts up with a clustered configuration. When you [run multiple instances with autoscaling](/azure/azure-monitor/autoscale/autoscale-get-started), the JBoss EAP instances communicate with each other over the subnet specified in the virtual network integration, using the ports shown in the `WEBSITES_PRIVATE_PORTS` environment variable at runtime. You can disable clustering by creating an app setting named `WEBSITE_DISABLE_CLUSTERING` with any value.
 
 :::image type="content" source="media/configure-language-java-deploy-run/jboss-clustering.png" alt-text="A diagram showing a vnet-integrated JBoss App Service app, scaled out to three instances.":::
 

articles/app-service/includes/configure-language-java-data-sources/configure-jboss-mysql.md

@@ -26,7 +26,7 @@ ms.author: cephalin
 
 1. Using a deployment option of your choice, upload your JDBC driver, *jboss-cli-commands.cli*, and *startup.sh* to the paths specified in the respective scripts. Especially, upload *startup.sh* as a startup file. For example:
 
-# [Azure CLI](#tab/cli)
+    # [Azure CLI](#tab/cli)
 
     ```azurecli-interactive
     export RESOURCE_GROUP_NAME=<resource-group-name>
@@ -39,9 +39,9 @@ ms.author: cephalin
     az webapp deploy --resource-group $RESOURCE_GROUP_NAME --name $APP_NAME --src-path startup.sh --type startup
     ```
 
-For more information, see [Deploy files to App Service](deploy-zip.md).
+    For more information, see [Deploy files to App Service](../../deploy-zip.md).
 
-# [Azure Maven Plugin](#tab/maven)
+    # [Azure Maven Plugin](#tab/maven)
 
     ```xml
     <deployment>
@@ -75,7 +75,7 @@ For more information, see [Deploy files to App Service](deploy-zip.md).
     </deployment>
     ```
 
----
+    ---
 
 To confirm that the datasource was added to the JBoss server, SSH into your webapp and run `$JBOSS_HOME/bin/jboss-cli.sh --connect`. Once you're connected to JBoss, run the `/subsystem=datasources:read-resource` to print a list of the data sources.
 

articles/app-service/includes/configure-language-java-data-sources/configure-jboss-postgresql.md

@@ -26,7 +26,7 @@ ms.author: cephalin
 
 1. Using a deployment option of your choice, upload your JDBC driver, *jboss-cli-commands.cli*, and *startup.sh* to the paths specified in the respective scripts. Especially, upload *startup.sh* as a startup file. For example:
 
-# [Azure CLI](#tab/cli)
+    # [Azure CLI](#tab/cli)
 
     ```azurecli-interactive
     export RESOURCE_GROUP_NAME=<resource-group-name>
@@ -39,9 +39,9 @@ ms.author: cephalin
     az webapp deploy --resource-group $RESOURCE_GROUP_NAME --name $APP_NAME --src-path startup.sh --type startup
     ```
 
-For more information, see [Deploy files to App Service](deploy-zip.md).
+    For more information, see [Deploy files to App Service](../../deploy-zip.md).
 
-# [Azure Maven Plugin](#tab/maven)
+    # [Azure Maven Plugin](#tab/maven)
 
     ```xml
     <deployment>
@@ -75,7 +75,7 @@ For more information, see [Deploy files to App Service](deploy-zip.md).
     </deployment>
     ```
 
----
+    ---
 
 To confirm that the datasource was added to the JBoss server, SSH into your webapp and run `$JBOSS_HOME/bin/jboss-cli.sh --connect`. Once you're connected to JBoss, run the `/subsystem=datasources:read-resource` to print a list of the data sources.