iOS migration guide update

release-content/0.16/migration-guides/14780_Link_iOS_example_with_rustc_and_avoid_C_trampoline.md

@@ -2,9 +2,28 @@
 
 Previously, the `#[bevy_main]` attribute created a `main_rs` entry point that most Xcode templates were using to run your Rust code from C. This was found to be unnecessary, as you can simply let Rust build your application as a binary, and run that directly.
 
-You have two options for dealing with this:
+You have two options for dealing with this.
 
-If you’ve added further C code and Xcode customizations, or it makes sense for your use-case to continue link with Xcode, you can revert to the old behaviour by adding `#[no_mangle] extern "C" main_rs() { main() }` to your `main.rs`. Note that the old approach of linking a static library prevents the Rust standard library from doing runtime initialization, so certain functionality provided by `std` might be unavailable (stack overflow handlers, stdout/stderr flushing and other such functionality provided by the initialization routines).
+#### New, suggested approach
+
+Preferred option is to remove your “compile” and “link” build phases, and instead replace it with a “run script” phase that invokes `cargo build --bin ...`, and moves the built binary to the Xcode path `$TARGET_BUILD_DIR/$EXECUTABLE_PATH`. An example of how to do this can be viewed in [mobile example](https://github.com/bevyengine/bevy/tree/main/examples/mobile).
+
+If you are not sure how to do this, consider one of two ways:
+- replace local mobile `game` crate with the one in repo and reaplly your changes.
+- replicate the changes from [pull request](https://github.com/bevyengine/bevy/pull/14780) in your `mobile` crate.
 
-The other, preferred option is to remove your “compile” and “link” build phases, and instead replace it with a “run script” phase that invokes `cargo build --bin ...`, and moves the built binary to the Xcode path `$TARGET_BUILD_DIR/$EXECUTABLE_PATH`. An example of how to do this can be viewed at [INSERT LINK TO UPDATED EXAMPLE PROJECT].
 To make the debugging experience in Xcode nicer after this, you might also want to consider either enabling `panic = "abort"` or to set a breakpoint on the `rust_panic` symbol.
+
+#### Restoring old behaviour
+
+If you’ve added further C code and Xcode customizations, or it makes sense for your use-case to continue link with Xcode, you can revert to the old behaviour by adding code below to your `main.rs` file:
+
+```rust
+#[cfg(target_os = "ios")]
+#[no_mangle]
+extern "C" fn main_rs() {
+    main()
+}
+```
+
+Note that the old approach of linking a static library prevents the Rust standard library from doing runtime initialization, so certain functionality provided by `std` might be unavailable (stack overflow handlers, stdout/stderr flushing and other such functionality provided by the initialization routines).