Replace "Windows Communication Foundation (WCF)" token with plain text, final part (#5095)

* Replace Windows Communication Foundation (WCF) token

For #4801

* Replace remaining token that wasn't caught by RegEx

Author: ErlendLandro

docs/framework/configure-apps/file-schema/wcf/filter.md

@@ -61,7 +61,7 @@ None.
 
 | Element | Description |
 | ------- | ----------- |
-| [\<routing>](../../../../../docs/framework/configure-apps/file-schema/wcf/routing.md) | A configuration section for defining a set of routing filters, which determine the type of [!INCLUDE[ indigo1](../../../../../includes/indigo1-md.md)]<xref:System.ServiceModel.Dispatcher.MessageFilter> to be used when evaluating incoming messages. |
+| [\<routing>](../../../../../docs/framework/configure-apps/file-schema/wcf/routing.md) | A configuration section for defining a set of routing filters, which determine the type of Windows Communication Foundation (WCF)<xref:System.ServiceModel.Dispatcher.MessageFilter> to be used when evaluating incoming messages. |
 
 ## See also
 

docs/framework/data/wcf/developing-and-deploying-wcf-data-services.md

@@ -47,7 +47,7 @@ This topic provides information about developing and deploying [!INCLUDE[ssAstor
 
 1.  **Local IIS Server**  
 
-     When you create a data service that is an [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] application or [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] Web site that runs on Internet Information Services (IIS), we recommend that you develop and test your data service by using IIS on the local computer. Running the data service on IIS makes it easier to trace HTTP requests during debugging. This also enables you to pre-determine the necessary rights required by IIS to access files, databases, and other resources required by the data service. To run your data service on IIS, you must makes sure that both IIS and [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] are installed and configured correctly and grant access to IIS accounts in the file system and databases. For more information, see [How to: Develop a WCF Data Service Running on IIS](../../../../docs/framework/data/wcf/how-to-develop-a-wcf-data-service-running-on-iis.md).  
+     When you create a data service that is an [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] application or [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] Web site that runs on Internet Information Services (IIS), we recommend that you develop and test your data service by using IIS on the local computer. Running the data service on IIS makes it easier to trace HTTP requests during debugging. This also enables you to pre-determine the necessary rights required by IIS to access files, databases, and other resources required by the data service. To run your data service on IIS, you must makes sure that both IIS and Windows Communication Foundation (WCF) are installed and configured correctly and grant access to IIS accounts in the file system and databases. For more information, see [How to: Develop a WCF Data Service Running on IIS](../../../../docs/framework/data/wcf/how-to-develop-a-wcf-data-service-running-on-iis.md).  
 
     > [!NOTE]
     >  You must run Visual Studio with administrator rights to enable the develop environment to configure the local IIS server.  

docs/framework/data/wcf/streaming-provider-wcf-data-services.md

@@ -88,7 +88,7 @@ A data service can expose large object binary data. This binary data might repre
  For general information about how to create a data service, see [Configuring the Data Service](../../../../docs/framework/data/wcf/configuring-the-data-service-wcf-data-services.md).  
 
 ## Enabling Large Binary Streams in the Hosting Environment  
- When you create a data service in an [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] Web application, [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] is used to provide the HTTP protocol implementation. By default, [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] limits the size of HTTP messages to only 65K bytes. To be able to stream large binary data to and from the data service, you must also configure the Web application to enable large binary files and to use streams for transfer. To do this, add the following in the `<configuration />` element of the application's Web.config file:  
+ When you create a data service in an [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] Web application, Windows Communication Foundation (WCF) is used to provide the HTTP protocol implementation. By default, [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] limits the size of HTTP messages to only 65K bytes. To be able to stream large binary data to and from the data service, you must also configure the Web application to enable large binary files and to use streams for transfer. To do this, add the following in the `<configuration />` element of the application's Web.config file:  
 
 
 

docs/framework/wcf/architecture.md

@@ -22,7 +22,7 @@ ms.workload:
   - "dotnet"
 ---
 # Windows Communication Foundation Architecture
-The following graphic illustrates the major layers of the [!INCLUDE[indigo1](../../../includes/indigo1-md.md)] architecture.  
+The following graphic illustrates the major layers of the Windows Communication Foundation (WCF) architecture.  
 
 ## WCF Architecture  
  ![The WCF Architecture](../../../docs/framework/wcf/media/wcf-architecture.gif "WCF_Architecture")  

docs/framework/wcf/basic-programming-lifecycle.md

@@ -20,7 +20,7 @@ ms.workload:
   - "dotnet"
 ---
 # Basic Programming Lifecycle
-[!INCLUDE[indigo1](../../../includes/indigo1-md.md)] enables applications to communicate whether they are on the same computer, across the Internet, or on different application platforms. This topic outlines the tasks that are required to build a [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] application. For a working sample application, see [Getting Started Tutorial](../../../docs/framework/wcf/getting-started-tutorial.md).  
+Windows Communication Foundation (WCF) enables applications to communicate whether they are on the same computer, across the Internet, or on different application platforms. This topic outlines the tasks that are required to build a [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] application. For a working sample application, see [Getting Started Tutorial](../../../docs/framework/wcf/getting-started-tutorial.md).  
 
 ## The Basic Tasks  
  The basic tasks to perform are, in order:  

docs/framework/wcf/basic-wcf-programming.md

@@ -24,7 +24,7 @@ ms.workload:
   - "dotnet"
 ---
 # Basic WCF Programming
-This section presents the fundamentals for creating [!INCLUDE[indigo1](../../../includes/indigo1-md.md)] applications.  
+This section presents the fundamentals for creating Windows Communication Foundation (WCF) applications.  
 
 ## In This Section  
  [Basic Programming Lifecycle](../../../docs/framework/wcf/basic-programming-lifecycle.md)  

docs/framework/wcf/best-practices-data-contract-versioning.md

@@ -26,7 +26,7 @@ ms.workload:
 This topic lists the best practices for creating data contracts that can evolve easily over time. For more information about data contracts, see the topics in [Using Data Contracts](../../../docs/framework/wcf/feature-details/using-data-contracts.md).  
 
 ## Note on Schema Validation  
- In discussing data contract versioning, it is important to note that the data contract schema exported by [!INCLUDE[indigo1](../../../includes/indigo1-md.md)] does not have any versioning support, other than the fact that elements are marked as optional by default.  
+ In discussing data contract versioning, it is important to note that the data contract schema exported by Windows Communication Foundation (WCF) does not have any versioning support, other than the fact that elements are marked as optional by default.  
 
  This means that even the most common versioning scenario, such as adding a new data member, cannot be implemented in a way that is seamless with regard to a given schema. The newer versions of a data contract (with a new data member, for example) do not validate using the old schema.  
 

docs/framework/wcf/bindings-overview.md

@@ -20,7 +20,7 @@ ms.workload:
   - "dotnet"
 ---
 # Windows Communication Foundation Bindings Overview
-Bindings are objects that are used to specify the communication details that are required to connect to the endpoint of a [!INCLUDE[indigo1](../../../includes/indigo1-md.md)] service. Each endpoint in a [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] service requires a binding to be well-specified. This topic outlines the types of communication details that the bindings define, the elements of a binding, what bindings are included in [!INCLUDE[indigo2](../../../includes/indigo2-md.md)], and how a binding can be specified for an endpoint.  
+Bindings are objects that are used to specify the communication details that are required to connect to the endpoint of a Windows Communication Foundation (WCF) service. Each endpoint in a [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] service requires a binding to be well-specified. This topic outlines the types of communication details that the bindings define, the elements of a binding, what bindings are included in [!INCLUDE[indigo2](../../../includes/indigo2-md.md)], and how a binding can be specified for an endpoint.  
 
 ## What a Binding Defines  
  The information in a binding can be very basic, or very complex. The most basic binding specifies only the transport protocol (such as HTTP) that must be used to connect to the endpoint. More generally, the information a binding contains about how to connect to an endpoint falls into one of the following categories.  

docs/framework/wcf/bindings.md

@@ -20,7 +20,7 @@ ms.workload:
   - "dotnet"
 ---
 # Windows Communication Foundation Bindings
-Bindings specify how a [!INCLUDE[indigo1](../../../includes/indigo1-md.md)] service endpoint communicates with other endpoints. At its most basic, a binding must specify the transport (for example, HTTP or TCP) to use. You can also set other characteristics, such as security and transaction support, through bindings.  
+Bindings specify how a Windows Communication Foundation (WCF) service endpoint communicates with other endpoints. At its most basic, a binding must specify the transport (for example, HTTP or TCP) to use. You can also set other characteristics, such as security and transaction support, through bindings.  
 
 ## In This Section  
  [WCF Bindings Overview](../../../docs/framework/wcf/bindings-overview.md)  

docs/framework/wcf/building-clients.md

@@ -21,7 +21,7 @@ ms.workload:
   - "dotnet"
 ---
 # Building Clients
-The topics in this section demonstrate how to create and use a [!INCLUDE[indigo1](../../../includes/indigo1-md.md)] client.  
+The topics in this section demonstrate how to create and use a Windows Communication Foundation (WCF) client.  
 
 ## In This Section  
  [WCF Client Overview](../../../docs/framework/wcf/wcf-client-overview.md)