Replace "Windows Communication Foundation (WCF)" token with plain text, part 4 (#5082)

* Replace Windows Communication Foundation (WCF) token, part 1

For #4801

* Add token that was removed by search and replace

Author: ErlendLandro

docs/framework/wcf/feature-details/access-control-mechanisms.md

@@ -21,7 +21,7 @@ ms.workload:
   - "dotnet"
 ---
 # Access Control Mechanisms
-You can control access in several way with [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)]. This topic briefly discusses the various mechanisms and provides suggestions on when to use each; it is intended to help you select the correct mechanism to use. The access technologies are listed in order of complexity. The simplest is the <xref:System.Security.Permissions.PrincipalPermissionAttribute>; the most complex is the Identity Model.  
+You can control access in several way with Windows Communication Foundation (WCF). This topic briefly discusses the various mechanisms and provides suggestions on when to use each; it is intended to help you select the correct mechanism to use. The access technologies are listed in order of complexity. The simplest is the <xref:System.Security.Permissions.PrincipalPermissionAttribute>; the most complex is the Identity Model.  
 
  In addition to these mechanisms, impersonation and delegation with [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] is explained in [Delegation and Impersonation](../../../../docs/framework/wcf/feature-details/delegation-and-impersonation-with-wcf.md).  
 

docs/framework/wcf/feature-details/accessing-services-using-a-client.md

@@ -37,7 +37,7 @@ Client applications must create, configure, and use [!INCLUDE[indigo2](../../../
 -   Initializing channels interactively.  
 
 ### Channel and Session Lifetimes  
- [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] applications includes two categories of channels, datagram and sessionful.  
+ Windows Communication Foundation (WCF) applications includes two categories of channels, datagram and sessionful.  
 
  A *datagram* channel is a channel in which all messages are uncorrelated. With a datagram channel, if an input or output operation fails, the next operation is typically unaffected, and the same channel can be reused. Because of this, datagram channels typically do not fault.  
 

docs/framework/wcf/feature-details/adopting-wcf.md

@@ -18,7 +18,7 @@ ms.workload:
   - "dotnet"
 ---
 # Adopting Windows Communication Foundation
-You can choose to use [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] for new development, while continuing to maintain existing applications developed using ASP.NET. Because [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] is intended to be the most suitable choice for facilitating communication with applications built with the .NET Framework in any scenario, it can serve as a standard tool for solving a wide variety of software communications problems in a way that ASP.NET cannot.  
+You can choose to use Windows Communication Foundation (WCF) for new development, while continuing to maintain existing applications developed using ASP.NET. Because [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] is intended to be the most suitable choice for facilitating communication with applications built with the .NET Framework in any scenario, it can serve as a standard tool for solving a wide variety of software communications problems in a way that ASP.NET cannot.  
 
  New [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] applications can be deployed on the same machines as existing ASP.NET Web services. If the existing ASP.NET Web services use a version of the .NET Framework prior to version 2.0, then you can use the ASP.NET IIS Registration Tool to selectively deploy the .NET Framework 2.0 to IIS applications in which new [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] applications are to be hosted. That tool is documented at [ASP.NET IIS Registration Tool (Aspnet_regiis.exe)](http://go.microsoft.com/fwlink/?LinkId=94687), and has a user interface built into the IIS 6.0 management console.  
 

docs/framework/wcf/feature-details/ajax-integration-and-json-support.md

@@ -20,7 +20,7 @@ ms.workload:
   - "dotnet"
 ---
 # AJAX Integration and JSON Support
-The [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] support for ASP.NET Asynchronous JavaScript and XML (AJAX) and the JavaScript Object Notation (JSON) data format allow [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] services to expose operations to AJAX clients. AJAX clients are Web pages running JavaScript code and accessing these [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] services using HTTP requests. The topics in this section provide information about this support and about how to implement it.  
+The Windows Communication Foundation (WCF) support for ASP.NET Asynchronous JavaScript and XML (AJAX) and the JavaScript Object Notation (JSON) data format allow [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] services to expose operations to AJAX clients. AJAX clients are Web pages running JavaScript code and accessing these [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] services using HTTP requests. The topics in this section provide information about this support and about how to implement it.  
 
  For more information about ASP.NET AJAX and its integration with ASP.NET 2.0, see [ASP.NET AJAX Overview](http://go.microsoft.com/fwlink/?LinkId=96725).  
 

docs/framework/wcf/feature-details/architecture-of-syndication.md

@@ -32,7 +32,7 @@ The Syndication API is designed to provide a format-neutral programming model th
 
  These classes map closely to the constructs defined in the Atom 1.0 specification, although some of the names are different.  
 
- In [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)], syndication feeds are modeled as another type of service operation, one where the return type is one of the derived classes of <xref:System.ServiceModel.Syndication.SyndicationFeedFormatter>. The retrieval of a feed is modeled as a request-response message exchange. A client sends a request to the service and the service responds. The request message is set over an infrastructure protocol (for example, raw HTTP) and the response message contains a payload that consists of a commonly understood syndication format (RSS 2.0 or Atom 1.0). Services that implement these message exchanges are referred to as syndication services.  
+ In Windows Communication Foundation (WCF), syndication feeds are modeled as another type of service operation, one where the return type is one of the derived classes of <xref:System.ServiceModel.Syndication.SyndicationFeedFormatter>. The retrieval of a feed is modeled as a request-response message exchange. A client sends a request to the service and the service responds. The request message is set over an infrastructure protocol (for example, raw HTTP) and the response message contains a payload that consists of a commonly understood syndication format (RSS 2.0 or Atom 1.0). Services that implement these message exchanges are referred to as syndication services.  
 
  The contract for a syndication service consists of a set of operations that returns an instance of the <xref:System.ServiceModel.Syndication.SyndicationFeedFormatter> class. The following example demonstrates an interface declaration for a syndication service.  
 

docs/framework/wcf/feature-details/auditing-security-events.md

@@ -20,7 +20,7 @@ ms.workload:
   - "dotnet"
 ---
 # Auditing Security Events
-Applications created with [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] can log security events (either success, failure, or both) with the auditing feature. The events are written to the Windows system event log and can be examined using the Event Viewer.  
+Applications created with Windows Communication Foundation (WCF) can log security events (either success, failure, or both) with the auditing feature. The events are written to the Windows system event log and can be examined using the Event Viewer.  
 
  Auditing provides a way for an administrator to detect an attack that has already occurred or is in progress. In addition, auditing can help a developer to debug security-related problems. For example, if an error in the configuration of the authorization or checking policy accidentally denies access to an authorized user, a developer can quickly discover and isolate the cause of this error by examining the event log.  
 

docs/framework/wcf/feature-details/authentication-in-wcf.md

@@ -21,7 +21,7 @@ ms.workload:
   - "dotnet"
 ---
 # Authentication in WCF
-The following topics show a number of different mechanisms in [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] that provide authentication, for example, Windows authentication, X.509 certificates, and user name and passwords.  
+The following topics show a number of different mechanisms in Windows Communication Foundation (WCF) that provide authentication, for example, Windows authentication, X.509 certificates, and user name and passwords.  
 
 ## In This Section  
  [How to: Use the ASP.NET Membership Provider](../../../../docs/framework/wcf/feature-details/how-to-use-the-aspnet-membership-provider.md)  

docs/framework/wcf/feature-details/authorization-in-wcf.md

@@ -21,7 +21,7 @@ ms.workload:
   - "dotnet"
 ---
 # Authorization in WCF
-Authorization is the process of controlling access and rights to resources, such as services or files. The topics in this section show you how to perform this basic task in [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] in a variety of ways.  
+Authorization is the process of controlling access and rights to resources, such as services or files. The topics in this section show you how to perform this basic task in Windows Communication Foundation (WCF) in a variety of ways.  
 
 ## In This Section  
  [Access Control Mechanisms](../../../../docs/framework/wcf/feature-details/access-control-mechanisms.md)  

docs/framework/wcf/feature-details/batching-messages-in-a-transaction.md

@@ -23,7 +23,7 @@ ms.workload:
 Queued applications use transactions to ensure correctness and reliable delivery of messages. Transactions, however, are expensive operations and can dramatically reduce message throughput. One way to improve message throughput is to have an application read and process multiple messages within a single transaction. The trade-off is between performance and recovery: as the number of messages in a batch increases, so does the amount of recovery work that required if transactions are rolled back. It is important to note the difference between batching messages in a transaction and sessions. A *session* is a grouping of related messages that are processed by a single application and committed as a single unit. Sessions are generally used when a group of related messages must be processed together. An example of this is an online shopping Web site. *Batches* are used to process multiple, unrelated messages in a way that increases message throughput. For more information about sessions, see [Grouping Queued Messages in a Session](../../../../docs/framework/wcf/feature-details/grouping-queued-messages-in-a-session.md). Messages in a batch are also processed by a single application and committed as a single unit, but there may be no relationship between the messages in the batch. Batching messages in a transaction is an optimization that does not change how the application runs.  
 
 ## Entering Batching Mode  
- The <xref:System.ServiceModel.Description.TransactedBatchingBehavior> endpoint behavior controls batching. Adding this endpoint behavior to a service endpoint tells [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] to batch messages in a transaction. Not all messages require a transaction, so only messages that require a transaction are placed in a batch, and only messages sent from operations marked with `TransactionScopeRequired` = `true` and `TransactionAutoComplete` = `true` are considered for a batch. If all operations on the service contract are marked with `TransactionScopeRequired` = `false` and `TransactionAutoComplete` = `false`, then batching mode is never entered.  
+ The <xref:System.ServiceModel.Description.TransactedBatchingBehavior> endpoint behavior controls batching. Adding this endpoint behavior to a service endpoint tells Windows Communication Foundation (WCF) to batch messages in a transaction. Not all messages require a transaction, so only messages that require a transaction are placed in a batch, and only messages sent from operations marked with `TransactionScopeRequired` = `true` and `TransactionAutoComplete` = `true` are considered for a batch. If all operations on the service contract are marked with `TransactionScopeRequired` = `false` and `TransactionAutoComplete` = `false`, then batching mode is never entered.  
 
 ## Committing a Transaction  
  A batched transaction is committed based on the following:  

docs/framework/wcf/feature-details/best-practices-for-queued-communication.md

@@ -21,7 +21,7 @@ ms.workload:
   - "dotnet"
 ---
 # Best Practices for Queued Communication
-This topic provides recommended practices for queued communication in [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)]. The following sections discuss recommended practices from a scenario perspective.  
+This topic provides recommended practices for queued communication in Windows Communication Foundation (WCF). The following sections discuss recommended practices from a scenario perspective.  
 
 ## Fast, Best-Effort Queued Messaging  
  For scenarios that require separation that queued messaging provides and fast, high-performance messaging with best-effort assurances, use a non-transactional queue and set the <xref:System.ServiceModel.MsmqBindingBase.ExactlyOnce%2A> property to `false`.