Markdig changes

docs/framework/data/adonet/entity-data-model-key-concepts.md

@@ -12,7 +12,7 @@ The Entity Data Model (EDM) uses three key concepts to describe the structure of
  Inheritance is supported with entity types: that is, one entity type can be derived from another. For more information, see [Entity Data Model: Inheritance](entity-data-model-inheritance.md).  
 
 ## Association Type  
- An [association type](association-type.md) (also called an association) is the fundamental building block for describing relationships in the Entity Data Model. In a conceptual model, an association represents a relationship between two entity types (such as Customer and Order). Every association has two [association ends](association-end.md) that specify the entity types involved in the association. Each association end also specifies an [association end multiplicity](association-end-multiplicity.md) that indicates the number of entities that can be at that end of the association. An association end multiplicity can have a value of one (1), zero or one (0..1), or many (*). Entities at one end of an association can be accessed through [navigation properties](navigation-property.md), or through foreign keys if they are exposed on an entity type. For more information, see [foreign key property](foreign-key-property.md).  
+ An [association type](association-type.md) (also called an association) is the fundamental building block for describing relationships in the Entity Data Model. In a conceptual model, an association represents a relationship between two entity types (such as Customer and Order). Every association has two [association ends](association-end.md) that specify the entity types involved in the association. Each association end also specifies an [association end multiplicity](association-end-multiplicity.md) that indicates the number of entities that can be at that end of the association. An association end multiplicity can have a value of one (1), zero or one (0..1), or many (\*). Entities at one end of an association can be accessed through [navigation properties](navigation-property.md), or through foreign keys if they are exposed on an entity type. For more information, see [foreign key property](foreign-key-property.md).  
 
  In an application, an instance of an association represents a specific association (such as an association between an instance of Customer and instances of Order). Association instances are logically grouped in an [association set](association-set.md). Association sets (and [entity sets](entity-set.md)) are logically grouped in an [entity container](entity-container.md).  
 

docs/framework/data/adonet/sql/handling-null-values.md

@@ -29,7 +29,7 @@ A null value in a relational database is used when the value in a column is unkn
  ![Truth Table](./media/truthtable-bpuedev11.gif "TruthTable_bpuedev11")  
 
 ### Understanding the ANSI_NULLS Option  
- <xref:System.Data.SqlTypes> provides the same semantics as when the ANSI_NULLS option is set on in SQL Server. All arithmetic operators (+, -, *, /, %), bitwise operators (~, &, &#124;), and most functions return null if any of the operands or arguments is null, except for the property `IsNull`.  
+ <xref:System.Data.SqlTypes> provides the same semantics as when the ANSI_NULLS option is set on in SQL Server. All arithmetic operators (+, -, \*, /, %), bitwise operators (~, &, \|), and most functions return null if any of the operands or arguments is null, except for the property `IsNull`.  
 
  The ANSI SQL-92 standard does not support *columnName* = NULL in a WHERE clause. In SQL Server, the ANSI_NULLS option controls both default nullability in the database and evaluation of comparisons against null values. If ANSI_NULLS is turned on (the default), the IS NULL operator must be used in expressions when testing for null values. For example, the following comparison always yields unknown when ANSI_NULLS is on:  
 

docs/framework/wcf/extending/creating-user-defined-bindings.md

@@ -33,10 +33,10 @@ There are several ways to create bindings not provided by the system:
 |Reliability|<xref:System.ServiceModel.Channels.ReliableSessionBindingElement?displayProperty=nameWithType>|No|  
 |Security|<xref:System.ServiceModel.Channels.SecurityBindingElement?displayProperty=nameWithType>|No|  
 |Composite Duplex|<xref:System.ServiceModel.Channels.CompositeDuplexBindingElement?displayProperty=nameWithType>|No|  
-|Encoding|Text, Binary, MTOM, Custom|Yes*|  
+|Encoding|Text, Binary, MTOM, Custom|Yes\*|  
 |Transport|TCP, Named Pipes, HTTP, HTTPS, MSMQ, Custom|Yes|  
 
- *Because an encoding is required for each binding, if an encoding is not specified, WCF adds a default encoding for you. The default is Text/XML for the HTTP and HTTPS transports, and Binary otherwise.  
+\*Because an encoding is required for each binding, if an encoding is not specified, WCF adds a default encoding for you. The default is Text/XML for the HTTP and HTTPS transports, and Binary otherwise.  
 
 ## Creating a new Binding Element  
  In addition to the types derived from <xref:System.ServiceModel.Channels.BindingElement> that are provided by WCF, you can create your own binding elements. This lets you customize the way the stack of bindings is created and the components that go in it by creating your own <xref:System.ServiceModel.Channels.BindingElement> that can be composed with the other system-provided types in the stack.