SEOImages: User Story 1463880, Part 27 (#11384)

* Image updates.

* Image updates.

* SEO image updates.

* SEO image updates.

* SEO image updates.

* SEO image updates.

* SEO image updates.

* Update docs/framework/winforms/controls/bindingnavigator-control-overview-windows-forms.md

Co-Authored-By: damabe <[email protected]>

* Update docs/framework/winforms/controls/bindingnavigator-control-overview-windows-forms.md

Co-Authored-By: damabe <[email protected]>

* Reviewer feedback.

Author: damabe

docs/csharp/programming-guide/concepts/linq/media/linq_partition.png renamed to docs/csharp/programming-guide/concepts/linq/media/partitioning-data/linq-partitioning-operations.png

@@ -8,7 +8,7 @@ Partitioning in LINQ refers to the operation of dividing an input sequence into
 
  The following illustration shows the results of three different partitioning operations on a sequence of characters. The first operation returns the first three elements in the sequence. The second operation skips the first three elements and returns the remaining elements. The third operation skips the first two elements in the sequence and returns the next three elements.  
 
- ![LINQ Partitioning Operations](../../../../csharp/programming-guide/concepts/linq/media/linq_partition.png "LINQ_Partition")  
+ ![Illustration that shows three LINQ partitioning operations.](./media/partitioning-data/linq-partitioning-operations.png)  
 
  The standard query operator methods that partition sequences are listed in the following section.  
 

docs/csharp/programming-guide/concepts/linq/partitioning-data.md

@@ -26,7 +26,7 @@ The Entity Data Model (EDM) uses three key concepts to describe the structure of
 ## Representations of a Conceptual Model  
  A *conceptual model* is a specific representation of the structure of some data as entities and relationships. One way to represent a conceptual model is with a diagram. The following diagram represents a conceptual model with three entity types (`Book`, `Publisher`, and `Author`) and two associations (`PublishedBy` and `WrittenBy`):  
 
- ![Model with Navigation Properties](../../../../docs/framework/data/adonet/media/modelwithnavprops.gif "ModelWithNavProps")  
+ ![Diagram showing a conceptual model with three entity types.](./media/entity-data-model-key-concepts/conceptual-model-entity-types-associations.gif)  
 
  This representation, however, has some shortcomings when it comes to conveying some details about the model. For example, property type and entity set information are not conveyed in the diagram. The richness of a conceptual model can be conveyed more clearly with a domain-specific language (DSL). The [ADO.NET Entity Framework](../../../../docs/framework/data/adonet/ef/index.md) uses an XML-based DSL called *conceptual schema definition language* ([CSDL](../../../../docs/framework/data/adonet/ef/language-reference/csdl-specification.md)) to define conceptual models. The following is the CSDL definition of the conceptual model in the diagram above:  
 

docs/framework/data/adonet/entity-data-model-key-concepts.md

@@ -23,7 +23,7 @@ The data type of a navigation property is determined by the [multiplicity](assoc
 
 The diagram below shows a conceptual model with three entity types: `Book`, `Publisher`, and `Author`. Navigation properties, `Publisher` and `Authors`, are defined on the Book entity type. Navigation property `Books` is defined on both the Publisher entity type and the `Author` entity type.
 
-![Model with Navigation Properties](/media/modelwithnavprops.gif "ModelWithNavProps")
+ ![Diagram showing a conceptual model with three entity types.](./media/navigation-property/conceptual-model-entity-types-associations.gif)  
 
 The [ADO.NET Entity Framework](./ef/index.md) uses a domain-specific language (DSL) called conceptual schema definition language ([CSDL](./ef/language-reference/csdl-specification.md)) to define conceptual models. The following CSDL defines the `Book` entity type shown in the diagram above:
 

docs/framework/data/adonet/media/modelwithnavprops.gif renamed to docs/framework/data/adonet/media/entity-data-model-key-concepts/conceptual-model-entity-types-associations.gif

@@ -13,7 +13,7 @@ author: "BrucePerlerMS"
 
  This topic outlines the scenario of building claims-aware ASP.NET web applications using WIF. There are usually three participants in a claims-aware application scenario: the application itself, the end user, and the Security Token Service (STS). The following figure describes this scenario:  
 
- ![WIF Basic Web App](../../../docs/framework/security/media/wifbasicwebapp.gif "WIFBasicWebApp")  
+ ![Diagram showing a WIF Basic Web App components.](./media/building-my-first-claims-aware-aspnet-web-app/windows-identity-foundation-basic-web-application.gif)  
 
 1.  The claims-aware application uses WIF to identify unauthenticated requests and to redirect them to the STS.  
 

docs/framework/data/adonet/media/navigation-property/conceptual-model-entity-types-associations.gif

@@ -14,9 +14,10 @@ ms.assetid: 4423eede-f8d1-4d02-822f-5bf8432680d0
 You can use the <xref:System.Windows.Forms.BindingNavigator> control to create a standardized means for users to search and change data on a Windows Form. You frequently use <xref:System.Windows.Forms.BindingNavigator> with the <xref:System.Windows.Forms.BindingSource> component to enable users to move through data records on a form and interact with the records.  
 
 ## How the BindingNavigator Works  
- The <xref:System.Windows.Forms.BindingNavigator> control is composed of a <xref:System.Windows.Forms.ToolStrip> with a series of <xref:System.Windows.Forms.ToolStripItem> objects for most of the common data-related actions: adding data, deleting data, and navigating through data. By default, the <xref:System.Windows.Forms.BindingNavigator> control contains these standard buttons. The following screen shot shows the <xref:System.Windows.Forms.BindingNavigator> control on a form.  
+
+ The <xref:System.Windows.Forms.BindingNavigator> control is composed of a <xref:System.Windows.Forms.ToolStrip> with a series of <xref:System.Windows.Forms.ToolStripItem> objects for most of the common data-related actions: adding data, deleting data, and navigating through data. By default, the <xref:System.Windows.Forms.BindingNavigator> control contains these standard buttons. The following screenshot shows the <xref:System.Windows.Forms.BindingNavigator> control on a form:
 
- ![BindingNavigator Control](./media/cpdatacontainerctrl.gif "cpDataContainerCtrl")  
+ ![Screenshot showing the BindingNavigator control.](./media/bindingnavigator-control-overview-windows-forms/bindingnavigator-control-form.gif)  
 
  The following table lists the controls and describes their functions.