dotnet · Thraka · Mar 25, 2019 · Feb 27, 2019 · Feb 27, 2019 · Mar 6, 2019
diff --git a/docs/csharp/programming-guide/types/index.md b/docs/csharp/programming-guide/types/index.md
@@ -66,10 +66,12 @@ ms.assetid: f782d7cc-035e-4500-b1b1-36a9881130ad
 
 -   Each type in the CTS is defined as either a *value type* or a *reference type*. This includes all custom types in the .NET class library and also your own user-defined types. Types that you define by using the [struct](../../../csharp/language-reference/keywords/struct.md) keyword are value types; all the built-in numeric types are `structs`. Types that you define by using the [class](../../../csharp/language-reference/keywords/class.md) keyword are reference types. Reference types and value types have different compile-time rules, and different run-time behavior.  
 
- The following illustration shows the relationship between value types and reference types in the CTS.  
+ The following illustration shows the relationship between value types and reference types in the CTS.
+
+ The following image shows value types and reference types in the CTS: 
+
 
- ![Value Types and Reference Types](../../../csharp/programming-guide/types/media/valuetypescts.png "ValueTypesCTS")  
-Value types and reference types in the CTS  
+ ![Screenshot that shows CTS value types and reference types.](./media/index/value-reference-types-common-type-system.png)  
 
 > [!NOTE]
 >  You can see that the most commonly used types are all organized in the <xref:System> namespace. However, the namespace in which a type is contained has no relation to whether it is a value type or reference type.  

diff --git a/...mming-guide/types/media/valuetypescts.png → ...ue-reference-types-common-type-system.png b/...mming-guide/types/media/valuetypescts.png → ...ue-reference-types-common-type-system.png
diff --git a/...ure-details/media/transactionmanagers.gif → ...version-1-0/transaction-managers-flow.gif b/...ure-details/media/transactionmanagers.gif → ...version-1-0/transaction-managers-flow.gif
diff --git a/...k/wcf/feature-details/media/transaction-protocols/transaction-managers-flow.gif b/...k/wcf/feature-details/media/transaction-protocols/transaction-managers-flow.gif
diff --git a/...ature-details/media/securedbyusername.gif → ...ansport-security-basic-authentication.gif b/...ature-details/media/securedbyusername.gif → ...ansport-security-basic-authentication.gif
diff --git a/...tails/media/applicationserveraddcomps.jpg → ...ibuted-transaction-coordinator-access.jpg b/...tails/media/applicationserveraddcomps.jpg → ...ibuted-transaction-coordinator-access.jpg
diff --git a/docs/framework/wcf/feature-details/transaction-protocols-version-1-0.md b/docs/framework/wcf/feature-details/transaction-protocols-version-1-0.md
@@ -15,9 +15,9 @@ Windows Communication Foundation (WCF) version 1 implements version 1.0 of the W
 
  This topic describes a composition of the WS-Atomic Transaction (WS-AT) specification with security and describes the secure binding used for communication between transaction managers. The approach described in this document has been successfully tested with other implementations of WS-AT and WS-Coordination including IBM, IONA, Sun Microsystems, and others.  
 
- The following figure depicts the interoperability between two transaction managers, Transaction Manager 1 and Transaction Manager 2, and two applications, Application 1 and Application 2.  
+ The following figure depicts the interoperability between two transaction managers, Transaction Manager 1 and Transaction Manager 2, and two applications, Application 1 and Application 2:  
 
- ![Transaction Protocols](../../../../docs/framework/wcf/feature-details/media/transactionmanagers.gif "TransactionManagers")  
+ ![Screenshot that shows interaction between transaction managers.](./media/transaction-protocols/transaction-managers-flow.gif)  
 
  Consider a typical WS-Coordination/WS-Atomic Transaction scenario with one Initiator (I) and one Participant (P). Both Initiator and Participant have Transaction Managers, (ITM and PTM, respectively). Two-phase commit is referred to as 2PC in this topic.  
 

diff --git a/docs/framework/wcf/feature-details/transaction-protocols.md b/docs/framework/wcf/feature-details/transaction-protocols.md
@@ -15,9 +15,9 @@ Windows Communication Foundation (WCF) implements WS-Atomic Transaction and WS-C
 
  This topic describes a composition of the WS-Atomic Transaction (WS-AT) specification with security and describes the secure binding used for communication between transaction managers. The approach described in this document has been successfully tested with other implementations of WS-AT and WS-Coordination including IBM, IONA, Sun Microsystems, and others.  
 
- The following figure depicts the interoperability between two transaction managers, Transaction Manager 1 and Transaction Manager 2, and two applications, Application 1 and Application 2.  
+ The following figure depicts the interoperability between two transaction managers, Transaction Manager 1 and Transaction Manager 2, and two applications, Application 1 and Application 2:  
 
- ![Transaction Protocols](../../../../docs/framework/wcf/feature-details/media/transactionmanagers.gif "TransactionManagers")  
+ ![Screenshot that shows interaction between transaction managers.](./media/transaction-protocols/transaction-managers-flow.gif)  
 
  Consider a typical WS-Coordination/WS-Atomic Transaction scenario with one Initiator (I) and one Participant (P). Both Initiator and Participant have Transaction Managers, (ITM and PTM, respectively). Two-phase commit is referred to as 2PC in this topic.  
 

diff --git a/docs/framework/wcf/feature-details/transport-security-with-basic-authentication.md b/docs/framework/wcf/feature-details/transport-security-with-basic-authentication.md
@@ -9,7 +9,7 @@ ms.assetid: b54f491d-196b-4279-876c-76b83ec0442c
 # Transport Security with Basic Authentication
 The following illustration shows a Windows Communication Foundation (WCF) service and client. The server needs a valid X.509 certificate that can be used for Secure Sockets Layer (SSL), and the clients must trust the server’s certificate. Further, the Web service already has an SSL implementation that can be used. For more information about enabling basic authentication on Internet Information Services (IIS), see [https://go.microsoft.com/fwlink/?LinkId=83822](https://go.microsoft.com/fwlink/?LinkId=83822).  
 
- ![Transport security with basic authentication](../../../../docs/framework/wcf/feature-details/media/securedbyusername.gif "SecuredbyUsername")  
+ ![Screenshot that shows transport security with basic authentication.](./media/transport-security-with-basic-authentication/transport-security-basic-authentication.gif)  
 
 |Characteristic|Description|  
 |--------------------|-----------------|  

diff --git a/docs/framework/wcf/feature-details/troubleshooting-queued-messaging.md b/docs/framework/wcf/feature-details/troubleshooting-queued-messaging.md
@@ -180,7 +180,7 @@ System.ServiceModel.MsmqPoisonMessageException: The transport channel detected a
 
 -   If you are in domain mode, remote transacted receive requires Microsoft Distributed Transaction Coordinator (MSDTC) network access. You can enable this using **Add/Remove Components**.  
 
-     ![Enabling network DTC access](../../../../docs/framework/wcf/feature-details/media/applicationserveraddcomps.jpg "ApplicationServerAddComps")  
+     ![Screenshot that shows enabling network DTC access.](./media/troubleshooting-queued-messaging/enable-distributed-transaction-coordinator-access.jpg)  
 
 -   Check the authentication mode for communicating with the transaction manager. If you are in workgroup mode, "No Authentication Required" must be selected. If you are in domain mode, then "Mutual Authentication Required" must be selected.  
 

diff --git a/...dia/trackingdatathroughetwparticipant.gif → ...g-data-event-tracing-windows-provider.gif b/...dia/trackingdatathroughetwparticipant.gif → ...g-data-event-tracing-windows-provider.gif
diff --git a/docs/framework/windows-workflow-foundation/tracking-participants.md b/docs/framework/windows-workflow-foundation/tracking-participants.md
@@ -54,7 +54,7 @@ Tracking participants are extensibility points that allow a workflow developer t
 
  The following illustration shows the flow of tracking data through the ETW tracking participant. Once the tracking data reaches the ETW session, it can be accessed in a number of ways. One of the most useful ways to access these events is through Event Viewer, a common Windows tool used for viewing logs and traces from applications and services.  
 
- ![The flow of Tracking and ETW Tracking Provider](./media/trackingdatathroughetwparticipant.gif "TrackingDatathroughETWParticipant")  
+ ![Flow of tracking data through the ETW tracking provider.](./media/tracking-participants/tracking-data-event-tracing-windows-provider.gif)  
 
 ## Tracking Participant Event Data  
  A tracking participant serializes tracked event data to an ETW session in the format of one event per tracking record.  An event is identified using an ID within the range of 100 through 199. For definitions of the tracking event records emitted by a tracking participant, see the [Tracking Events Reference](tracking-events-reference.md) topic.  

diff --git a/...ontrols/media/toolbarwithoverflowitem.png → ...olbar-overview/toolbar-overflow-items.png b/...ontrols/media/toolbarwithoverflowitem.png → ...olbar-overview/toolbar-overflow-items.png
diff --git a/...f/controls/media/treeviewillustration.JPG → ...treeview/nested-treeviewitem-controls.jpg b/...f/controls/media/treeviewillustration.JPG → ...treeview/nested-treeviewitem-controls.jpg
diff --git a/docs/framework/wpf/controls/toolbar-overview.md b/docs/framework/wpf/controls/toolbar-overview.md
@@ -22,10 +22,9 @@ ms.assetid: a8edb32c-118d-4f31-b6e6-8899082b504b
 
 <a name="ToolBars_with_Overflow_Items"></a>   
 ## ToolBars with Overflow Items  
- Often <xref:System.Windows.Controls.ToolBar> controls contain more items than can fit into the toolbar's size. When this happens, the <xref:System.Windows.Controls.ToolBar> displays an overflow button. To see the overflow items, a user clicks the overflow button and the items are shown in a pop-up window below the <xref:System.Windows.Controls.ToolBar>. The following graphic shows a <xref:System.Windows.Controls.ToolBar> with overflow items.  
+ Often <xref:System.Windows.Controls.ToolBar> controls contain more items than can fit into the toolbar's size. When this happens, the <xref:System.Windows.Controls.ToolBar> displays an overflow button. To see the overflow items, a user clicks the overflow button and the items are shown in a pop-up window below the <xref:System.Windows.Controls.ToolBar>. The following graphic shows a <xref:System.Windows.Controls.ToolBar> with overflow items:  
 
- ![ToolBar with overflow](./media/toolbarwithoverflowitem.png "ToolbarWithOverflowItem")  
-Toolbar with Overflow Items  
+ ![Screenshot that shows a toolbar with overflow items.](./media/toolbar-overview/toolbar-overflow-items.png)  
 
  You can specify when an item on a toolbar is placed on the overflow panel by setting the <xref:System.Windows.Controls.ToolBar.OverflowMode%2A?displayProperty=nameWithType> attached property to <xref:System.Windows.Controls.OverflowMode.Always?displayProperty=nameWithType>, <xref:System.Windows.Controls.OverflowMode.Never?displayProperty=nameWithType>, or <xref:System.Windows.Controls.OverflowMode.AsNeeded?displayProperty=nameWithType>. The following example specifies that the last four buttons on the toolbar should always be on the overflow panel.  
 

diff --git a/docs/framework/wpf/controls/treeview.md b/docs/framework/wpf/controls/treeview.md
@@ -12,9 +12,9 @@ ms.assetid: 805c235c-0a0e-4e34-8d96-9dc3865cf2df
 # TreeView
 The <xref:System.Windows.Controls.TreeView> control displays information in a hierarchical structure by using collapsible nodes.  
 
- The following illustration is an example of a <xref:System.Windows.Controls.TreeView> control that has nested <xref:System.Windows.Controls.TreeViewItem> controls.  
+ The following illustration is an example of a <xref:System.Windows.Controls.TreeView> control that has nested <xref:System.Windows.Controls.TreeViewItem> controls:  
 
- ![TreeView illustration](./media/treeviewillustration.JPG "TreeViewIllustration")  
+ ![Illustration that shows nested TreeViewItem controls.](./media/treeview/nested-treeviewitem-controls.jpg)  
 
 ## In This Section  
  [TreeView Overview](treeview-overview.md)  

diff --git a/docs/standard/io/media/typesofisolation.gif → ...s-of-isolation/isolated-storage-types.gif b/docs/standard/io/media/typesofisolation.gif → ...s-of-isolation/isolated-storage-types.gif
diff --git a/docs/standard/io/types-of-isolation.md b/docs/standard/io/types-of-isolation.md
@@ -40,10 +40,9 @@ Access to isolated storage is always restricted to the user who created it. To i
 
  Either of these isolations can be combined with a roaming user profile. For more information, see the section [Isolated Storage and Roaming](#Roaming).  
 
- The following illustration demonstrates how stores are isolated in different scopes.  
+ The following illustration demonstrates how stores are isolated in different scopes:  
 
- ![Isolation by user and assembly](../../../docs/standard/io/media/typesofisolation.gif "typesofisolation")  
-Types of isolated storage  
+ ![Diagram that shows isolation by user and assembly.](./media/types-of-isolation/isolated-storage-types.gif)  
 
  Note that except for roaming stores, isolated storage is always implicitly isolated by computer because it uses the storage facilities that are local to a given computer.  
 

diff --git a/...guide/concepts/linq/media/sjltyperels.png → ...erations/linq-query-description-terms.png b/...guide/concepts/linq/media/sjltyperels.png → ...erations/linq-query-description-terms.png
diff --git a/...basic/programming-guide/concepts/linq/type-relationships-in-query-operations.md b/...basic/programming-guide/concepts/linq/type-relationships-in-query-operations.md
@@ -15,8 +15,7 @@ ms.assetid: b5ff4da5-f3fd-4a8e-aaac-1cbf52fa16f6
 # Type Relationships in Query Operations (Visual Basic)
 Variables used in [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] query operations are strongly typed and must be compatible with each other. Strong typing is used in the data source, in the query itself, and in the query execution. The following illustration identifies terms used to describe a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query. For more information about the parts of a query, see [Basic Query Operations (Visual Basic)](../../../../visual-basic/programming-guide/concepts/linq/basic-query-operations.md).  
 
- ![Pseudocode query with elements highlighted.](../../../../visual-basic/programming-guide/concepts/linq/media/sjltyperels.png "SJLtypeRels")  
-Parts of a LINQ query  
+ ![Screenshot showing a pseudocode query with elements highlighted.](./media/type-relationships-in-query-operations/linq-query-description-terms.png)  
 
  The type of the range variable in the query must be compatible with the type of the elements in the data source. The type of the query variable must be compatible with the sequence element defined in the `Select` clause. Finally, the type of the sequence elements also must be compatible with the type of the loop control variable that is used in the `For Each` statement that executes the query. This strong typing facilitates identification of type errors at compile time.