fix/replace links (dotnet#2822)

* fix/replace links

* fixed link

* Update removing-elements-attributes-and-nodes-from-an-xml-tree.md

* fixed broken links

* replaced one more link

* replaced a few more links

* fixed formatting

* fixed links format

* trying to fix broken link

* fixed links format

* added missing punctuation

* fixed link

Author: mairaw

docs/csharp/programming-guide/concepts/linq/removing-elements-attributes-and-nodes-from-an-xml-tree.md

@@ -1,21 +1,16 @@
 ---
 title: "Removing Elements, Attributes, and Nodes from an XML Tree (C#)"
-ms.custom: ""
 ms.date: "2015-07-20"
 ms.prod: .net
-ms.reviewer: ""
-ms.suite: ""
 ms.technology: 
   - "devlang-csharp"
-
 ms.topic: "article"
 dev_langs: 
   - "CSharp"
 ms.assetid: 07dd06d6-1117-4077-bf98-9120cf51176e
 caps.latest.revision: 4
 author: "BillWagner"
 ms.author: "wiwagn"
-
 ---
 # Removing Elements, Attributes, and Nodes from an XML Tree (C#)
 You can modify an XML tree, removing elements, attributes, and other types of nodes.  
@@ -28,8 +23,8 @@ You can modify an XML tree, removing elements, attributes, and other types of no
 
 |Method|Description|  
 |------------|-----------------|  
-|[XAttribute.Remove](https://msdn.microsoft.com/library/system.xml.linq.xattribute.remove\(v=vs.110\).aspx)|Removes an <xref:System.Xml.Linq.XAttribute> from its parent.|  
-|[XContainer.RemoveNodes](https://msdn.microsoft.com/library/system.xml.linq.xcontainer.removenodes\(v=vs.110\).aspx)|Removes the child nodes from an <xref:System.Xml.Linq.XContainer>.|  
+|<xref:System.Xml.Linq.XAttribute.Remove%2A?displayProperty=fullName>|Removes an <xref:System.Xml.Linq.XAttribute> from its parent.|  
+|<xref:System.Xml.Linq.XContainer.RemoveNodes%2A?displayProperty=fullName>|Removes the child nodes from an <xref:System.Xml.Linq.XContainer>.|  
 |<xref:System.Xml.Linq.XElement.RemoveAll%2A?displayProperty=fullName>|Removes content and attributes from an <xref:System.Xml.Linq.XElement>.|  
 |<xref:System.Xml.Linq.XElement.RemoveAttributes%2A?displayProperty=fullName>|Removes the attributes of an <xref:System.Xml.Linq.XElement>.|  
 |<xref:System.Xml.Linq.XElement.SetAttributeValue%2A?displayProperty=fullName>|If you pass `null` for value, then removes the attribute.|  

docs/framework/app-domains/how-to-load-assemblies-into-an-application-domain.md

@@ -19,9 +19,9 @@ ms.author: "ronpet"
 manager: "wpickett"
 ---
 # How to: Load Assemblies into an Application Domain
-There are several ways to load an assembly into an application domain. The recommended way is to use the `static` (`Shared` in Visual Basic) <xref:System.Reflection.Assembly.Load%2A> method of the [System.Reflection.Assembly](https://msdn.microsoft.com/en-us/library/system.reflection.aspx) class. Other ways assemblies can be loaded include:  
+There are several ways to load an assembly into an application domain. The recommended way is to use the `static` (`Shared` in Visual Basic) <xref:System.Reflection.Assembly.Load%2A> method of the <xref:System.Reflection.Assembly?displayProperty=fullName> class. Other ways assemblies can be loaded include:  
 
--   The <xref:System.Reflection.Assembly.LoadFrom%2A> method of the [Assembly](https://msdn.microsoft.com/en-us/library/system.reflection.aspx) class loads an assembly given its file location. Loading assemblies with this method uses a different load context.  
+-   The <xref:System.Reflection.Assembly.LoadFrom%2A> method of the <xref:System.Reflection.Assembly> class loads an assembly given its file location. Loading assemblies with this method uses a different load context.  
 
 -   The <xref:System.Reflection.Assembly.ReflectionOnlyLoad%2A> and <xref:System.Reflection.Assembly.ReflectionOnlyLoadFrom%2A> methods load an assembly into the reflection-only context. Assemblies loaded into this context can be examined but not executed, allowing the examination of assemblies that target other platforms. See [How to: Load Assemblies into the Reflection-Only Context](../../../docs/framework/reflection-and-codedom/how-to-load-assemblies-into-the-reflection-only-context.md).  
 

docs/framework/deployment/how-the-runtime-locates-assemblies.md

@@ -42,7 +42,7 @@ To successfully deploy your .NET Framework application, you must understand how
 
  You can also make a dynamic reference to an assembly by providing the calling method with only partial information about the assembly, such as specifying only the assembly name. In this case, only the application directory is searched for the assembly, and no other checking occurs. You make a partial reference using any of the various methods for loading assemblies such as <xref:System.Reflection.Assembly.Load%2A?displayProperty=fullName> or <xref:System.AppDomain.Load%2A?displayProperty=fullName>.  
 
- Finally, you can make a dynamic reference using a method such as [System.Reflection.Assembly.Load](https://msdn.microsoft.com/en-us/library/system.reflection.assembly.load.aspx) and provide only partial information; you then qualify the reference using the [\<qualifyAssembly>](../../../docs/framework/configure-apps/file-schema/runtime/qualifyassembly-element.md) element in the application configuration file. This element allows you to provide the full reference information (name, version, culture and, if applicable, the public key token) in your application configuration file instead of in your code. You would use this technique if you wanted to fully qualify a reference to an assembly outside the application directory, or if you wanted to reference an assembly in the global assembly cache but you wanted the convenience of specifying the full reference in the configuration file instead of in your code.  
+ Finally, you can make a dynamic reference using a method such as <xref:System.Reflection.Assembly.Load*?displayProperty=fullName> and provide only partial information; you then qualify the reference using the [\<qualifyAssembly>](../../../docs/framework/configure-apps/file-schema/runtime/qualifyassembly-element.md) element in the application configuration file. This element allows you to provide the full reference information (name, version, culture and, if applicable, the public key token) in your application configuration file instead of in your code. You would use this technique if you wanted to fully qualify a reference to an assembly outside the application directory, or if you wanted to reference an assembly in the global assembly cache but you wanted the convenience of specifying the full reference in the configuration file instead of in your code.  
 
 > [!NOTE]
 >  This type of partial reference should not be used with assemblies that are shared among several applications. Because configuration settings are applied per application and not per assembly, a shared assembly using this type of partial reference would require each application using the shared assembly to have the qualifying information in its configuration file.  

docs/framework/migration-guide/net-framework-4-migration-issues.md

@@ -256,8 +256,8 @@ Namespaces: <xref:System.Windows>, <xref:System.Windows.Controls>, <xref:System.
 | ------- | ------------------------ | ------------------- |
 | **Binding command instances** | To provide a mechanism to bind View-Model-based command instances to View-based input gestures, the <xref:System.Windows.Input.InputBinding> class now inherits from <xref:System.Windows.Freezable> instead of <xref:System.Windows.DependencyObject>. The following properties are now dependency properties:<br><br>* <xref:System.Windows.Input.InputBinding.Command><br>* <xref:System.Windows.Input.InputBinding.CommandParameter><br>* <xref:System.Windows.Input.InputBinding.CommandTarget><br><br>This change results in the following:<br><br>* An <xref:System.Windows.Input.InputBinding> object is now frozen when it is registered instead of remaining mutable.<br>* You cannot access instance-level <xref:System.Windows.Input.InputBinding> objects from multiple threads, due to the restrictions of the <xref:System.Windows.DependencyObject> class.<br>* You cannot mutate class-level input bindings after their registration, due to the restrictions of the <xref:System.Windows.Freezable> class.<br>* You cannot specify input bindings on command instances that are created in a View-Model. | Create separate instances of an <xref:System.Windows.Input.InputBinding> class on separate threads if bindings are to be mutable, or freeze them otherwise. Do not mutate a class-level static <xref:System.Windows.Input.InputBinding> after it has been registered. |
 | **Browser applications** | WPF Browser applications (.XBAP) now process key events just like stand-alone WPF applications so that objects receive routed key events in the correct order. | None. |
-| **Dead key combinations** | WPF obfuscates dead keys, which produce no visible character, but instead indicates that the key is to be combined with the next letter key to produce one character. The key input events, such as the [KeyDown](https://msdn.microsoft.com/library/system.windows.input.keyboard.keydown(v=vs.100).aspx) event, report when a key is a dead key by setting the <xref:System.Windows.Input.KeyEventArgs.Key> property to the <xref:System.Windows.Input.Key> value. This is usually expected behavior because applications usually do not intend to respond to keyboard input that creates a combined character. | Applications that expect to read keys that were part of combined characters can get the now obfuscated key by using the <xref:System.Windows.Input.KeyEventArgs.DeadCharProcessedKey> property. |
-| **Focus manager** | When the [FocusManager.GetFocusedElement](https://msdn.microsoft.com/library/ms604088(v=vs.100).aspx) method is passed an element that has the [IsFocusScope](https://msdn.microsoft.com/library/system.windows.input.focusmanager.isfocusscope(v=vs.100).aspx) attached property set to `true`, the method returns an element that is the last keyboard-focused element within that focus scope if and only if the returned element belongs to the same <xref:System.Windows.PresentationSource> object as the element that is passed to the method. | None. |
+| **Dead key combinations** | WPF obfuscates dead keys, which produce no visible character, but instead indicates that the key is to be combined with the next letter key to produce one character. The key input events, such as the <xref:System.Windows.Input.Keyboard.KeyDownEvent> event, report when a key is a dead key by setting the <xref:System.Windows.Input.KeyEventArgs.Key> property to the <xref:System.Windows.Input.Key> value. This is usually expected behavior because applications usually do not intend to respond to keyboard input that creates a combined character. | Applications that expect to read keys that were part of combined characters can get the now obfuscated key by using the <xref:System.Windows.Input.KeyEventArgs.DeadCharProcessedKey> property. |
+| **Focus manager** | When the <xref:System.Windows.Input.FocusManager.GetFocusedElement(System.Windows.DependencyObject)?displayProperty=fullName> method is passed an element that has the [IsFocusScope](https://msdn.microsoft.com/library/system.windows.input.focusmanager.isfocusscope.aspx) attached property set to `true`, the method returns an element that is the last keyboard-focused element within that focus scope if and only if the returned element belongs to the same <xref:System.Windows.PresentationSource> object as the element that is passed to the method. | None. |
 
 ### UI Automation
 
@@ -292,7 +292,7 @@ Namespaces: <xref:System.Xml.Linq>; <xref:System.Xml.Schema>, <xref:System.Xml.X
 | Feature | Differences from 3.5 SP1 |
 | ------- | ------------------------ |
 | **Chameleon schemas** | To prevent data corruption, chameleon schemas are now cloned correctly when they are included with multiple schemas.<br><br>Chameleon schemas are schemas that do not have a target namespace, and when they are included in another XSD, they take on the target namespace of the importing schema. They are often used to include common types into a schema. |
-| **ID functions** | The XSLT [id function](https://msdn.microsoft.com/library/ms190915.aspx) now returns the correct value instead of null when an <xref:System.Xml.XmlReader> object is passed to an XLST.<br><br>If the user created an <xref:System.Xml.XmlReader> object from a LINQ to XML class by using the <xref:System.Xml.Linq.XNode.CreateReader%2A> method, and this <xref:System.Xml.XmlReader> object was passed to an XSLT, any instances of the `id` function in the XSLT previously returned null. This is not an allowed return value for the `id` function. |
+| **ID functions** | The XSLT [id function](/sql/xquery/functions-on-sequences-id) now returns the correct value instead of null when an <xref:System.Xml.XmlReader> object is passed to an XLST.<br><br>If the user created an <xref:System.Xml.XmlReader> object from a LINQ to XML class by using the <xref:System.Xml.Linq.XNode.CreateReader%2A> method, and this <xref:System.Xml.XmlReader> object was passed to an XSLT, any instances of the `id` function in the XSLT previously returned null. This is not an allowed return value for the `id` function. |
 | **Namespace attribute** | To prevent data corruption, an <xref:System.Xml.XPath.XPathNavigator> object now returns the local name of the `x:xmlns` attribute correctly. |
 | **Namespace declarations** | An <xref:System.Xml.XmlReader> object on a sub-tree no longer creates duplicate namespace declarations within one XML element. |
 | **Schema validation** | To prevent erroneous schema validation, the <xref:System.Xml.Schema.XmlSchemaSet> class allows for XSD schemas to be compiled correctly and consistently. These schemas can include other schemas; for example, `A.xsd` can include `B.xsd`, which can include `C.xsd`. Compiling any one of these causes this graph of dependencies to be traversed. |

docs/framework/tools/winres-exe-windows-forms-resource-editor.md

@@ -140,7 +140,7 @@ winres /?
   
 4.  To save the localized version of the .resx or .resources file, click the **Save** icon or the same command on the **File** menu. The tool displays the **Select Culture** window.  
   
-5.  Select the appropriate culture and file mode then click **OK**. The tool saves the file, using the naming convention that the run time expects for localized resource files. For example, if you localize `TestApp.resources` for German in Germany, the tool saves the file as `TestApp.de-DE.resources`. If you localize `TestApp.resx` for German in Germany, the tool saves the file as `TestApp.de-DE.resx`. For more information about resource naming conventions, see [Packaging and Deploying Resources](../../../docs/framework/resources/packaging-and-deploying-resources-in-desktop-apps.md). For a list of the predefined culture names used by the run time, see the [CultureInfo Class](https://msdn.microsoft.com/en-us/library/system.globalization.cultureinfo.aspx).  
+5.  Select the appropriate culture and file mode then click **OK**. The tool saves the file, using the naming convention that the run time expects for localized resource files. For example, if you localize `TestApp.resources` for German in Germany, the tool saves the file as `TestApp.de-DE.resources`. If you localize `TestApp.resx` for German in Germany, the tool saves the file as `TestApp.de-DE.resx`. For more information about resource naming conventions, see [Packaging and Deploying Resources](../../../docs/framework/resources/packaging-and-deploying-resources-in-desktop-apps.md). For a list of the predefined culture names used by the run time, see the <xref:System.Globalization.CultureInfo> class.  
   
 ## See Also  
  <xref:System.ComponentModel.LocalizableAttribute>   

docs/framework/unmanaged-api/profiling/icorprofilercallback7-moduleinmemorysymbolsupdated-method.md

@@ -27,7 +27,7 @@ manager: "wpickett"
 # ICorProfilerCallback7::ModuleInMemorySymbolsUpdated Method
 [Supported in the .NET Framework 4.6.1 and later versions]  
 
- Notifies the profiler whenever the symbol stream associated with an     in-memory module is updated.  
+ Notifies the profiler whenever the symbol stream associated with an in-memory module is updated.  
 
 ## Syntax  
 
@@ -45,9 +45,9 @@ HRESULT ModuleInMemorySymbolsUpdated(
  This callback is controlled by setting the [COR_PRF_HIGH_IN_MEMORY_SYMBOLS_UPDATED](../../../../docs/framework/unmanaged-api/profiling/cor-prf-high-monitor-enumeration.md) event mask flag when calling the [ICorProfilerCallback5::SetEventMask2](../../../../docs/framework/unmanaged-api/profiling/icorprofilerinfo5-seteventmask2-method.md) method.  
 
 > [!NOTE]
->  This event is not currently raised for symbols implicitly created or     modified via <xref:System.Reflection.Emit> APIs.  
+>  This event is not currently raised for symbols implicitly created or modified via <xref:System.Reflection.Emit> APIs.  
   
- Even when symbols are provided up front in     a call to one of the overloads of the managed [Assembly.Load](https://msdn.microsoft.com/library/system.reflection.assembly.load.aspx) methods that includes a `rawSymbolStore` argument to specify the symbols for the assembly, the runtime     may not actually associate the symbolic data with the module until after     the [ModuleLoadFinished](../../../../docs/framework/unmanaged-api/profiling/icorprofilercallback-moduleloadfinished-method.md) callback has occurred. This event provides a later     opportunity to collect symbols for such modules.  
+ Even when symbols are provided up front in a call to one of the overloads of the managed <xref:System.Reflection.Assembly.Load*?displayProperty=fullName> methods that includes a `rawSymbolStore` argument to specify the symbols for the assembly, the runtime may not actually associate the symbolic data with the module until after the [ModuleLoadFinished](../../../../docs/framework/unmanaged-api/profiling/icorprofilercallback-moduleloadfinished-method.md) callback has occurred. This event provides a later opportunity to collect symbols for such modules.  
 
 ## Requirements  
  **Platforms:** See [System Requirements](../../../../docs/framework/get-started/system-requirements.md).