diff --git a/releases/net471/KnownIssues/481090-WPF Touch generates NullReferenceException in ProcessInputReport.md b/releases/net471/KnownIssues/481090-WPF Touch generates NullReferenceException in ProcessInputReport.md
index ea53d00..4712603 100644
--- a/releases/net471/KnownIssues/481090-WPF Touch generates NullReferenceException in ProcessInputReport.md	
+++ b/releases/net471/KnownIssues/481090-WPF Touch generates NullReferenceException in ProcessInputReport.md	
@@ -1,10 +1,10 @@
-## WPF Touch generates a NullReferenceException in WispLogic.ProcessInputReport
+# WPF Touch generates a NullReferenceException in WispLogic.ProcessInputReport
 
-### Symptoms
+## Symptoms
 WPF throws a NullReferenceException in WispLogic.ProcessInputReport and the application may crash.
 
-### Cause
+## Cause
 In WPF applications running on touch or stylus enabled machines, specific hardware and timing issues can cause touch messages to arrive without associated StylusDevices.  When this occurs WPF tries to access this null StylusDevice, causing the error.
 
-### Resolution
-This issue is fixed for all supported OS platforms prior to Windows 10 Fall Creators Update. The fix for Windows 10 Fall Creators Update is expected in a future servicing update. 
\ No newline at end of file
+## Resolution
+This issue is fixed for all supported OS platforms prior to Windows 10 Fall Creators Update. The fix for Windows 10 Fall Creators Update is expected in a future servicing update.