update comment

Author: jjw24

Flow.Launcher/Helper/ErrorReporting.cs

@@ -17,11 +17,12 @@ private static void Report(Exception e, bool silent = false, [CallerMemberName]
         logger.Fatal(ExceptionFormatter.FormatExcpetion(e));
         if (silent) return;
 
+        // Workaround for issue https://github.com/Flow-Launcher/Flow.Launcher/issues/4016
         // The crash occurs in PresentationFramework.dll, not necessarily when the Runner UI is visible, originating from this line:
         // https://github.com/dotnet/wpf/blob/3439f20fb8c685af6d9247e8fd2978cac42e74ac/src/Microsoft.DotNet.Wpf/src/PresentationFramework/System/Windows/Shell/WindowChromeWorker.cs#L1005
-        // Many bug reports because users see the "Report problem UI" after "the" crash with System.Runtime.InteropServices.COMException 0xD0000701 or 0x80263001.
-        // However, displaying this "Report problem UI" during WPF crashes, especially when DWM composition is changing, is not ideal; some users reported it hangs for up to a minute before the "Report problem UI" appears.
-        // This change modifies the behavior to log the exception instead of showing the "Report problem UI".
+        // Many bug reports because users see the "Error report UI" after the crash with System.Runtime.InteropServices.COMException 0xD0000701 or 0x80263001.
+        // However, displaying this "Error report UI" during WPF crashes, especially when DWM composition is changing, is not ideal; some users reported it hangs for up to a minute before the it appears.
+        // This change modifies the behavior to log the exception instead of showing the "Error report UI".
         if (ExceptionHelper.IsRecoverableDwmCompositionException(e)) return;
 
         var reportWindow = new ReportWindow(e);