Replace Windows Communication Foundation (WCF) token (#5053)

For #4801

Author: ErlendLandro

docs/framework/xaml-services/default-xaml-schema-context-and-wpf-xaml-schema-context.md

@@ -65,7 +65,7 @@ A XAML schema context is a conceptual entity that qualifies how a XAML productio
     -   If the name is unqualified in the mapping, call <xref:System.Reflection.Assembly.LoadWithPartialName%2A?displayProperty=nameWithType>.  
 
 #### XamlBuildTask  
- `XamlBuildTask` is used for [!INCLUDE[vsindigo](../../../includes/vsindigo-md.md)] and Windows Workflow Foundation.  
+ `XamlBuildTask` is used for Windows Communication Foundation (WCF) and Windows Workflow Foundation.  
 
  Note that assembly references through `XamlBuildTask` are always fully qualified.  
 

docs/framework/xaml-services/index.md

@@ -44,7 +44,7 @@ This topic describes the capabilities of a technology set known as .NET Framewor
  If you are looking for introductory material on XAML as a language, you might try [XAML Overview (WPF)](../../../docs/framework/wpf/advanced/xaml-overview-wpf.md). That topic discusses XAML for an audience that is new both to [!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)] and also to using XAML markup and XAML language features. Another useful document is the introductory material in the [XAML language specification](http://go.microsoft.com/fwlink/?LinkId=114525).  
 
 ## .NET Framework XAML Services and System.Xaml in the .NET Architecture  
- In previous versions of [!INCLUDE[TLA#tla_netframewk](../../../includes/tlasharptla-netframewk-md.md)], support for XAML language features was implemented by frameworks that built on [!INCLUDE[TLA#tla_netframewk](../../../includes/tlasharptla-netframewk-md.md)] ([!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)], Windows Workflow Foundation and [!INCLUDE[vsindigo](../../../includes/vsindigo-md.md)]), and therefore varied in its behavior and the API used depending on which specific framework you were using. This included the XAML parser and its object graph creation mechanism, XAML language intrinsics, serialization support, and so on.  
+ In previous versions of [!INCLUDE[TLA#tla_netframewk](../../../includes/tlasharptla-netframewk-md.md)], support for XAML language features was implemented by frameworks that built on [!INCLUDE[TLA#tla_netframewk](../../../includes/tlasharptla-netframewk-md.md)] ([!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)], Windows Workflow Foundation and Windows Communication Foundation (WCF)), and therefore varied in its behavior and the API used depending on which specific framework you were using. This included the XAML parser and its object graph creation mechanism, XAML language intrinsics, serialization support, and so on.  
 
  In [!INCLUDE[net_v40_long](../../../includes/net-v40-long-md.md)], .NET Framework XAML Services and the System.Xaml assembly define much of what is needed for supporting XAML language features. This includes base classes for XAML readers and XAML writers. The most important feature added to .NET Framework XAML Services that was not present in any of the framework-specific XAML implementations is a type system representation for XAML. The type system representation presents XAML in an object-oriented way that centers on XAML capabilities without taking dependencies on specific capabilities of frameworks.  
 

docs/framework/xaml-services/type-converters-and-markup-extensions-for-xaml.md

@@ -40,7 +40,7 @@ Type converters and markup extensions are two techniques that XAML type systems
 
 <a name="type_converters"></a>   
 ## Type Converters  
- In the .NET Framework XAML Services definition, type converters are classes that derive from the CLR <xref:System.ComponentModel.TypeConverter> class. <xref:System.ComponentModel.TypeConverter> is a class that was in the [!INCLUDE[TLA#tla_netframewk](../../../includes/tlasharptla-netframewk-md.md)] before XAML existed. Its original purpose was to support property windows and similar text-based editing metaphors for [!INCLUDE[TLA2#tla_ide](../../../includes/tla2sharptla-ide-md.md)] properties. The introduction of XAML to .NET Framework uses <xref:System.ComponentModel.TypeConverter> to convert a text syntax (as found in an attribute value or a XAML value node) into an object. <xref:System.ComponentModel.TypeConverter> can also be used to serialize an object value to text syntax. <xref:System.ComponentModel.TypeConverter> was also used in previous framework-specific XAML implementations in [!INCLUDE[TLA#tla_wpf](../../../includes/tlasharptla-wpf-md.md)] and [!INCLUDE[vsindigo](../../../includes/vsindigo-md.md)]. For more information about the <xref:System.ComponentModel.TypeConverter> in XAML, see [Type Converters for XAML Overview](../../../docs/framework/xaml-services/type-converters-for-xaml-overview.md).  
+ In the .NET Framework XAML Services definition, type converters are classes that derive from the CLR <xref:System.ComponentModel.TypeConverter> class. <xref:System.ComponentModel.TypeConverter> is a class that was in the [!INCLUDE[TLA#tla_netframewk](../../../includes/tlasharptla-netframewk-md.md)] before XAML existed. Its original purpose was to support property windows and similar text-based editing metaphors for [!INCLUDE[TLA2#tla_ide](../../../includes/tla2sharptla-ide-md.md)] properties. The introduction of XAML to .NET Framework uses <xref:System.ComponentModel.TypeConverter> to convert a text syntax (as found in an attribute value or a XAML value node) into an object. <xref:System.ComponentModel.TypeConverter> can also be used to serialize an object value to text syntax. <xref:System.ComponentModel.TypeConverter> was also used in previous framework-specific XAML implementations in [!INCLUDE[TLA#tla_wpf](../../../includes/tlasharptla-wpf-md.md)] and Windows Communication Foundation (WCF). For more information about the <xref:System.ComponentModel.TypeConverter> in XAML, see [Type Converters for XAML Overview](../../../docs/framework/xaml-services/type-converters-for-xaml-overview.md).  
 
 <a name="markup_extensions"></a>   
 ## Markup Extensions