Next round of updates for 7861

Author: ryanberg-aquent

…best-practices-and-troubleshoot-guide.md …ejs-best-practices-troubleshoot-guide.mdsupport/azure/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md renamed to support/azure/app-service/app-service-web-nodejs-best-practices-troubleshoot-guide.md support/azure/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md renamed to support/azure/app-service/app-service-web-nodejs-best-practices-troubleshoot-guide.md

@@ -165,7 +165,7 @@ To go to the Debug Console site for your app, select **Development Tools** > **A
 
 Go into your site/wwwroot directory. You see a command prompt as shown in the following example:
 
-![Screenshot that shows your site/wwwroot directory and command prompt.](./media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/scm_install_v8.png)
+![Screenshot that shows your site/wwwroot directory and command prompt.](./media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/scm-install-v8.png)
 
 Run the command `npm install v8-profiler`.
 
@@ -198,11 +198,11 @@ http.createServer(function (req, res) {
 
 The preceding code profiles the WriteConsoleLog function and then writes the profile output to the ‘profile.cpuprofile’ file under your site wwwroot. Send a request to your application. You see a ‘profile.cpuprofile’ file created under your site wwwroot.
 
-![Screenshot that shows the profile.cpuprofile file.](./media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/scm_profile.cpuprofile.png)
+![Screenshot that shows the profile.cpuprofile file.](./media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/scm-profile.cpuprofile.png)
 
 Download this file and open it with Chrome F12 Tools. Press F12 on Chrome, then choose the **Profiles** tab. Choose the **Load** button. Select your profile.cpuprofile file that you downloaded. Click on the profile you just loaded.
 
-![Screenshot that shows the profile.cpuprofile file that you loaded.](./media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/chrome_tools_view.png)
+![Screenshot that shows the profile.cpuprofile file that you loaded.](./media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/chrome-tools-view.png)
 
 You can see that 95% of the time was consumed by the WriteConsoleLog function. The output also shows you the exact line numbers and source files that caused the issue.
 

…troubleshoot-guide/chrome_tools_view.png …troubleshoot-guide/chrome-tools-view.pngsupport/azure/app-service/media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/chrome_tools_view.png renamed to support/azure/app-service/media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/chrome-tools-view.png support/azure/app-service/media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/chrome_tools_view.png renamed to support/azure/app-service/media/app-service-web-nodejs-best-practices-and-troubleshoot-guide/chrome-tools-view.png

@@ -11,7 +11,7 @@
   - name: Troubleshoot Azure App Service
     href: ./welcome-app-service.yml
   - name: Node.js Best Practices and Troubleshooting Guide
-    href: app-service-web-nodejs-best-practices-and-troubleshoot-guide.md
+    href: app-service-web-nodejs-best-practices-troubleshoot-guide.md
   - name: Capture memory dumps in Azure App Service
     href: ./capture-memory-dumps-app-service.md
   - name: Create or delete web apps FAQs