Fix xref format issue in MetadataLoadContext.xml and LinqDataSourceView.xml (#4266)

Author: TianqiZhang

xml/System.Reflection/MetadataLoadContext.xml

@@ -121,7 +121,7 @@ If a core assembly cannot be found or if the core assembly is missing types, thi
 
   * <xref:System.Reflection.MethodInfo.ReturnType?displayProperty=nameWithType>
   * <xref:System.Reflection.MethodBase.GetParameters%2A?displayProperty=nameWithType>
-  * <xref:System.Type.BaseType?displayProperty-nameWithType>
+  * <xref:System.Type.BaseType?displayProperty=nameWithType>
   * <xref:System.Type.GetInterfaces%2A?displayProperty=nameWithType>
 
 * APIs that need to compare types to well-known core types will not throw an exception, and the comparison will evaluate to `false`. For example, if you do not specify a core assembly, <xref:System.Type.IsPrimitive> will return `false` for everything, even types named <xref:System.Int32>. Similarly, <xref:System.Type.GetTypeCode%2A?displayProperty=nameWithType> will return <xref:System.TypeCode.Object> for everything.

xml/System.Web.UI.WebControls/LinqDataSourceView.xml

@@ -2104,7 +2104,7 @@ For more information, see the <xref:System.Web.UI.WebControls.LinqDataSource.Ord
 ## Remarks  
 The `SaveViewState` method is primarily used by control developers.
 
-View state is the accumulation of the values of the properties for a server control. These values are automatically added to the <xref:System.Web.UI.Control.ViewState> property of the server control, which is an instance of the <xref>:System.Web.UI.StateBag> class. The <xref:System.Web.UI.Control.ViewState> value for the server control is then persisted to a string object after the save-state stage of the server control life cycle.
+View state is the accumulation of the values of the properties for a server control. These values are automatically added to the <xref:System.Web.UI.Control.ViewState> property of the server control, which is an instance of the <xref:System.Web.UI.StateBag> class. The <xref:System.Web.UI.Control.ViewState> value for the server control is then persisted to a string object after the save-state stage of the server control life cycle.
 
 When view state is saved, the string object that was persisted after the save-state stage of the server control life cycle is rendered to the browser as an HTML hidden element. When you create custom server controls, you can improve efficiency by overriding the `SaveViewState` method and modifying the `ViewState` property for your server control. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).