Replace WCF token (#5152)

For #4801

Author: ErlendLandro

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

@@ -70,7 +70,7 @@ This topic provides information about developing and deploying [!INCLUDE[ssAstor
 
 -   An HTTP inspection program can be very helpful when debugging a data service by enabling you to inspect the contents of request and response messages. Any network packet analyzer that can display raw packets can be used to inspect HTTP requests to and responses from the data service.  
 
--   When debugging a data service, you may may want to get more information about an error from the data service than during regular operation. You can get additional error information from the data service by setting the <xref:System.Data.Services.DataServiceConfiguration.UseVerboseErrors%2A> property in the <xref:System.Data.Services.DataServiceConfiguration> to `true` and by setting the <xref:System.ServiceModel.Description.ServiceDebugBehavior.IncludeExceptionDetailInFaults%2A> property of the <xref:System.ServiceModel.Description.ServiceDebugBehavior> attribute on the data service class to `true`. For more information, see the post [Debugging WCF Data Services](http://go.microsoft.com/fwlink/?LinkId=201868). You can also enable tracing in [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] to view exceptions raised in the HTTP messaging layer. For more information, see [Configuring Tracing](../../../../docs/framework/wcf/diagnostics/tracing/configuring-tracing.md).  
+-   When debugging a data service, you may may want to get more information about an error from the data service than during regular operation. You can get additional error information from the data service by setting the <xref:System.Data.Services.DataServiceConfiguration.UseVerboseErrors%2A> property in the <xref:System.Data.Services.DataServiceConfiguration> to `true` and by setting the <xref:System.ServiceModel.Description.ServiceDebugBehavior.IncludeExceptionDetailInFaults%2A> property of the <xref:System.ServiceModel.Description.ServiceDebugBehavior> attribute on the data service class to `true`. For more information, see the post [Debugging WCF Data Services](http://go.microsoft.com/fwlink/?LinkId=201868). You can also enable tracing in WCF to view exceptions raised in the HTTP messaging layer. For more information, see [Configuring Tracing](../../../../docs/framework/wcf/diagnostics/tracing/configuring-tracing.md).  
 
 -   A data service is usually developed as an [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] application project, but you can also create you data service as an [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] Web site project in Visual Studio. For information about the differences between the two types of projects, see [NIB: Web Application Projects versus Web Site Projects in Visual Studio](http://msdn.microsoft.com/library/2861815e-f5a2-4378-a2f8-b8a86dc012f5).  
 
@@ -111,7 +111,7 @@ This topic provides information about developing and deploying [!INCLUDE[ssAstor
 
 -   When you deploy a data service that uses the [!INCLUDE[adonet_ef](../../../../includes/adonet-ef-md.md)] provider to access a SQL Server database, you might also have to propagate data structures, data, or both with your data service deployment. Visual Studio can automatically create scripts (.sql files) to do this in the destination database, and these scripts can be included in the Web deployment package of an [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] application. For more information, see [NIB: How to: Deploy a Database With a Web Application Project](http://msdn.microsoft.com/library/683b33f1-8a3d-45cf-af6e-61ab50fc518b). For an [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] Web site, you can do this by using the **Database Publishing Wizard** in Visual Studio. For more information, see [Deploying a Database by Using the Database Publishing Wizard](http://msdn.microsoft.com/library/1e3682e7-8b57-4da6-a393-af9640ccf8b7).  
 
--   Because [!INCLUDE[ssAstoria](../../../../includes/ssastoria-md.md)] includes a basic [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] implementation, you can use Windows Server AppFabric to monitor a data service deployed to IIS running on Windows Server. For more information about using Windows Server AppFabric to monitor a data service, see the post [Tracking WCF Data Services with Windows Server AppFabric](http://go.microsoft.com/fwlink/?LinkID=202005).  
+-   Because [!INCLUDE[ssAstoria](../../../../includes/ssastoria-md.md)] includes a basic WCF implementation, you can use Windows Server AppFabric to monitor a data service deployed to IIS running on Windows Server. For more information about using Windows Server AppFabric to monitor a data service, see the post [Tracking WCF Data Services with Windows Server AppFabric](http://go.microsoft.com/fwlink/?LinkID=202005).  
 
 ## See Also  
  [Hosting the Data Service](../../../../docs/framework/data/wcf/hosting-the-data-service-wcf-data-services.md)  

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

@@ -74,12 +74,12 @@ 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, 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:  
+ 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, WCF 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:  
 
 
 
 > [!NOTE]
->  You must use a <xref:System.ServiceModel.TransferMode.Streamed?displayProperty=nameWithType> transfer mode to ensure that the binary data in both the request and response messages are streamed and not buffered by [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)].  
+>  You must use a <xref:System.ServiceModel.TransferMode.Streamed?displayProperty=nameWithType> transfer mode to ensure that the binary data in both the request and response messages are streamed and not buffered by WCF.  
   
  For more information, see [Streaming Message Transfer](../../../../docs/framework/wcf/feature-details/streaming-message-transfer.md) and [Transport Quotas](../../../../docs/framework/wcf/feature-details/transport-quotas.md).  
 

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

@@ -9,13 +9,13 @@ helpviewer_keywords:
 ms.assetid: d780af9f-73c5-42db-9e52-077a5e4de7fe
 ---
 # Accessing Services Using a WCF Client
-After you create a service, the next step is to create a [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client proxy. A client application uses the [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client proxy to communicate with the service. Client applications usually import a service's metadata to generate [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client code that can be used to invoke the service.  
+After you create a service, the next step is to create a WCF client proxy. A client application uses the WCF client proxy to communicate with the service. Client applications usually import a service's metadata to generate WCF client code that can be used to invoke the service.  
 
- The basic steps for creating a [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client include the following:  
+ The basic steps for creating a WCF client include the following:  
 
 1.  Compile the service code.  
 
-2.  Generate the [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client proxy.  
+2.  Generate the WCF client proxy.  
 
 3.  Instantiate the WCF client proxy.  
 
@@ -34,7 +34,7 @@ Svcutil.exe <service's Metadata Exchange (MEX) address or HTTP GET address>
 Svcutil.exe <list of WSDL and XSD files on file system>  
 ```  
 
- The result is a code file that contains [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client code that the client application can use to invoke the service.  
+ The result is a code file that contains WCF client code that the client application can use to invoke the service.  
 
  You can also use the tool to generate configuration files.  
 
@@ -74,7 +74,7 @@ Public Interface ICalculator
 End Interface
 ```
 
- The ServiceModel Metadata utility tool and Add Service Reference in Visual Studio generates the following [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client class. The class inherits from the generic <xref:System.ServiceModel.ClientBase%601> class and implements the `ICalculator` interface. The tool also generates the `ICalculator` interface (not shown here).  
+ The ServiceModel Metadata utility tool and Add Service Reference in Visual Studio generates the following WCF client class. The class inherits from the generic <xref:System.ServiceModel.ClientBase%601> class and implements the `ICalculator` interface. The tool also generates the `ICalculator` interface (not shown here).  
 
 ```csharp
 public partial class CalculatorClient : System.ServiceModel.ClientBase<ICalculator>, ICalculator
@@ -142,7 +142,7 @@ End Class
 ```
 
 ## Using the WCF Client  
- To use the [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client, create an instance of the [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client, and then call its methods, as shown in the following code.  
+ To use the WCF client, create an instance of the WCF client, and then call its methods, as shown in the following code.  
 
 ```csharp
 // Create a client object with the given client endpoint configuration.
@@ -167,7 +167,7 @@ Console.WriteLine("Add({0},{1}) = {2}", value1, value2, result)
 ```
 
 ## Debugging Exceptions Thrown by a Client  
- Many exceptions thrown by a [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client are caused by an exception on the service. Some examples of this are:  
+ Many exceptions thrown by a WCF client are caused by an exception on the service. Some examples of this are:  
 
 -   <xref:System.Net.Sockets.SocketException>: An existing connection was forcibly closed by the remote host.  
 

docs/framework/wcf/architecture.md

@@ -19,7 +19,7 @@ The following graphic illustrates the major layers of the Windows Communication
  Policies and bindings stipulate the conditions required to communicate with a service.  For example, the binding must (at a minimum) specify the transport used (for example, HTTP or TCP), and an encoding. Policies include security requirements and other conditions that must be met to communicate with a service.  
 
 ### Service Runtime  
- The service runtime layer contains the behaviors that occur only during the actual operation of the service, that is, the runtime behaviors of the service. Throttling controls how many messages are processed, which can be varied if the demand for the service grows to a preset limit. An error behavior specifies what occurs when an internal error occurs on the service, for example, by controlling what information is communicated to the client. (Too much information can give a malicious user an advantage in mounting an attack.) Metadata behavior governs how and whether metadata is made available to the outside world. Instance behavior specifies how many instances of the service can be run (for example, a singleton specifies only one instance to process all messages). Transaction behavior enables the rollback of transacted operations if a failure occurs. Dispatch behavior is the control of how a message is processed by the [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] infrastructure.  
+ The service runtime layer contains the behaviors that occur only during the actual operation of the service, that is, the runtime behaviors of the service. Throttling controls how many messages are processed, which can be varied if the demand for the service grows to a preset limit. An error behavior specifies what occurs when an internal error occurs on the service, for example, by controlling what information is communicated to the client. (Too much information can give a malicious user an advantage in mounting an attack.) Metadata behavior governs how and whether metadata is made available to the outside world. Instance behavior specifies how many instances of the service can be run (for example, a singleton specifies only one instance to process all messages). Transaction behavior enables the rollback of transacted operations if a failure occurs. Dispatch behavior is the control of how a message is processed by the WCF infrastructure.  
 
  Extensibility enables customization of runtime processes. For example, message inspection is the facility to inspect parts of a message, and parameter filtering enables preset actions to occur based on filters acting on message headers.  
 
@@ -37,7 +37,7 @@ The following graphic illustrates the major layers of the Windows Communication
 ### Hosting and Activation  
  In its final form, a service is a program. Like other programs, a service must be run in an executable. This is known as a *self-hosted* service.  
 
- Services can also be *hosted*, or run in an executable managed by an external agent, such as IIS or Windows Activation Service (WAS). WAS enables [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] applications to be activated automatically when deployed on a computer running WAS. Services can also be manually run as executables (.exe files). A service can also be run automatically as a Windows service. COM+ components can also be hosted as [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] services.  
+ Services can also be *hosted*, or run in an executable managed by an external agent, such as IIS or Windows Activation Service (WAS). WAS enables WCF applications to be activated automatically when deployed on a computer running WAS. Services can also be manually run as executables (.exe files). A service can also be run automatically as a Windows service. COM+ components can also be hosted as WCF services.  
 
 ## See Also  
  [What Is Windows Communication Foundation](../../../docs/framework/wcf/whats-wcf.md)  

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

@@ -6,7 +6,7 @@ helpviewer_keywords:
 ms.assetid: 7cf21bfe-23bd-46aa-8033-609f851dbf76
 ---
 # Basic Programming Lifecycle
-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).  
+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 WCF 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

@@ -14,22 +14,22 @@ This section presents the fundamentals for creating Windows Communication Founda
 
 ## In This Section  
  [Basic Programming Lifecycle](../../../docs/framework/wcf/basic-programming-lifecycle.md)  
- Describes the lifecycle of designing, building, and deploying [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] service and client applications.  
+ Describes the lifecycle of designing, building, and deploying WCF service and client applications.  
 
  [Designing and Implementing Services](../../../docs/framework/wcf/designing-and-implementing-services.md)  
  Describes how to design and implement a service contract, choose a message exchange pattern, specify a fault contract, and other basic aspects of services.  
 
  [Configuring Services](../../../docs/framework/wcf/configuring-services.md)  
- Describes how to configure a [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] service to support the contract requirements, customize local runtime behavior, and indicate the address to publish the service.  
+ Describes how to configure a WCF service to support the contract requirements, customize local runtime behavior, and indicate the address to publish the service.  
 
  [Hosting Services](../../../docs/framework/wcf/hosting-services.md)  
  Describes the basics of hosting services in an application.  
 
  [Building Clients](../../../docs/framework/wcf/building-clients.md)  
- Describes how to obtain metadata from services, convert that into [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client code, handle security issues, and build, configure, and host an [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] client.  
+ Describes how to obtain metadata from services, convert that into WCF client code, handle security issues, and build, configure, and host an WCF client.  
 
  [Introduction to Extensibility](../../../docs/framework/wcf/introduction-to-extensibility.md)  
- Describes how to extend [!INCLUDE[indigo2](../../../includes/indigo2-md.md)] to create custom solutions.  
+ Describes how to extend WCF to create custom solutions.  
 
  [WCF Troubleshooting Quickstart](../../../docs/framework/wcf/wcf-troubleshooting-quickstart.md)  
  Describes some of the most common issues that occur, what you can do to solve them, and where to locate more information about the issue.