diff --git a/docs/enhancements/2023-09-01-cross-silo-error.md b/docs/enhancements/2023-09-01-cross-silo-error.md
index 9188c73..4c44c3b 100644
--- a/docs/enhancements/2023-09-01-cross-silo-error.md
+++ b/docs/enhancements/2023-09-01-cross-silo-error.md
@@ -1,7 +1,15 @@
 ## Summary
+### Changelog
+
+#### [2023-09-01]
+- Fisrt Version
+
+#### [2024-01-03]
+- Update the threading model: main thread is signaled and exit only when exit_on_sending_failure==True.
+
 ### General Motivation
 Before this proposal, when the execution of a DAG encounters an error in 'alice', below is what will happen:
-![image](https://github.com/ray-project/rayfed/assets/26196566/77fa1bd1-dc14-4ddc-8d9e-5dbaf6942564)
+![image](./images/local_error.png)
 
 In alice, both main thread and data sending thread will raise the error, and the process will exit.
 In bob,  since it needs the input from 'alice', it waits for 'alice' forever no matter whether 'alice' exists or not.
@@ -10,19 +18,20 @@ Therefore, we need a mechanism to inform the other participant(s) when the DAG e
 
 ## Design and Architecture
 The below graph shows what will happen now after this proposal:
-![image](https://github.com/ray-project/rayfed/assets/26196566/2f2ad25d-53cb-4ba8-9f3b-38419c7f494b)
+![image](./images/cross_silo_error_flow.png)
 
 In alice, when the data-sending thread finds a RayTaskError indicating an execution failure, it will wrap it as a `FedRemoteError` object and replace the original data object in place to send to bob.
 In bob, the main thread will poll data from receiver actor, where it finds out the data is in the type of `FedRemoteError` and re-raises it, and gets an exception just as what happens in "alice".
 
 The threading model in this proposal is shown below:
-![image](https://github.com/ray-project/rayfed/assets/26196566/bcf8ae62-9842-4618-9d93-a3ae2ac52f8b)
+
+![image](./images/threading_model.png)
 
 ### The explanation of the `_atomic_shutdown_flag`
 When the failure happens, both main thread and data thread get the error and trigger the shutdown, which will execute the "failure handler" twice.  The typical method to ensure the `failure_handler` is executed only once is to set up a flag to check whether it has been executed or not, and wrap it with `threading.lock` because it's a critical section. 
 
 However, this will cause the dead lock as shown in below's graph.
 The data thread triggers the shutdown stage by sending `SIGINT`  signal that is implemented by causing `KeyboardInterrupt` error (step 8). In order to handle the exception, OS will hold the context of the current process, including the acquired `threading.lock` in step 6, and change the context to error handler, i.e. the signal handler in step 9. Since the lock has not yet released, acquiring the same lock will cause the dead lock (step 10).
-![image](https://github.com/ray-project/rayfed/assets/26196566/23c632c8-c6bd-4e36-949b-77abb897fd42)
+![image](./images/dead_lock.png)
 
 The solution is to check the lock before sending the signal. That lock is the `_atomic_shutdown_flag`.
diff --git a/docs/enhancements/images/cross_silo_error_flow.png b/docs/enhancements/images/cross_silo_error_flow.png
new file mode 100644
index 0000000..3f75622
Binary files /dev/null and b/docs/enhancements/images/cross_silo_error_flow.png differ
diff --git a/docs/enhancements/images/dead_lock.png b/docs/enhancements/images/dead_lock.png
new file mode 100644
index 0000000..f0432f0
Binary files /dev/null and b/docs/enhancements/images/dead_lock.png differ
diff --git a/docs/enhancements/images/local_error.png b/docs/enhancements/images/local_error.png
new file mode 100644
index 0000000..8f4481c
Binary files /dev/null and b/docs/enhancements/images/local_error.png differ
diff --git a/docs/enhancements/images/threading_model.png b/docs/enhancements/images/threading_model.png
new file mode 100644
index 0000000..a508f42
Binary files /dev/null and b/docs/enhancements/images/threading_model.png differ