Removed comments (#628)

Documentation/compatibility/changing-the-isenabled-property-of-the-parent-of-a-textblock-control-affects-any-child-controls.md

@@ -22,8 +22,8 @@ reflect the state of the
 <xref:System.Windows.UIElement.IsEnabled?displayProperty=name> property of the
 <xref:System.Windows.Controls.TextBlock?displayProperty=name> parent.
 
-- [ ] Quirked // Uses some mechanism to turn the feature on or off, usually using runtime targeting, AppContext or config files. Needs to be turned on automatically for some situations.
-- [ ] Build-time break // Causes a break if attempted to recompile
+- [ ] Quirked
+- [ ] Build-time break 
 
 ### Recommended Action
 None. This change conforms to the expected behavior for controls inside a <xref:System.Windows.Controls.TextBlock?displayProperty=name> control.

Documentation/compatibility/etw-event-names-cannot-differ-only-by-suffix.md

@@ -16,8 +16,8 @@ NotPlanned
 ### Change Description
 In the .NET Framework 4.6 and 4.6.1, the runtime throws an <xref:System.ArgumentException> when two Event Tracing for Windows (ETW) event names differ only by a "Start" or "Stop" suffix (as when one event is named `LogUser` and another is named `LogUserStart`). In this case, the runtime cannot construct the event source, which cannot emit any logging.
 
-- [X] Quirked // Uses some mechanism to turn the feature on or off, usually using runtime targeting, AppContext or config files. Needs to be turned on automatically for some situations.
-- [ ] Build-time break // Causes a break if attempted to recompile
+- [X] Quirked 
+- [ ] Build-time break 
 
 ### Recommended Action
 

Documentation/compatibility/horizontal-scrolling-and-virtualization.md

@@ -51,8 +51,8 @@ after a horizontal scroll, whether invoked by the end user or by an explicit
 call to
 <xref:System.Windows.Controls.Primitives.IScrollInfo.SetHorizontalOffset(System.Double)>.
 
-- [ ] Quirked // Uses some mechanism to turn the feature on or off, usually using runtime targeting, AppContext or config files. Needs to be turned on automatically for some situations.
-- [ ] Build-time break // Causes a break if attempted to recompile
+- [ ] Quirked 
+- [ ] Build-time break
 
 ### Recommended Action
 

Documentation/compatibility/sql-server-database-connection-that-resolves-to-localhost.md

@@ -16,8 +16,8 @@ NotPlanned
 
 In the .NET Framework 4.6 and 4.6.1, attempting a TCP/IP connection to a SQL Server database that resolves to `localhost` fails with the error, "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"
 
-- [ ] Quirked // Uses some mechanism to turn the feature on or off, usually using runtime targeting, AppContext or config files. Needs to be turned on automatically for some situations.
-- [ ] Build-time break // Causes a break if attempted to recompile
+- [ ] Quirked 
+- [ ] Build-time break 
 
 ### Recommended Action
 

Documentation/compatibility/wcf-services-using-nettcp-with-ssl-security-and-md5-certificate-authentication.md

@@ -14,8 +14,8 @@ The .NET Framework 4.6 adds TLS 1.1 and TLS 1.2 to the WCF SSL default protocol
 
 TLS 1.2 does not support MD5 certificate authentication. As a result, if a customer uses an MD5 certificate, the WCF client will fail to connect to the WCF service. 
 
-- [ ] Quirked // Uses some mechanism to turn the feature on or off, usually using runtime targeting, AppContext or config files. Needs to be turned on automatically for some situations.
-- [ ] Build-time break // Causes a break if attempted to recompile
+- [ ] Quirked 
+- [ ] Build-time break
 
 ### Recommended Action
 You can work around this issue so that a WCF client can connect to a WCF server by doing any of the following: