fix links

Author: v-thepet

docs/containers/tutorial-kubernetes-tools.md

@@ -36,7 +36,7 @@ To leverage this new functionality, you'll need:
         [Creating an AKS cluster](/azure/aks/kubernetes-walkthrough-portal#create-an-aks-cluster). Be sure to [connect to the cluster](/azure/aks/kubernetes-walkthrough#connect-to-the-cluster) from your development workstation.
 
     1. Helm CLI installed on your development workstation. For more information
-        see [Installing Helm](https://github.com/kubernetes/helm/blob/master/docs/install.md).
+        see [Installing Helm](https://github.com/helm/helm-www/blob/master/content/en/docs/helm/helm_install.md).
 
     1. Helm configured against your AKS cluster by using the `helm init` command. For more information on how to do this, see [How to configure Helm](/azure/aks/kubernetes-helm#configure-helm).
 ::: moniker-end

docs/deployment/how-to-check-for-application-updates-programmatically-using-the-clickonce-deployment-api.md

@@ -40,7 +40,7 @@ ClickOnce provides two ways to update an application once it is deployed. In the
 
 ### Use Mage.exe to deploy an application that checks for updates programmatically
 
-- Follow the instructions for deploying your application using Mage.exe as explained in [Walkthrough: Manually deploy a ClickOnce application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md). When calling Mage.exe to generate the deployment manifest, make sure to use the command-line switch `providerUrl`, and to specify the URL where ClickOnce should check for updates. If your application will update from [http://www.adatum.com/MyApp](http://www.adatum.com/MyApp), for example, your call to generate the deployment manifest might look like this:
+- Follow the instructions for deploying your application using Mage.exe as explained in [Walkthrough: Manually deploy a ClickOnce application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md). When calling Mage.exe to generate the deployment manifest, make sure to use the command-line switch `providerUrl`, and to specify the URL where ClickOnce should check for updates. If your application will update from `http://www.adatum.com/MyApp`, for example, your call to generate the deployment manifest might look like this:
 
     ```cmd
     mage -New Deployment -ToFile WindowsFormsApp1.application -Name "My App 1.0" -Version 1.0.0.0 -AppManifest 1.0.0.0\MyApp.manifest -providerUrl http://www.adatum.com/MyApp/MyApp.application

docs/extensibility/private-galleries.md

@@ -36,9 +36,9 @@ You can share the controls, templates, and tools that you develop by posting the
 
 5. In the **URL** field, enter the URL of the Atom feed or SharePoint site that is hosting the private gallery.
 
-    1. If the host is an Atom feed that connects to the private gallery, the URL would resemble this one: http://www.mywebsite/mygallery/atom.xml.  This URL can refer to a file or a network path.
+    1. If the host is an Atom feed that connects to the private gallery, the URL would resemble this one: `http://www.mywebsite/mygallery/atom.xml`.  This URL can refer to a file or a network path.
 
-    2. If the host is a SharePoint site, the URL would resemble this one: http://mysharepoint/sites/mygallery/forms/AllItems.aspx.
+    2. If the host is a SharePoint site, the URL would resemble this one: `http://mysharepoint/sites/mygallery/forms/AllItems.aspx`.
 
 ### Manage private galleries
  An administrator can make a private gallery available to several computers at the same time by modifying the system registry on each computer. To accomplish this, create a *.pkgdef* file that describes the new registry keys and their values.  The format of this file is as follows.

docs/extensibility/roslyn-analyzers-and-code-aware-library-for-immutablearrays.md

@@ -306,4 +306,4 @@ You can see all the finished code [here](https://github.com/DustinCampbell/CoreF
 * [Completed code on GitHub](https://github.com/DustinCampbell/CoreFxAnalyzers/tree/master/Source/CoreFxAnalyzers)
 * [Several examples on GitHub, grouped into three kinds of analyzers](https://github.com/dotnet/roslyn/blob/master/docs/analyzers/Analyzer%20Samples.md)
 * [Other docs on the GitHub OSS site](https://github.com/dotnet/roslyn/tree/master/docs/analyzers)
-* [FxCop rules implemented with Roslyn analyzers on GitHub](https://github.com/dotnet/roslyn/tree/master/src/Diagnostics/FxCop)
+* [FxCop rules implemented with Roslyn analyzers on GitHub](https://github.com/dotnet/roslyn/tree/master/src/Features/Core/Portable/Diagnostics/Analyzers)

docs/ide/quickstart-python.md

@@ -177,7 +177,7 @@ You're now ready to add a bit of Python code to implement a minimal web app.
 
 3. Select **Debug > Start Without Debugging** (**Ctrl**+**F5**), which saves changes to files and runs the app.
 
-4. A command window appears with the message "* Running in <https://localhost:4449/>", and a browser window should open to `localhost:4449` where you see the message, "Hello, Python!" The GET request also appears in the command window with a status of 200.
+4. A command window appears with the message **Running in https:\//localhost:4449**, and a browser window should open to `localhost:4449` where you see the message, "Hello, Python!" The GET request also appears in the command window with a status of 200.
 
     If a browser does not open automatically, start the browser of your choice and navigate to `localhost:4449`.
 

docs/javascript/publish-nodejs-app-azure.md

@@ -173,7 +173,7 @@ and it is accessible at the URL created for the Azure App Service (by default th
 * If the node.exe process dies (that is, an unhandled exception occurs), the container restarts.
 * When the container starts up, it runs through various heuristics to figure out
 how to start the Node.js process. Details of the implementation can be seen at
-[generateStartupCommand.js](https://github.com/Azure-App-Service/node/blob/master/8.9.4/startup/generateStartupCommand.js).
+[generateStartupCommand.js](https://github.com/Azure-App-Service/node/).
 * You can connect to the running container via SSH for investigations. This is easily done using the Azure portal. Select the App Service, and scroll down
 the list of tools until reaching **SSH** under the **Development Tools** section.
 * To aid in troubleshooting, go to the **Diagnostics logs** settings for the App Service, and change the **Docker Container logging** setting

docs/modeling/vs-shell-deployment.md

@@ -10,7 +10,7 @@ ms.workload:
 ---
 # VS Shell deployment
 
-An isolated shell lets you determine which Visual Studio functionality you need to interact with your domain-specific language and how that solution should appear. For more information about the Visual Studio isolated shell, see [Customizing the Isolated Shell](https://vspartner.com/pages/vsshells).
+An isolated shell lets you determine which Visual Studio functionality you need to interact with your domain-specific language and how that solution should appear. For more information about the Visual Studio isolated shell, see [Customizing the Isolated Shell](https://docs.microsoft.com/visualstudio/extensibility/customizing-the-isolated-shell).
 
 To set a Visual Studio Shell as the deployment target:
 

docs/sharepoint/deploying-publishing-and-upgrading-sharepoint-solution-packages.md

@@ -48,7 +48,7 @@ ms.workload:
  You can also add commands to run before and after deployment. For more information, see [How to: Set SharePoint deployment commands](../sharepoint/how-to-set-sharepoint-deployment-commands.md).
 
 ## Publish packages to a remote or local server
- To publish a sandboxed SharePoint solution to a remote server, on the menu bar, choose **Build**, **Publish**, and then, in the **Publish** dialog box, choose the **Publish to SharePoint Site** option button, providing the remote server's URL, such as **https://someremoteserver.sharepoint.microsoftonline.com**.
+ To publish a sandboxed SharePoint solution to a remote server, on the menu bar, choose **Build**, **Publish**, and then, in the **Publish** dialog box, choose the **Publish to SharePoint Site** option button, providing the remote server's URL, such as `https://someremoteserver.sharepoint.microsoftonline.com`.
 
  To publish a SharePoint solution to a local server, in the **Publish** dialog box, choose the **Publish to File System** option button, providing a local system path.
 

docs/test/editing-coded-ui-tests-using-the-coded-ui-test-editor.md

@@ -68,7 +68,7 @@ Using the Coded UI Test Editor, you can quickly locate and view all the UI actio
 
 To modify the properties for a UI action, in the **UI Action** pane, expand the test method that contains a UI action that you want to edit the properties for, select the UI action, and then modify the properties using the Properties window.
 
-For example, if a server is unavailable, and you have a UI action associated with your web browser that states **Go to Web page '<http://Contoso1/default.aspx>'**, you could change the URL to `'http://Contoso2/default.aspx'`.
+For example, if a server is unavailable, and you have a UI action associated with your web browser that states **Go to Web page http:\//Contoso1/default.aspx**, you could change the URL to `http://Contoso2/default.aspx`.
 
 ![Control properties](../test/media/codeduitestcontrolprop.png)
 

docs/vs-2015/debugger/debug-xaml-in-blend.md

@@ -108,7 +108,7 @@ You can use the tools in [!INCLUDE[blend_first](../includes/blend-first-md.md)]
   
 4. Double-click "The member 'content' is not recognized or is not accessible." The `c` in `content` should be upper-case. Replace the lower-case "c" with an upper-case "c."  
   
-5. Double-click "The property 'Mame' does not exist in the '<https://schemas.microsoft.com/winfx/2006/xaml>' namespace." The "M" in "Mame" should be an "N." Replace the "M" with an "N." Now that the XAML can be parsed, the app appears on the design surface.  
+5. Double-click "The property 'Mame' does not exist in the `https://schemas.microsoft.com/winfx/2006/xaml` namespace." The "M" in "Mame" should be an "N." Replace the "M" with an "N." Now that the XAML can be parsed, the app appears on the design surface.  
   
     ![Debugging XAML in Blend for Visual Studio](../debugger/media/blend-debugartboard-xaml.png "blend_debugArtboard_XAML")  
   

docs/vs-2015/deployment/how-to-check-for-application-updates-programmatically-using-the-clickonce-deployment-api.md

@@ -43,7 +43,7 @@ ClickOnce provides two ways to update an application once it is deployed. In the
 
 ### Using Mage.exe to deploy an application that checks for updates programmatically  
 
-- Follow the instructions for deploying your application using Mage.exe as explained in [Walkthrough: Manually Deploying a ClickOnce Application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md). When calling Mage.exe to generate the deployment manifest, make sure to use the command-line switch `providerUrl`, and to specify the URL where ClickOnce should check for updates. If your application will update from [http://www.adatum.com/MyApp](http://www.adatum.com/MyApp), for example, your call to generate the deployment manifest might look like this:  
+- Follow the instructions for deploying your application using Mage.exe as explained in [Walkthrough: Manually Deploying a ClickOnce Application](../deployment/walkthrough-manually-deploying-a-clickonce-application.md). When calling Mage.exe to generate the deployment manifest, make sure to use the command-line switch `providerUrl`, and to specify the URL where ClickOnce should check for updates. If your application will update from `http://www.adatum.com/MyApp`, for example, your call to generate the deployment manifest might look like this:  
 
     ```  
     mage -New Deployment -ToFile WindowsFormsApp1.application -Name "My App 1.0" -Version 1.0.0.0 -AppManifest 1.0.0.0\MyApp.manifest -providerUrl http://www.adatum.com/MyApp/MyApp.application  

docs/vs-2015/extensibility/getting-started-with-roslyn-analyzers.md

@@ -30,4 +30,4 @@ With live, project-based code analyzers in Visual Studio, API authors can ship d
 ## Other Resources
 [More docs on the GitHub OSS site](https://github.com/dotnet/roslyn/tree/master/docs/analyzers)
 
-[FxCop rules implemented with Roslyn analyzers on GitHub](https://github.com/dotnet/roslyn/tree/master/src/Diagnostics/FxCop)
+[FxCop rules implemented with Roslyn analyzers on GitHub](https://github.com/dotnet/roslyn/tree/master/src/Features/Core/Portable/Diagnostics/Analyzers)

docs/vs-2015/extensibility/private-galleries.md

@@ -38,9 +38,9 @@ You can share the controls, templates, and tools that you develop by posting the
 
 5. In the **URL** field, enter the URL of the Atom feed or SharePoint site that is hosting the private gallery.  
 
-    1. If the host is an Atom feed that connects to the private gallery, the URL would resemble this one: http://www.mywebsite/mygallery/atom.xml.  This URL can refer to a file or a network path.  
+    1. If the host is an Atom feed that connects to the private gallery, the URL would resemble this one: `http://www.mywebsite/mygallery/atom.xml`.  This URL can refer to a file or a network path.  
 
-    2. If the host is a SharePoint site, the URL would resemble this one: http://mysharepoint/sites/mygallery/forms/AllItems.aspx.  
+    2. If the host is a SharePoint site, the URL would resemble this one: `http://mysharepoint/sites/mygallery/forms/AllItems.aspx`.  
 
 ### Managing Private Galleries  
  An administrator can make a private gallery available to several computers at the same time by modifying the system registry on each computer. To accomplish this, create a .pkgdef file that describes the new registry keys and their values.  The format of this file is as follows.  

docs/vs-2015/extensibility/roslyn-analyzers-and-code-aware-library-for-immutablearrays.md

@@ -308,4 +308,4 @@ You can see all the finished code [here](https://github.com/DustinCampbell/CoreF
 [Completed code on GitHub](https://github.com/DustinCampbell/CoreFxAnalyzers/tree/master/Source/CoreFxAnalyzers) 
 [Several examples on GitHub, grouped into three kinds of analyzers](https://github.com/dotnet/roslyn/blob/master/docs/analyzers/Analyzer%20Samples.md) 
 [Other docs on the GitHub OSS site](https://github.com/dotnet/roslyn/tree/master/docs/analyzers) 
-[FxCop rules implemented with Roslyn analyzers on GitHub](https://github.com/dotnet/roslyn/tree/master/src/Diagnostics/FxCop)
+[FxCop rules implemented with Roslyn analyzers on GitHub](https://github.com/dotnet/roslyn/tree/master/src/Features/Core/Portable/Diagnostics/Analyzers)

docs/vs-2015/install/create-an-offline-installation-of-visual-studio.md

@@ -56,7 +56,7 @@ This page describes how to install Visual Studio 2015 when you are not connected
 | Component or Package | Solution |
 |-|-|
 | Dotfuscator and Analytics Community Edition 5.19.1 (for the Community, Professional, and Enterprise editions of Visual Studio, as installed on **Windows 7 SP1** and **Windows Server 2008 R2**) | If your offline machine is running **Windows 7 SP1** or **Windows Server 2008 R2**, you must perform the following steps before you install Visual Studio 2015:<br /><br /> 1.  Configure a file or web server to download the CTL files.<br /><br /> 2.    Redirect the Microsoft Automatic Update URL for a disconnected environment.<br /><br /> For more information, see the [Configure Trusted Roots and Disallowed Certificates](https://technet.microsoft.com/library/dn265983.aspx) page on the Microsoft TechNet site. |
-| Android SDK Setup (API Level) | You must have an internet connection to install Android SDK (API Level) packages. If you are on a restricted network, you must allow access to the following URLs when you install Visual Studio:<br /><br /> -   https://dl.google.com:443<br />-   https://dl-ssl.google.com:443<br />-   https://dl-ssl.google.com/android/repository/*<br /> <br />For more information about how to resolve possible issues with proxy settings, see the [Visual Studio 2015 install failures (Android SDK Setup) behind a Proxy](https://blogs.msdn.microsoft.com/peterhauge/2016/09/22/visual-studio-2015-install-failures-android-sdk-setup-behind-a-proxy/) blog post. |
+| Android SDK Setup (API Level) | You must have an internet connection to install Android SDK (API Level) packages. If you are on a restricted network, you must allow access to the following URLs when you install Visual Studio:<br /><br /> -   `https://dl.google.com:443`<br />-   `https://dl-ssl.google.com:443`<br />-   `https://dl-ssl.google.com/android/repository/*`<br /> <br />For more information about how to resolve possible issues with proxy settings, see the [Visual Studio 2015 install failures (Android SDK Setup) behind a Proxy](https://blogs.msdn.microsoft.com/peterhauge/2016/09/22/visual-studio-2015-install-failures-android-sdk-setup-behind-a-proxy/) blog post. |
 | Visual Studio Extensibility Item Templates<br /><br /> GitHub Extension for Visual Studio<br /><br /> PowerShell Tools for Visual Studio | If you do not have an internet connection when you install Visual Studio 2015, you can use a special offline feed to generate the offline installation layout. **Note:**  This special feed includes the most recent Updates to Visual Studio 2015. <br /><br /> To create the special offline feed, run the following command: /layout *Drive:*\VisualStudio2015 /overridefeeduri *URL-to-feed-xml*<br /><br /> For example, for an English-language special offline feed of Visual Studio 2015 Enterprise, run:<br /><br /> `vs_enterprise_ENU.exe /layout D:\VisualStudio2015 /overridefeeduri "https://go.microsoft.com/fwlink/?LinkID=785882&clcid0x409"`<br /><br /> For a complete list of URLs that you can use to create a special offline feed in the language of your choice, see the table below. |
 
  Use the following URLs to create a language-specific special offline feed, as described in the table above.

docs/vs-2015/msbuild/additional-msbuild-resources.md

@@ -606,7 +606,7 @@ manager: jillfra
 If you are trying to solve a problem and cannot find the information you need in the documentation, you can consult other resources such as Knowledge Base articles, the developer community, or product support.  
 
 ## Knowledge Base Articles  
- You can search the Knowledge Base (KB) online for articles about product issues. Not all issues have a corresponding KB article, but errors encountered by a significant number of customers are typically documented. You can access KB articles on the [Knowledge Base (MSBuild search results)](https://search.microsoft.com/supportresults.aspx?q=knowledge+base+MSBuild&x=0&y=0) Web site.  
+ You can search the Knowledge Base (KB) online for articles about product issues. Not all issues have a corresponding KB article, but errors encountered by a significant number of customers are typically documented. You can access KB articles on the [Knowledge Base](https://support.microsoft.com/help/242450/how-to-query-the-microsoft-knowledge-base-by-using-keywords-and-query) Web site.  
 
 ## Community Forums  
  Forums let you interact with other developers, and also Microsoft employees. If you encounter an error that you cannot find a resolution for, you can post questions about the issue on a forum. You can also search the newsgroups to see whether others have posted about the same issue. You can access the Visual Studio MSBuild forum on the [MSDN Forums](https://social.msdn.microsoft.com/forums/en-US/msbuild/threads/) Web site.