From d504637e7c9fa312e47babd81d9682e894969651 Mon Sep 17 00:00:00 2001 From: Valentin-Gabriel Radu Date: Mon, 3 Jan 2022 15:09:13 +0200 Subject: [PATCH] Updated Reporting problems (markdown) --- Reporting-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reporting-problems.md b/Reporting-problems.md index 42fbc07..e5b7b1c 100644 --- a/Reporting-problems.md +++ b/Reporting-problems.md @@ -32,7 +32,7 @@ VERY useful things to include: Useless things to include: * Personal feelings, especially if not even remotely based on some fact -* Windows Event Log output, besides the crashing module. The information there is 99% of the times useless, being too generic. Instead, use [these](https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps) to enable and collect full crash dumps. +* Windows Event Log output, besides the information about the crashing module. The information there is 99% of the times useless, being too generic. Instead, use [these](https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps) to enable and collect full crash dumps. ### Self fix ExplorerPatcher is a collaborative, open development project that relies on user contributions as well. For simple issues, like typos in the docs, small and relevant changes in the code etc, you can fork the repository, make the change there and submit a pull request for review directly. This is often preferable, if documented well, than asking for the change from me in a new thread.