Merge pull request #4771 from craigcaseyMSFT/vcraic0603

fixes for broken link report

Author: PRMerger19

docs/install/update-servicing-baseline.md

@@ -16,9 +16,9 @@ ms.technology: vs-installation
 ---
 # Update Visual Studio while on a servicing baseline
 
-Visual Studio 2019 will have frequent updates during its [product lifecycle](/visualstudio/productinfo/release-rhythm.md#release-channel-updates). These will include both minor release updates (for example: 16.0 to 16.1) that can include new features and components, and servicing updates (for example: 16.0.4 to 16.0.5) containing only targeted fixes for critical issues. 
+Visual Studio 2019 will have frequent updates during its [product lifecycle](/visualstudio/productinfo/release-rhythm#release-channel-updates). These will include both minor release updates (for example: 16.0 to 16.1) that can include new features and components, and servicing updates (for example: 16.0.4 to 16.0.5) containing only targeted fixes for critical issues. 
 
-Enterprise administrators can choose to keep their clients on a servicing baseline, which is supported with servicing updates for a year past the release of the next servicing baseline. This allows more flexibility for developers and administrators to adopt the new features, bug fixes, or components included in new minor updates. The first servicing baseline is 16.0.x. See [Support options for enterprise and professional customers](/visualstudio/releases/2019/servicing.md#support-options-for-enterprise-and-professional-customers) for more information.
+Enterprise administrators can choose to keep their clients on a servicing baseline, which is supported with servicing updates for a year past the release of the next servicing baseline. This allows more flexibility for developers and administrators to adopt the new features, bug fixes, or components included in new minor updates. The first servicing baseline is 16.0.x. See [Support options for enterprise and professional customers](https://docs.microsoft.com/visualstudio/releases/2019/servicing#support-options-for-enterprise-and-professional-customers) for more information.
 
 ## How to get onto a servicing baseline
 

mac/2017/installation.md

@@ -62,7 +62,7 @@ For working with iOS in Visual Studio you need the following pieces:
       - Fully cross-platform Xamarin apps – Select **Android**, **iOS**, and **macOS** platforms.
    * **.NET Core applications** – Select **.NET Core** platform.
    * **ASP.NET Core Web Applications** – Select **.NET Core** platform.
-   * **Cross-platform Unity Game Development** – No additional platforms need to be installed beyond Visual Studio for Mac. Refer to the [Unity setup guide](/visualstudio/macm/setup-vsmac-tools-unity) for more information on installing the Unity extension.
+   * **Cross-platform Unity Game Development** – No additional platforms need to be installed beyond Visual Studio for Mac. Refer to the [Unity setup guide](/visualstudio/mac/setup-vsmac-tools-unity) for more information on installing the Unity extension.
 
    This installation screen displays the version and size of each individual component. You can click each component to display a list of dependencies for that component (for Android), see additional packages that it downloads (for .NET Core), or view any additional applications required (for iOS and macOS):
 

mac/2017/javascript.md

@@ -34,7 +34,7 @@ Visual Studio for Mac uses the [JavaScript Language Service](/visualstudio/ide/j
 JavaScript intellisense in Visual Studio for Mac can be based on type inference, JSDoc, or TypeScript declaration.
 
 - **Type inference** – The type of an object is figured out by the surrounding code context. For more information, see Visual Studio's section on [IntelliSense based on type inference](/visualstudio/ide/javascript-intellisense#intellisense-based-on-type-inference).
-- **JSDoc** – There are times when type inference doesn't provide the correct type information. In these cases, the type information can be provided explicitly by [JSDoc](http://usejsdoc.org/about-getting-started.html) annotations. For more information, see Visual Studio's section on [IntelliSense based on JSDoc](/visualstudio/ide/javascript-intellisense#intellisense-based-on-jsdoc)
+- **JSDoc** – There are times when type inference doesn't provide the correct type information. In these cases, the type information can be provided explicitly by [JSDoc](https://jsdoc.app/about-getting-started.html) annotations. For more information, see Visual Studio's section on [IntelliSense based on JSDoc](/visualstudio/ide/javascript-intellisense#intellisense-based-on-jsdoc)
 - **TypeScript declaration files** – `.d.ts` files are used to provide values for JavaScript IntelliSense. Types declared in that file can be used as types on JSDoc comments. For more information, see Visual Studio's section on [IntelliSense based on TypeScript declaration files](/visualstudio/ide/javascript-intellisense#intellisense-based-on-typescript-declaration-files)
 
     ![adding a typescript definition file](media/javascript-image3.png)

mac/2017/report-a-problem.md

@@ -52,7 +52,7 @@ To report a problem with Visual Studio for Mac, select **Help > Report a Problem
 
 1. Select **Submit** to send your report, along with any images and log files.
 
-   For information about what data is collected, see [Data we collect](/visualstudio/ide/developer-community-privacy.md#data-we-collect).
+   For information about what data is collected, see [Data we collect](/visualstudio/ide/developer-community-privacy#data-we-collect).
 
 ## Search for solutions or provide feedback
 

mac/2017/tf-version-control.md

@@ -152,7 +152,7 @@ The following options can be used to authenticate with a server:
 
 To use basic authentication it is necessary to enable **Alternative authentication credentials** in Azure DevOps Services, by following the steps below:
 
-1. Sign in to your Azure DevOps organization as the owner (https://dev.azure.com/{organization}/{project}).
+1. Sign in to your Azure DevOps organization as the owner (https:\//dev.azure.com/{organization}/{project}).
 
 2. From your organization toolbar, select the gear icon and select **Policy**:
 

mac/javascript.md

@@ -34,7 +34,7 @@ Visual Studio for Mac uses the [JavaScript Language Service](/visualstudio/ide/j
 JavaScript intellisense in Visual Studio for Mac can be based on type inference, JSDoc, or TypeScript declaration.
 
 - **Type inference** – The type of an object is figured out by the surrounding code context. For more information, see Visual Studio's section on [IntelliSense based on type inference](/visualstudio/ide/javascript-intellisense#intellisense-based-on-type-inference).
-- **JSDoc** – There are times when type inference doesn't provide the correct type information. In these cases, the type information can be provided explicitly by [JSDoc](http://usejsdoc.org/about-getting-started.html) annotations. For more information, see Visual Studio's section on [IntelliSense based on JSDoc](/visualstudio/ide/javascript-intellisense#intellisense-based-on-jsdoc)
+- **JSDoc** – There are times when type inference doesn't provide the correct type information. In these cases, the type information can be provided explicitly by [JSDoc](https://jsdoc.app/about-getting-started.html) annotations. For more information, see Visual Studio's section on [IntelliSense based on JSDoc](/visualstudio/ide/javascript-intellisense#intellisense-based-on-jsdoc)
 - **TypeScript declaration files** – `.d.ts` files are used to provide values for JavaScript IntelliSense. Types declared in that file can be used as types on JSDoc comments. For more information, see Visual Studio's section on [IntelliSense based on TypeScript declaration files](/visualstudio/ide/javascript-intellisense#intellisense-based-on-typescript-declaration-files)
 
     ![adding a typescript definition file](media/javascript-image3.png)

mac/report-a-problem.md

@@ -52,7 +52,7 @@ To report a problem with Visual Studio for Mac, select **Help > Report a Problem
 
 1. Select **Submit** to send your report, along with any images and log files.
 
-   For information about what data is collected, see [Data we collect](/visualstudio/ide/developer-community-privacy.md#data-we-collect).
+   For information about what data is collected, see [Data we collect](/visualstudio/ide/developer-community-privacy#data-we-collect).
 
 ## Search for solutions or provide feedback
 

mac/tf-version-control.md

@@ -238,7 +238,7 @@ The following options can be used to authenticate with a server:
 
 To use basic authentication it is necessary to enable **Alternative authentication credentials** in Azure DevOps Services, by following the steps below:
 
-1. Sign in to your Azure DevOps organization as the owner (https://dev.azure.com/{organization}/{project}).
+1. Sign in to your Azure DevOps organization as the owner (https:\//dev.azure.com/{organization}/{project}).
 
 2. From your organization toolbar, select the gear icon and select **Policy**:
 

subscriptions/vs-office-dev.md

@@ -77,6 +77,6 @@ Not sure which subscription you're using?  Connect to [https://my.visualstudio.c
 
 ## Support resources
 
-- Need help with your Office Developer subscription? Check out the [support](https://developer.microsoft.com/office/support) resources on the [Office Dev Center](https://developer.microsoft.com/office).
+- Need help with your Office Developer subscription? Check out the [support](https://developer.microsoft.com/office/docs#officecommunity) resources on the [Office Dev Center](https://developer.microsoft.com/office).
 - For assistance with sales, subscriptions, accounts and billing for Visual Studio Subscriptions, contact Visual Studio [Subscriptions Support](https://visualstudio.microsoft.com/subscriptions/support/).
 - Have a question about Visual Studio IDE, Azure DevOps Services or other Visual Studio products or services?  Visit [Visual Studio Support](https://visualstudio.microsoft.com/support/).