Update README.md

README.md

@@ -59,7 +59,7 @@ The edited resources are saved in .resx files in the `Resources` subfolder of th
 
 > _Note:_ If you create a localization for your language feel free to [submit a new issue](https://github.com/koszeggy/KGySoft.Drawing.Tools/issues/new?assignees=&labels=&template=submit-resources.md&title=%5BRes%5D) and I will make it available for everyone. Don't forget to mention your name in the translated About menu.
 
-#### Help, my reasources are gone!
+#### Help, my resources are gone!
 
 If you use Imaging Tools as debugger visualizers, then it can be executed from various locations. See the bottom of the [Troubleshooting](#troubleshooting) section below.
 
@@ -145,7 +145,7 @@ If Visual Studio cannot load the visualizer or you have other debugger visualize
 | Could not load this custom viewer.<br/>![Could not load this custom viewer.](https://kgysoft.net/images/DebuggerVisualizerTrShCouldNotLoadViewer.png) | Open _Debug / Options / Debugging / General_ and make sure that both _Use Managed Compatibility Mode_ and _Use legacy C# and VB expression evaluators_ are unchecked.<br/>![Debugging Options.](https://kgysoft.net/images/DebuggerVisualizerTrShCouldNotLoadSettings.png) |
 | An unhandled exception of type 'System.InvalidOperationException' was thrown by the custom visualizer component in the process being debugged. (Object is currently in use elsewhere.)<br/>![Object is currently in use elsewhere.](https://kgysoft.net/images/DebuggerVisualizerTrShObjectIsInUse.png) | You try to debug a `Graphics` instance, whose Device Context is in use (the `GetHdc` method has been called previously). This `Graphics` instance cannot be accessed until the `ReleaseHdc` method is called. |
 | Unable to perform function evaluation on the process being debugged (Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.)<br/>![Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.](https://kgysoft.net/images/DebuggerVisualizerTrShOptimized.png) | Can occur even with debug build, typically when debugging a .NET Core project. When it happens, then likely all members in the debug window show a similar error message. Perform a Step Over operation (F10 by default)/Set Next Statement (Ctrl+Shift+F10), or restart the debugging session and try again. |
-| Unable to perform function evaluation on the process being debugged (Function evaluation timed out)<br/>![Function evaluation timed out.](https://kgysoft.net/images/DebuggerVisualizerTrShTimeout.png) | On slower computers with a slower Visual Studio (with many add-ons, for example) it can happen that the visualizer loads too slowly for the first time. Just try to click the magnifier icon again, which usually solves the problem. Alternatively, you can try to set a `DWORD` value in the Registry under the `HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\[version]\Debugger` key, called `LocalsTimeout`. The value represents milliseconds. |
+| Unable to perform function evaluation on the process being debugged (Function evaluation timed out)<br/>![Function evaluation timed out.](https://kgysoft.net/images/DebuggerVisualizerTrShTimeout.png) | It can happen that the visualizer loads too slowly for the first time. Just try to click the magnifier icon again, which usually solves the problem. If all members in the debug window show an error, then perform a Step Over operation first (F10 by default). |
 | Unable to load the custom visualizer (Operation is not valid due to the current state of the object)<br/>![Operation is not valid due to the current state of the object.](https://kgysoft.net/images/DebuggerVisualizerTrShOperationIsNotValid.png) | Typically happens after timeout. Likely all members in the debug window show a similar error message. Perform a Step Over operation (F10 by default)/Set Next Statement (Ctrl+Shift+F10), or restart the debugging session and try again. |
 | An unhandled exception of type 'System.NullReferenceException' was thrown by the custom visualizer component in the process being debugged.<br/>![An unhandled exception of type 'System.NullReferenceException' was thrown by the custom visualizer component in the process being debugged.](https://kgysoft.net/images/DebuggerVisualizerTrShExceptionNullRef.png) | • Occurs when you clear the debugged image in Visual Studio 2019, which does not support nullifying the debugged value.<br/>The bug has been [reported](https://developercommunity.visualstudio.com/content/problem/676481/visual-sudio-2019-throws-a-nullreferenceexception.html) to the VisualStudio team.<br/><br/> • Occurs in Visual Studio 2019 also when replacing a `Color` entry in an array by the visualizer.<br/>The bug has been [reported](https://developercommunity.visualstudio.com/content/problem/1142584/visual-sudio-2019-throws-a-nullreferenceexception-1.html) to the VisualStudio team. |
 | The Color visualizer appears in read-only, even though the debugged value is in a read-write context (eg. local variable).<br/>![Color visualizer appears as read-only.](https://kgysoft.net/images/DebuggerVisualizerTrShColorReadOnly.png) | Occurs with some specific builds of Visual Studio 2019<br/>The bug has been [reported](https://developercommunity.visualstudio.com/content/problem/1142584/visual-sudio-2019-throws-a-nullreferenceexception-1.html) to the VisualStudio team as part of another issue. |