Absolute urls and other fixes

_zip/missingapi.yml

@@ -2,91 +2,91 @@
 hrefUpdated: true
 references:
 - uid: System.Xml.Linq.XElement.Elements*
-  href: https://msdn.microsoft.com/en-us/library/system.xml.linq.xelement.elements(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.xml.linq.xelement.elements(v=vs.110).aspx
   name: Elements
   name.vb: Elements
   fullName: XElement.Elements
   fullName.vb: XElement.Elements
 - uid: System.Xml.Linq.XElement.ToString*
-  href: https://msdn.microsoft.com/en-us/library/system.xml.linq.xelement.tostring(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.xml.linq.xelement.tostring(v=vs.110).aspx
   name: ToString
   name.vb: ToString
   fullName: XElement.ToString
   fullName.vb: XElement.ToString
 - uid: System.Xml.Linq.XDocument.ToString*
-  href: https://msdn.microsoft.com/en-us/library/system.xml.linq.xdocument.tostring(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.xml.linq.xdocument.tostring(v=vs.110).aspx
   name: ToString
   name.vb: ToString
   fullName: XDocument.ToString
   fullName.vb: XDocument.ToString
 - uid: System​.Runtime​.CompilerServices.IndexerNameAttribute
-  href: https://msdn.microsoft.com/en-us/library/system.runtime.compilerservices.indexernameattribute(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.runtime.compilerservices.indexernameattribute(v=vs.110).aspx
   name: IndexerNameAttribute
   name.vb: IndexerNameAttribute
   fullName: System.Runtime.CompilerServices.IndexerNameAttribute
   fullName.vb: System.Runtime.CompilerServices.IndexerNameAttribute
 - uid: System.Reflection.MethodInfo.IsGenericMethodDefinition*
-  href: https://msdn.microsoft.com/en-us/library/system.reflection.methodinfo.isgenericmethoddefinition(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.reflection.methodinfo.isgenericmethoddefinition(v=vs.110).aspx
   name: IsGenericMethodDefinition
   name.vb: IsGenericMethodDefinition
   fullName: MethodInfo.IsGenericMethodDefinition
   fullName.vb: MethodInfo.IsGenericMethodDefinition
 - uid: System​.Runtime​.InteropServices.FieldOffsetAttribute
-  href: https://msdn.microsoft.com/en-us/library/system.runtime.interopservices.fieldoffsetattribute(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.runtime.interopservices.fieldoffsetattribute(v=vs.110).aspx
   name: FieldOffsetAttribute
   name.vb: FieldOffsetAttribute
   fullName: System​.Runtime​.InteropServices.FieldOffsetAttribute
   fullName.vb: System​.Runtime​.InteropServices.FieldOffsetAttribute
 - uid: System​.Runtime​.InteropServices.StructLayoutAttribute
-  href: https://msdn.microsoft.com/en-us/library/system.runtime.interopservices.structlayoutattribute(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.runtime.interopservices.structlayoutattribute(v=vs.110).aspx
   name: StructLayoutAttribute
   name.vb: StructLayoutAttribute
   fullName: System​.Runtime​.InteropServices.StructLayoutAttribute
   fullName.vb: System​.Runtime​.InteropServices.StructLayoutAttribute
 - uid: System​.Runtime​.InteropServices.DllImportAttribute
-  href: https://msdn.microsoft.com/en-us/library/system.runtime.interopservices.dllimportattribute(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.runtime.interopservices.dllimportattribute(v=vs.110).aspx
   name: DllImportAttribute
   name.vb: DllImportAttribute
   fullName: System​.Runtime​.InteropServices.DllImportAttribute
   fullName.vb: System​.Runtime​.InteropServices.DllImportAttribute
 - uid: System​.Runtime​.InteropServices.OutAttribute
-  href: https://msdn.microsoft.com/en-us/library/system.runtime.interopservices.outattribute(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.runtime.interopservices.outattribute(v=vs.110).aspx
   name: OutAttribute
   name.vb: OutAttribute
   fullName: System​.Runtime​.InteropServices.OutAttribute
   fullName.vb: System​.Runtime​.InteropServices.OutAttribute
 - uid: System​.Runtime​.InteropServices.InAttribute
-  href: https://msdn.microsoft.com/en-us/library/system.runtime.interopservices.inattribute(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.runtime.interopservices.inattribute(v=vs.110).aspx
   name: InAttribute
   name.vb: InAttribute
   fullName: System​.Runtime​.InteropServices.InAttribute
   fullName.vb: System​.Runtime​.InteropServices.InAttribute
 - uid: System​.Runtime​.InteropServices.ComImportAttribute
-  href: https://msdn.microsoft.com/en-us/library/system.runtime.interopservices.comimportattribute(v=vs.110).aspx
+  href: https://msdn.microsoft.com/library/system.runtime.interopservices.comimportattribute(v=vs.110).aspx
   name: ComImportAttribute
   name.vb: ComImportAttribute
   fullName: System​.Runtime​.InteropServices.ComImportAttribute
   fullName.vb: System​.Runtime​.InteropServices.ComImportAttribute
 - uid: Microsoft.VisualBasic.PowerPacks.DataRepeater.BeginResetItemTemplate*
-  href: https://msdn.microsoft.com/en-us/library/microsoft.visualbasic.powerpacks.datarepeater.beginresetitemtemplate.aspx
+  href: https://msdn.microsoft.com/library/microsoft.visualbasic.powerpacks.datarepeater.beginresetitemtemplate.aspx
   name: BeginResetItemTemplate
   name.vb: BeginResetItemTemplate
   fullName: DataRepeater.BeginResetItemTemplate
   fullName.vb: DataRepeater.BeginResetItemTemplate
 - uid: Microsoft.VisualBasic.PowerPacks.DataRepeater.BeginResetItemTemplate
-  href: https://msdn.microsoft.com/en-us/library/microsoft.visualbasic.powerpacks.datarepeater.beginresetitemtemplate.aspx
+  href: https://msdn.microsoft.com/library/microsoft.visualbasic.powerpacks.datarepeater.beginresetitemtemplate.aspx
   name: BeginResetItemTemplate
   name.vb: BeginResetItemTemplate
   fullName: DataRepeater.BeginResetItemTemplate
   fullName.vb: DataRepeater.BeginResetItemTemplate
 - uid: Microsoft.VisualBasic.PowerPacks.DataRepeater.EndResetItemTemplate*
-  href: https://msdn.microsoft.com/en-us/library/microsoft.visualbasic.powerpacks.datarepeater.endresetitemtemplate.aspx
+  href: https://msdn.microsoft.com/library/microsoft.visualbasic.powerpacks.datarepeater.endresetitemtemplate.aspx
   name: EndResetItemTemplate
   name.vb: EndResetItemTemplate
   fullName: DataRepeater.EndResetItemTemplate
   fullName.vb: DataRepeater.EndResetItemTemplate
 - uid: Microsoft.VisualBasic.PowerPacks.DataRepeater.EndResetItemTemplate
-  href: https://msdn.microsoft.com/en-us/library/microsoft.visualbasic.powerpacks.datarepeater.endresetitemtemplate.aspx
+  href: https://msdn.microsoft.com/library/microsoft.visualbasic.powerpacks.datarepeater.endresetitemtemplate.aspx
   name: EndResetItemTemplate
   name.vb: EndResetItemTemplate
   fullName: DataRepeater.EndResetItemTemplate

docs/core/preview3/tools/dotnet-msbuild.md

@@ -24,9 +24,8 @@ dotnet-msbuild -- Builds a project and all of its dependencies
 ## Description
 The `dotnet msbuild` command allows access to a fully functional MSBuild 
 
-The command has the exact same capabilities as existing MSBuild command line client. The options are all the same. You can 
-use the [existing documentation](https://msdn.microsoft.com/en-us/library/ms164311.aspx) to get familiar with the command 
-reference. 
+The command has the exact same capabilities as existing MSBuild command-line client. The options are all the same. You can 
+use the [MSBuild Command-Line Reference](https://docs.microsoft.com/visualstudio/msbuild/msbuild-command-line-reference) to get familiar with the options. 
 
 ## Examples
 

docs/core/preview3/tools/layering.md

@@ -27,7 +27,7 @@ As part of this move, the custom build engine that was developed to build projec
 
 > [!NOTE]
 > If you are new to MSBuild and would like to learn more about it, you can start by reading 
-> the [existing documentation](https://msdn.microsoft.com/en-us/library/dd637714.aspx). 
+> the [MSBuild Concepts](https://docs.microsoft.com/visualstudio/msbuild/msbuild-concepts) article. 
 
 ## The tooling layers
 With the move away from the existing project system as well as with building engine switches, the question that naturally follows is do any of these changes change the overall "layering" of the whole .NET Core tooling ecosystem? Are there new bits and components?
@@ -45,7 +45,7 @@ With the move to the new project system, the previous diagram changes:
 The main difference is that the CLI is not the foundational layer anymore; this role is now filled by the "shared SDK component". This shared SDK component is a set of targets and associated tasks that are responsible for compiling your code, publishing it, packing nuget packages etc. The SDK itself is open-source and is available on GitHub on the [SDK repo](https://github.com/dotnet/sdk). 
 
 > [!NOTE]
-> A "target" is an MSBuild term that indicates a named operation that MSBuild can invoke. It is usually coupled with one or more tasks that execute some logic that the target is supposed to do. MSBuild supports many ready-made targets such as `Copy` or `Execute`; it also allows users to write their own tasks using managed code and define targets to execute those tasks. You can read more about MSBuild tasks on [MSDN](https://msdn.microsoft.com/en-us/library/ms171466.aspx). 
+> A "target" is an MSBuild term that indicates a named operation that MSBuild can invoke. It is usually coupled with one or more tasks that execute some logic that the target is supposed to do. MSBuild supports many ready-made targets such as `Copy` or `Execute`; it also allows users to write their own tasks using managed code and define targets to execute those tasks. For more information, see [MSBuild tasks](https://docs.microsoft.com/visualstudio/msbuild/msbuild-tasks). 
 
 All the toolsets now consume the shared SDK component and its targets, CLI included. For example, the next version of Visual Studio will not call into `dotnet restore` command to restore dependencies for .NET Core projects, it will use the "Restore" target directly. Since these are MSBuild targets, you can also use raw MSBuild to execute them using the [dotnet msbuild](dotnet-msbuild.md) command. 
 
@@ -75,5 +75,4 @@ This command is publishing an application into a `pub` folder using the "Release
 The notable exception to this rule are `new` and `run` commands, as they have not been implemented as MSBuild targets. 
 
 ## Conclusion 
-This document outlined at a high-level the changes that are happening to the overall CLI tooling architecture and functioning that are coming with Preview 3. It has introduced the notion of the shared SDK component as well as explained how the CLI commands function, from a technical perspective, in Preview 3. 
-
+This document outlined at a high-level the changes that are happening to the overall CLI tooling architecture and functioning that are coming with Preview 3. It has introduced the notion of the shared SDK component as well as explained how the CLI commands function, from a technical perspective, in Preview 3.