Work in progress.

Author: TimShererWithAquent

articles/app-service/includes/quickstart-java/quickstart-java-jboss.md

@@ -120,7 +120,7 @@ With all the configuration ready in your *pom.xml* file, you can deploy your Jav
 mvn package azure-webapp:deploy -DskipTests
 ```
 
-Once you select from a list of available subscriptions, Maven deploys to Azure App Service. When deployment completes, your application is ready at `http://<appName>.azurewebsites.net/` (`http://petstoreee7-1745409173307.azurewebsites.net` in the demo). Open the URL with your local web browser, you should see
+Once you select from a list of available subscriptions, Maven deploys to Azure App Service. When deployment completes, your application is ready. In this demo, the URL is `http://petstoreee7-1745409173307.azurewebsites.net`. Open the URL with your local web browser, you should see
 
 ![Screenshot of Maven Hello World web app running in Azure App Service.](../../media/quickstart-java/jboss-sample-in-app-service.png)
 

articles/app-service/includes/quickstart-java/quickstart-java-linux-maven-pivot.md

@@ -266,7 +266,7 @@ mvn package azure-webapp:deploy -DskipTests
 
 -----
 
-Once deployment is completed, your application is ready at `http://<appName>.azurewebsites.net/` (`http://helloworld-1590394316693.azurewebsites.net` in the demo). Open the url with your local web browser, you should see
+Once deployment is completed, your application is ready. at `http://<appName>.azurewebsites.net/` (`http://helloworld-1590394316693.azurewebsites.net` in the demo). Open the url with your local web browser, you should see
 
 # [Java SE](#tab/javase)
 

articles/app-service/includes/quickstart-java/quickstart-java-tomcat.md

@@ -110,7 +110,7 @@ With all the configuration ready in your *pom.xml* file, you can deploy your Jav
 ```azurecli-interactive
 mvn package azure-webapp:deploy
 ```
-Once you select from a list of available subscriptions, Maven deploys to Azure App Service. When deployment completes, your application is ready at `http://<appName>.azurewebsites.net/` (`http://helloworld-1745408005556.azurewebsites.net` in the demo). Open the URL with your local web browser, you should see
+Once you select from a list of available subscriptions, Maven deploys to Azure App Service. When deployment completes, your application is ready. In this demo, the URL is `http://helloworld-1745408005556.azurewebsites.net`. Open the URL with your local web browser, you should see
 
 ![Screenshot of Maven Hello World web app running in Azure App Service.](../../media/quickstart-java/java-hello-world-in-browser-azure-app-service.png)
 

articles/app-service/includes/quickstart-php/quickstart-php-windows-pivot.md

@@ -95,14 +95,10 @@ To complete this quickstart:
     You've created an empty new web app, with git deployment enabled.
 
     > [!NOTE]
-    > The URL of the Git remote is shown in the `deploymentLocalGitUrl` property, with the format `https://<username>@<app-name>.scm.azurewebsites.net/<app-name>.git`. Save this URL as you need it later.
+    > The URL of the Git remote is shown in the `deploymentLocalGitUrl` property. Save this URL as you need it later.
     >
 
-1. Browse to your newly created web app. Replace _&lt;app-name>_ with your unique app name created in the prior step.
-
-    ```bash
-    http://<app-name>.azurewebsites.net
-    ```
+1. Browse to your newly created web app. 
 
     Here's what your new web app should look like:
 
@@ -139,10 +135,6 @@ To complete this quickstart:
 
 Browse to the deployed application using your web browser.
 
-```
-http://<app-name>.azurewebsites.net
-```
-
 The PHP sample code is running in an Azure App Service web app.
 
 ![Sample app running in Azure](../../media/quickstart-php/hello-world-in-browser.png)

articles/app-service/tutorial-connect-app-access-sql-database-as-user-dotnet.md

@@ -273,7 +273,7 @@ The most common causes of this error are:
 Because App Service authentication is a feature in Azure, it's not possible for the same code to work in your local environment. Unlike the app running in Azure, your local code doesn't benefit from the authentication middleware from App Service. You have a few alternatives:
 
 - Connect to SQL Database from your local environment with [`Active Directory Interactive`](/sql/connect/ado-net/sql/azure-active-directory-authentication#using-active-directory-interactive-authentication). The authentication flow doesn't sign in the user to the app itself, but it does connect to the back-end database with the signed-in user, and allows you to test database authorization locally.
-- Manually copy the access token from `https://<app-name>.azurewebsites.net/.auth/me` into your code, in place of the `X-MS-TOKEN-AAD-ACCESS-TOKEN` request header.
+- Manually copy the access token into your code, in place of the `X-MS-TOKEN-AAD-ACCESS-TOKEN` request header.
 - If you deploy from Visual Studio, use remote debugging of your App Service app.
 
 #### What happens when access tokens expire?

articles/app-service/tutorial-connect-app-app-graph-javascript.md

@@ -269,7 +269,7 @@ Now that the code has the correct token for Microsoft Graph, use it to create a
 
 ## 6. Test your changes
 
-1. Use the frontend web site in a browser. The URL is in the format of `https://<front-end-app-name>.azurewebsites.net/`. You may need to refresh your token if it's expired.
+1. Use the frontend web site in a browser. You may need to refresh your token if it's expired.
 1. Select `Get user's profile`. This passes your authentication in the bearer token to the backend. 
 1. The backend end responds with the _real_ Microsoft Graph profile for your account.
 

articles/app-service/tutorial-dotnetcore-sqldb-app.md

@@ -118,7 +118,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
 
 In this step, you create the Azure resources. The steps used in this tutorial create a set of secure-by-default resources that include App Service, Azure SQL Database, and Azure Cache. For the creation process, you'll specify:
 
-* The **Name** for the web app. It's used as part of the DNS name for your app in the form of `https://<app-name>-<hash>.<region>.azurewebsites.net`.
+* The **Name** for the web app. It's used as part of the DNS name for your app.
 * The **Region** to run the app physically in the world. It's also used as part of the DNS name for your app.
 * The **Runtime stack** for the app. It's where you select the .NET version to use for your app.
 * The **Hosting plan** for the app. It's the pricing tier that includes the set of features and scaling capacity for your app.

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

@@ -116,7 +116,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
 
 First, you create the Azure resources. The steps used in this tutorial create a set of secure-by-default resources that include App Service and Azure Database for MySQL. For the creation process, you specify:
 
-* The **Name** for the web app. It's used as part of the DNS name for your app in the form of `https://<app-name>-<hash>.<region>.azurewebsites.net`.
+* The **Name** for the web app. It's used as part of the DNS name for your app.
 * The **Region** to run the app physically in the world. It's also used as part of the DNS name for your app.
 * The **Runtime stack** for the app. It's where you select the version of Java to use for your app.
 * The **Hosting plan** for the app. It's the pricing tier that includes the set of features and scaling capacity for your app.

articles/app-service/tutorial-java-spring-cosmosdb.md

@@ -117,7 +117,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
 
 First, you create the Azure resources. The steps used in this tutorial create a set of secure-by-default resources that include App Service and Azure Cosmos DB. For the creation process, you specify:
 
-* The **Name** for the web app. It's used as part of the DNS name for your app in the form of `https://<app-name>-<hash>.<region>.azurewebsites.net`.
+* The **Name** for the web app. It's used as part of the DNS name for your app.
 * The **Region** to run the app physically in the world. It's also used as part of the DNS name for your app.
 * The **Runtime stack** for the app. It's where you select the version of Java to use for your app.
 * The **Hosting plan** for the app. It's the pricing tier that includes the set of features and scaling capacity for your app.

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

@@ -115,7 +115,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
 
 First, you create the Azure resources. The steps used in this tutorial create a set of secure-by-default resources that include App Service and Azure Database for MySQL. For the creation process, you specify:
 
-* The **Name** for the web app. It's used as part of the DNS name for your app in the form of `https://<app-name>-<hash>.<region>.azurewebsites.net`.
+* The **Name** for the web app. It's used as part of the DNS name.
 * The **Region** to run the app physically in the world. It's also used as part of the DNS name for your app.
 * The **Runtime stack** for the app. It's where you select the version of Java to use for your app.
 * The **Hosting plan** for the app. It's the pricing tier that includes the set of features and scaling capacity for your app.