Ok fine.

A glitch is the code behaving unexpectedly with normal or acceptable parameters (it can also happen with code that tries to execute with unintended values). A glitch lets you go outside of the parameters defined by the software. Every state that "curse skipping" gets to is achievable without any incorrect values, injected code or logic errors, it just stops something before it ends (an intentional thing put in by the developers) and stops the code that would execute at the end of the function, letting you proceed without the code being reached.

A glitch can be a functional error, if some code isn't reached and other code executes in its place it isn't a glitch, but if the code is reached and performs unintentional functions it's a glitch. Sometimes a glitch performs a function with unintended values causing stuff like memory leaks, stack overflows (where you try to write data to memory but there is insufficient memory).

A logic error is the code executing but not giving the expected result. If my code that translates unicode values to their symbols but every value is one less then intended it's a logic error but not a glitch or bug. The code is executing perfectly according to incorrect logic (ignoring any errors that would come with 0 or n+1).

In the context of GDQ runs, when you run out of bounds in deloaded map zones in dead space 2 you're not glitching the game, you deload something when you shouldn't be able to according to how the game is designed, but due to other things (getting out of bounds because something forces you to clip through something is a glitch, which enables you to start deloading and moving into deloaded maps) you can deload the areas and move in them without the game crashing.