move longjmp bullet under 'Violating assumptions...'

Author: BatmanAoD

src/behavior-considered-undefined.md

@@ -59,9 +59,6 @@ Please read the [Rustonomicon] before writing unsafe code.
 * Executing code compiled with platform features that the current platform
   does not support (see [`target_feature`]), *except* if the platform explicitly documents this to be safe.
 * Calling a function with the wrong [call ABI][abi].
-* Deallocating a Rust stack frame without executing destructors
-  for local variables owned by the stack frame. This can occur
-  with C functions like `longjmp`.
 * Producing an [invalid value][invalid-values]. "Producing" a
   value happens any time a value is assigned to or read from a place, passed to
   a function/primitive operation or returned from a function/primitive
@@ -75,8 +72,11 @@ Please read the [Rustonomicon] before writing unsafe code.
   cast, e.g. by doing raw pointer casts or using a union.
 * Violating assumptions of the Rust runtime. This is only possible using
   mechanisms outside Rust. Most assumptions of the Rust runtime are currently
-  not explicitly documented. For assumptions specifically related to unwinding,
-  see [unwinding-ub].
+  not explicitly documented.
+  * For assumptions specifically related to unwinding, see [unwinding-ub].
+  * Deallocating a Rust stack frame without executing destructors for local
+    variables owned by the stack frame is always undefined. This can occur with
+    C functions like `longjmp`.
 
 > **Note**: Undefined behavior affects the entire program. For example, calling
 > a function in C that exhibits undefined behavior of C means your entire