Feedback

mairaw · gewarren · mairaw · commit cd19d8358870 · 2020-06-03T01:32:31.000-07:00
Co-Authored-By: Genevieve Warren &lt;gewarren@microsoft.com&gt;
diff --git a/xml/System.Data.Objects.DataClasses/EntityCollection`1.xml b/xml/System.Data.Objects.DataClasses/EntityCollection`1.xml
@@ -220,7 +220,7 @@
 
  -or-
 
- The relationship cannot be defined based on the [Adventure Works Sales Model](https://archive.codeplex.com/?p=msftdbprodsamples)EDM metadata. This can occur when the association in the conceptual schema does not support a relationship between the two types.</exception>
+ The relationship cannot be defined based on the [Adventure Works Sales Model](https://archive.codeplex.com/?p=msftdbprodsamples) EDM metadata. This can occur when the association in the conceptual schema does not support a relationship between the two types.</exception>
       </Docs>
     </Member>
     <Member MemberName="Attach">
diff --git a/xml/System.Resources/SatelliteContractVersionAttribute.xml b/xml/System.Resources/SatelliteContractVersionAttribute.xml
@@ -62,7 +62,7 @@
   
  If you want to revise a satellite assembly but not the main assembly, increment the version number on your satellite. In this case, ship a publisher policy assembly along with your satellite assembly stating that your new satellite assembly has backward compatibility with your old satellite assembly. The resource manager will still use the old contract number written into your main assembly based on the <xref:System.Resources.SatelliteContractVersionAttribute> attribute; however, the loader will bind to the satellite assembly version that is specified by the policy assembly.  
   
- A vendor of a shared component uses a publisher policy assembly to make a compatibility statement about a particular version of a released assembly. A publisher policy assembly is a strongly named assembly that has a name in the format `policy.<major>.<minor>.<ComponentAssemblyName>`, and is registered in the [Global Assembly Cache (GAC)](/dotnet/framework/app-domains/gac). The publisher policy is generated from an XML configuration file (see the ) by using the [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker) tool. The Assembly Linker is used with the `/link` option to link the XML configuration file to a manifest assembly, which is then stored in the global assembly cache. The publisher policy assemblies can be used when a vendor ships a maintenance release (service pack) that contains bug fixes.  
+ A vendor of a shared component uses a publisher policy assembly to make a compatibility statement about a particular version of a released assembly. A publisher policy assembly is a strongly named assembly that has a name in the format `policy.<major>.<minor>.<ComponentAssemblyName>`, and is registered in the [Global Assembly Cache (GAC)](/dotnet/framework/app-domains/gac). The publisher policy is generated from an XML configuration file (see the [\<bindingRedirect> Element](/dotnet/framework/configure-apps/file-schema/runtime/bindingredirect-element)) by using the [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker) tool. The Assembly Linker is used with the `/link` option to link the XML configuration file to a manifest assembly, which is then stored in the global assembly cache. The publisher policy assemblies can be used when a vendor ships a maintenance release (service pack) that contains bug fixes.  
   
 ## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps  
  This attribute is ignored in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, because package resource index (PRI) files do not have versioning semantics. In addition, the [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] packaging model requires all resources to ship in the same package, with no possibility of redeploying satellite assemblies or PRI files.  
diff --git a/xml/System.Windows.Media.Animation/VectorAnimation.xml b/xml/System.Windows.Media.Animation/VectorAnimation.xml
@@ -42,7 +42,7 @@
  For information about applying multiple animations to a single property, see [Key-Frame Animations Overview](/dotnet/framework/wpf/graphics-multimedia/key-frame-animations-overview).  
   
 ## Freezable Features  
- Because the <xref:System.Windows.Media.Animation.VectorAnimation> class inherits from <xref:System.Windows.Freezable>, <xref:System.Windows.Media.Animation.VectorAnimation> objects gain several special features, which include the following: they can be declared as [resources](/dotnet/desktop-wpf/fundamentals/xaml-resources-define),shared among multiple objects, made read-only to improve performance, cloned, and made thread-safe. For more information about the different features provided by <xref:System.Windows.Freezable> objects, see the [Freezable Objects Overview](/dotnet/framework/wpf/advanced/freezable-objects-overview).  
+ Because the <xref:System.Windows.Media.Animation.VectorAnimation> class inherits from <xref:System.Windows.Freezable>, <xref:System.Windows.Media.Animation.VectorAnimation> objects gain several special features, which include the following: they can be declared as [resources](/dotnet/desktop-wpf/fundamentals/xaml-resources-define), shared among multiple objects, made read-only to improve performance, cloned, and made thread-safe. For more information about the different features provided by <xref:System.Windows.Freezable> objects, see the [Freezable Objects Overview](/dotnet/framework/wpf/advanced/freezable-objects-overview).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media/DoubleCollection.xml b/xml/System.Windows.Media/DoubleCollection.xml
@@ -61,7 +61,7 @@
 ## Remarks  
  Members of this class behave exactly as described by the <xref:System.Collections.Generic.IList%601>, <xref:System.Collections.Generic.ICollection%601>, and <xref:System.Collections.Generic.IEnumerable%601> documentation, except that this implementation throws an <xref:System.ArgumentException> if you attempt to insert `null` into the collection.  
   
- **Freezable Features:** Because it inherits from the <xref:System.Windows.Freezable> class, the <xref:System.Windows.Media.DoubleCollection> class provides several special features: <xref:System.Windows.Media.DoubleCollection> objects can be declared as [resources](/dotnet/desktop-wpf/fundamentals/xaml-resources-define),shared among multiple objects, made read-only to improve performance, cloned, and made thread-safe. For more information about the different features provided by <xref:System.Windows.Freezable> objects, see the [Freezable Objects Overview](/dotnet/framework/wpf/advanced/freezable-objects-overview).  
+ **Freezable Features:** Because it inherits from the <xref:System.Windows.Freezable> class, the <xref:System.Windows.Media.DoubleCollection> class provides several special features: <xref:System.Windows.Media.DoubleCollection> objects can be declared as [resources](/dotnet/desktop-wpf/fundamentals/xaml-resources-define), shared among multiple objects, made read-only to improve performance, cloned, and made thread-safe. For more information about the different features provided by <xref:System.Windows.Freezable> objects, see the [Freezable Objects Overview](/dotnet/framework/wpf/advanced/freezable-objects-overview).  
   
 <a name="xamlAttributeUsage_DoubleCollection"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Media/Drawing.xml b/xml/System.Windows.Media/Drawing.xml
@@ -29,7 +29,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Drawing> objects are light-weight objects that enable you to add geometric shapes, images, text, and media to an application. <xref:System.Windows.Media.Drawing> objects are considered light-weight because they do not provide support for [Layout](/dotnet/framework/wpf/advanced/layout), [Input Overview](/dotnet/framework/wpf/advanced/input-overview), and focus. Because of their performance benefits, drawings are ideal for backgrounds and clip art. You also use drawings when programming at the <xref:System.Windows.Media.Visual> level.  
   
- Because they inherit from the <xref:System.Windows.Freezable> class, <xref:System.Windows.Media.Drawing> objects provide additional features that make them useful for describing clip art and backgrounds: they can be declared as [resources](/dotnet/desktop-wpf/fundamentals/xaml-resources-define),shared among multiple objects, made read-only, and made thread-safe. For more information about the different features provided by <xref:System.Windows.Freezable> objects, see the [Freezable Objects Overview](/dotnet/framework/wpf/advanced/freezable-objects-overview).  
+ Because they inherit from the <xref:System.Windows.Freezable> class, <xref:System.Windows.Media.Drawing> objects  provide additional features that make them useful for describing clip art and backgrounds: they can be declared as [resources](~/docs/desktop-wpf/fundamentals/xaml-resources-define.md), shared among multiple objects, made read-only, and made thread-safe. For more information about the different features provided by <xref:System.Windows.Freezable> objects, see the [Freezable Objects Overview](~/docs/framework/wpf/advanced/freezable-objects-overview.md).  
   
  There are different types of <xref:System.Windows.Media.Drawing> objects for different types of content: <xref:System.Windows.Media.GeometryDrawing>, <xref:System.Windows.Media.ImageDrawing>,  <xref:System.Windows.Media.DrawingGroup>,  <xref:System.Windows.Media.VideoDrawing>, and  <xref:System.Windows.Media.GlyphRunDrawing>.  
   
