Replace WCF token, part 1 (#5096)

For #4801

Author: ErlendLandro

docs/framework/configure-apps/file-schema/wcf-directive/index.md

@@ -4,7 +4,7 @@ ms.date: "03/30/2017"
 ms.assetid: e471b042-d5e3-491c-bc81-758655016a3a
 ---
 # WCF Directive Syntax
-Specifies settings used by the Windows Communication Foundation (WCF) directives in the .svc files to direct the compilers. Each directive can contain one or more attributes (paired with values) that are specific to that directive. [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] has only the [@ServiceHost](../../../../../docs/framework/configure-apps/file-schema/wcf-directive/servicehost.md) directive.  
+Specifies settings used by the Windows Communication Foundation (WCF) directives in the .svc files to direct the compilers. Each directive can contain one or more attributes (paired with values) that are specific to that directive. WCF has only the [@ServiceHost](../../../../../docs/framework/configure-apps/file-schema/wcf-directive/servicehost.md) directive.  
 
 ## In This Section  
  [@ServiceHost](../../../../../docs/framework/configure-apps/file-schema/wcf-directive/servicehost.md)  

docs/framework/configure-apps/file-schema/wcf-directive/servicehost.md

@@ -26,7 +26,7 @@ CodeBehind = "CodeBehind"%>
  The CLR type name of the service host factory used to instantiate the service host. This attribute is optional. If unspecified, the default <xref:System.ServiceModel.Activation.ServiceHostFactory> is used, which returns an instance of <xref:System.ServiceModel.ServiceHost>.  
 
 #### Debug  
- Indicates whether the Windows Communication Foundation (WCF) service should be compiled with debug symbols. `true` if the [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] service should be compiled with debug symbols; otherwise, `false`.  
+ Indicates whether the Windows Communication Foundation (WCF) service should be compiled with debug symbols. `true` if the WCF service should be compiled with debug symbols; otherwise, `false`.  
 
 #### Language  
  Specifies the language used when compiling all the inline code within file (.svc). The values can represent any .NET-supported language, including C#, VB, and JS, which refer to C#, Visual Basic .NET, and JScript .NET, respectively. This attribute is optional.  

docs/framework/configure-apps/file-schema/wcf/add-of-allowaccounts.md

@@ -4,7 +4,7 @@ ms.date: "03/30/2017"
 ms.assetid: 763c7b1f-e7b0-4d99-a42c-4506fcb8da00
 ---
 # <add> of <allowAccounts>
-Specifies a user account for processes that host [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] services, and are granted connection access to the sharing service.  
+Specifies a user account for processes that host WCF services, and are granted connection access to the sharing service.  
 
  \<system.serviceModel.activation>  
 
@@ -32,7 +32,7 @@ Specifies a user account for processes that host [!INCLUDE[indigo2](../../../../
 
 |Element|Description|  
 |-------------|-----------------|  
-|[\<allowAccounts>](../../../../../docs/framework/configure-apps/file-schema/wcf/allowaccounts.md)|A collection of configuration elements that contain a `securityIdentifier` attribute to specify user accounts for processes that host [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] services, and are granted connection access to the sharing service.|  
+|[\<allowAccounts>](../../../../../docs/framework/configure-apps/file-schema/wcf/allowaccounts.md)|A collection of configuration elements that contain a `securityIdentifier` attribute to specify user accounts for processes that host WCF services, and are granted connection access to the sharing service.|  
 
 ## Example  
  The following configuration example adds the five default identifiers for user accounts to this collection.  

docs/framework/configure-apps/file-schema/wcf/add-of-baseaddressprefixfilter.md

@@ -44,7 +44,7 @@ Represents a configuration element that specifies a pass-through filter, which p
 
  IIS Web sites are containers for virtual applications which contain virtual directories. The application in a site can be accessed through one or more IIS binding. IIS bindings provide two pieces of information: binding protocol and binding information. Binding protocol (for example, HTTP) defines the scheme over which communication occurs, and binding information (for example, IP Address, Port, Hostheader) contains data used to access the site.  
 
- IIS supports specifying multiple IIS bindings for each site, which results in multiple base addresses for each scheme. Because a [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] service hosted under a site allows binding to only one base address for each scheme, you can use the prefix filter feature to pick the required base address of the hosted service. The incoming base addresses, supplied by IIS, are filtered based on the optional prefix list filter.  
+ IIS supports specifying multiple IIS bindings for each site, which results in multiple base addresses for each scheme. Because a WCF service hosted under a site allows binding to only one base address for each scheme, you can use the prefix filter feature to pick the required base address of the hosted service. The incoming base addresses, supplied by IIS, are filtered based on the optional prefix list filter.  
 
  For example, your site can contain the following base addresses.  
 

docs/framework/configure-apps/file-schema/wcf/add-of-protocolmapping.md

@@ -4,7 +4,7 @@ ms.date: "03/30/2017"
 ms.assetid: 08e62249-1641-41d1-91b1-66d7b46244e4
 ---
 # <add> of <protocolMapping>
-Represents a default protocol mapping between a transport protocol scheme (e.g., http, net.tcp, net.pipe, etc.) and a Windows Communication Foundation (WCF) binding. When creating default endpoints at runtime, [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] looks at the configured mappings and decides on which binding to use for a particular based address.  
+Represents a default protocol mapping between a transport protocol scheme (e.g., http, net.tcp, net.pipe, etc.) and a Windows Communication Foundation (WCF) binding. When creating default endpoints at runtime, WCF looks at the configured mappings and decides on which binding to use for a particular based address.  
 
  \<system.serviceModel>  
 \<protocolMapping>  

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

@@ -26,7 +26,7 @@ Contains a collection of configuration elements that specify user accounts for p
 
 |Attribute|Description|  
 |---------------|-----------------|  
-|[\<add>](../../../../../docs/framework/configure-apps/file-schema/wcf/add-of-allowaccounts.md)|Adds a user account for processes that host [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] services, and are granted connection access to the sharing service|  
+|[\<add>](../../../../../docs/framework/configure-apps/file-schema/wcf/add-of-allowaccounts.md)|Adds a user account for processes that host WCF services, and are granted connection access to the sharing service|  
 
 ### Parent Elements  
 

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

@@ -4,7 +4,7 @@ ms.date: "03/30/2017"
 ms.assetid: 034b7c69-a770-4502-8cef-38007bbcd025
 ---
 # <announcementEndpoint>
-This configuration element defines a standard endpoint with a fixed announcement contract. A service can optionally announce its availability by sending an online and offline announcement message when it is opened or closed respectively. A Windows Communication Foundation (WCF) service specifies the announcement endpoints in the [\<serviceDiscovery>](../../../../../docs/framework/configure-apps/file-schema/wcf/servicediscovery.md) element and uses the AnnouncementClient to perform the announcements. A client wishing to listen for the announcement from other service is actually acting as a [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] service; thus you have to configure the announcement endpoints for that client in the [\<services>](../../../../../docs/framework/configure-apps/file-schema/wcf/services.md) section.  
+This configuration element defines a standard endpoint with a fixed announcement contract. A service can optionally announce its availability by sending an online and offline announcement message when it is opened or closed respectively. A Windows Communication Foundation (WCF) service specifies the announcement endpoints in the [\<serviceDiscovery>](../../../../../docs/framework/configure-apps/file-schema/wcf/servicediscovery.md) element and uses the AnnouncementClient to perform the announcements. A client wishing to listen for the announcement from other service is actually acting as a WCF service; thus you have to configure the announcement endpoints for that client in the [\<services>](../../../../../docs/framework/configure-apps/file-schema/wcf/services.md) section.  
 
 \<system.ServiceModel>  
 \<standardEndpoints>  

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

@@ -45,7 +45,7 @@ Represents a collection of configuration elements that specify pass through filt
 
  IIS Web sites are containers for virtual applications which contain virtual directories. The application in a site can be accessed through one or more IIS bindings. IIS bindings provide two pieces of information: binding protocol and binding information. Binding protocol (for example, HTTP) defines the scheme over which communication occurs, and binding information (for example, IP Address, Port, Hostheader) contains data used to access the site.  
 
- IIS supports specifying multiple IIS bindings for each site, which results in multiple base addresses for each scheme. Because a [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] service hosted under a site allows binding to only one base address for each scheme, you can use the prefix filter feature to pick the required base address of the hosted service. The incoming base addresses, supplied by IIS, are filtered based on the optional prefix list filter.  
+ IIS supports specifying multiple IIS bindings for each site, which results in multiple base addresses for each scheme. Because a WCF service hosted under a site allows binding to only one base address for each scheme, you can use the prefix filter feature to pick the required base address of the hosted service. The incoming base addresses, supplied by IIS, are filtered based on the optional prefix list filter.  
 
  For example, your site can contain the following base addresses.  
 

docs/framework/configure-apps/file-schema/wcf/behavior-of-endpointbehaviors.md

@@ -47,7 +47,7 @@ The `behavior` element contains a collection of settings for the behavior of an
 |[\<soapProcessing>](../../../../../docs/framework/configure-apps/file-schema/wcf/soapprocessing.md)|Defines the client endpoint behavior used to marshal messages between different binding types and message versions.|  
 |[\<synchronousReceive>](../../../../../docs/framework/configure-apps/file-schema/wcf/synchronousreceive-element.md)|Specifies run-time behavior for receiving messages in either a service or client application. It does not have any attributes or child elements.|  
 |[\<transactedBatching>](../../../../../docs/framework/configure-apps/file-schema/wcf/transactedbatching.md)|Specifies whether transaction batching is supported for receive operations.|  
-|[\<webHttp>](../../../../../docs/framework/configure-apps/file-schema/wcf/webhttp.md)|Specifies the WebHttpBehavior on an endpoint through configuration. This behavior, when used in conjunction with the \<webHttpBinding> standard binding, enables the Web programming model for a [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] service.|  
+|[\<webHttp>](../../../../../docs/framework/configure-apps/file-schema/wcf/webhttp.md)|Specifies the WebHttpBehavior on an endpoint through configuration. This behavior, when used in conjunction with the \<webHttpBinding> standard binding, enables the Web programming model for a WCF service.|  
 
 ### Parent Elements  
 

docs/framework/configure-apps/file-schema/wcf/behavior-of-servicebehaviors.md

@@ -49,9 +49,9 @@ The `behavior` element contains a collection of settings for the behavior of a s
 |[\<serviceDiscovery>](../../../../../docs/framework/configure-apps/file-schema/wcf/servicediscovery.md)|Specifies the discoverability of service endpoints.|  
 |[\<serviceMetadata>](../../../../../docs/framework/configure-apps/file-schema/wcf/servicemetadata.md)|Specifies the publication of service metadata and associated information.|  
 |[\<serviceSecurityAudit>](../../../../../docs/framework/configure-apps/file-schema/wcf/servicesecurityaudit.md)|Specifies settings that enable auditing of security events during service operations.|  
-|[\<serviceThrottling>](../../../../../docs/framework/configure-apps/file-schema/wcf/servicethrottling.md)|Specifies the throttling mechanism of a [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] service.|  
+|[\<serviceThrottling>](../../../../../docs/framework/configure-apps/file-schema/wcf/servicethrottling.md)|Specifies the throttling mechanism of a WCF service.|  
 |[\<serviceTimeouts>](../../../../../docs/framework/configure-apps/file-schema/wcf/servicetimeouts.md)|Specifies the timeout for a service.|  
-|[\<workflowRuntime>](../../../../../docs/framework/configure-apps/file-schema/wcf/workflowruntime.md)|Specifies settings for an instance of WorkflowRuntime for hosting workflow-based [!INCLUDE[indigo2](../../../../../includes/indigo2-md.md)] services.|  
+|[\<workflowRuntime>](../../../../../docs/framework/configure-apps/file-schema/wcf/workflowruntime.md)|Specifies settings for an instance of WorkflowRuntime for hosting workflow-based WCF services.|  
 |[\<useRequestHeadersForMetadataAddress>](../../../../../docs/framework/configure-apps/file-schema/wcf/userequestheadersformetadataaddress.md)|Enables the retrieval of metadata address information from the request message headers.|  
 
 ### Parent Elements