On branch edburns-msft-em-4042-move-wls-aks-quickstart-to-aks-area Apply suggestions from @JamesJBarnett

modified:   howto-deploy-java-wls-app.md
renamed:    media/howto-deploy-java-wls-app/testwebapp.png -> media/howto-deploy-java-wls-app/test-web-app.png

@JamesJBarnett  wrote:

> articles/aks/howto-deploy-java-wls-app.md

> File name: spell out "wls" in lowercase with hyphens for spaces and add hyphen: "how-to"

I am pushing back on this one.  WLS is well known to the intended audience. As proof, I ask you to bing or google the keywords "java wls". You will see unambiguous results that WLS is WebLogic Server. As another proof, we do not spell out Structured Query Language.

> articles/aks/media/howto-deploy-java-wls-app/testwebapp.png
> File name: Add hyphens: "test-web-app.png"

Yes. Will comply.

> articles/aks/media/howto-deploy-java-wls-app/wls-admin-login.png
> File name: spell out "wls" in lowercase with hyphens for spaces.

I am pushing back on this one for the same reason.

Signed-off-by: Ed Burns <[email protected]>

Author: edburns

articles/aks/howto-deploy-java-wls-app.md

@@ -122,7 +122,7 @@ The following steps show you how to verify the functionality of the deployment b
 1. Construct a fully qualified URL for the sample app by appending the `context-path` to the value of **clusterExternalUrl**. If you deployed the recommended sample app, the fully qualified URL will be something like `http://123.456.789.012:8001/testwebapp/`.
 1. Paste the fully qualified URL in an Internet-connected web browser. If you deployed the recommended sample app, you should see results similar to the following screenshot.
 
-   :::image type="content" source="media/howto-deploy-java-wls-app/testwebapp.png" alt-text="Screenshot of test web app." border="false":::
+   :::image type="content" source="media/howto-deploy-java-wls-app/test-web-app.png" alt-text="Screenshot of test web app." border="false":::
 
 ## Clean up resources