From e5d93d2cf02fb0e2cb2a24ddff76e81faae9b39c Mon Sep 17 00:00:00 2001 From: Vaibhav Srivastava Date: Sat, 29 Aug 2026 13:15:05 +0530 Subject: [PATCH] docs: fix typo occured -> occurred (#4935) Signed-off-by: Vaibhav Srivastava --- documents/Debugging/Debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documents/Debugging/Debugging.md b/documents/Debugging/Debugging.md index a87e7b5e6..500152c02 100644 --- a/documents/Debugging/Debugging.md +++ b/documents/Debugging/Debugging.md @@ -131,7 +131,7 @@ This section will provide some preliminary steps to take and tips on what to do - **Logs aren't always accurate in determining the reason for a crash.**\ Some log entries are reported as errors but may not be fatal for the execution to stop. `Critical` entries are most likely to be the cause for crashes. - - Pinpoint the area of the emulator where the crash occured\ + - Pinpoint the area of the emulator where the crash occurred\ If the stack trace ends with functions that are relevant to rendering, it is safe to assume that the issue is with **rendering**.\ Similarly, if a crash is in a library responsible for playing videos, your issue can be narrowed down to the scope of video playback in the emulator.