SEOImages: User Story 1463880, Part 41 (#11490)

* SEO image updates.

Author: damabe

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.  

docs/csharp/programming-guide/types/media/valuetypescts.png renamed to docs/csharp/programming-guide/types/media/index/value-reference-types-common-type-system.png

@@ -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.  
 

docs/framework/wcf/feature-details/media/transactionmanagers.gif renamed to docs/framework/wcf/feature-details/media/transaction-protocols-version-1-0/transaction-managers-flow.gif

@@ -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.  
 

docs/framework/wcf/feature-details/media/transaction-protocols/transaction-managers-flow.gif

@@ -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|  
 |--------------------|-----------------|  

docs/framework/wcf/feature-details/media/securedbyusername.gif renamed to docs/framework/wcf/feature-details/media/transport-security-with-basic-authentication/transport-security-basic-authentication.gif

@@ -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.