From 5f62fad81b8b52c19bf7300b0e446ee21e007a91 Mon Sep 17 00:00:00 2001
From: Kurihara <kurihara0-lj@infoseek.jp>
Date: Tue, 7 May 2024 23:46:47 +0900
Subject: [PATCH] Update - README

---
 README.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index e270a5f..3b160e5 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@
 
 Asynchronous I/O communication framework during multi threads and section sequence manager.
 
-You can communicate threads N-to-N with patterns like request-reply and notify.
+Communicate threads N-to-N with patterns like request-reply and notify.
 
 <!--
 Generally, the number of callback functions that receive events increases in asynchronous processing, and the readability of the source code deteriorates. However, this framework improves the readability of the source code by enabling the description through a series of processing sequences.
@@ -49,14 +49,18 @@ Uninstall:
 -->
 <img src="https://github.com/ysan/thread_manager/blob/master/etc/big_picture.png" width="75%" height="75%">
 
+<!--
 ## About sequence
 
 The framework first receives queue, identifies the sequence from the sent queue, and calls that message as an argument to the corresponding sequence. After processing the called sequence, we return control to the framework and enter the next message wait. Sequence switching is done every 1 queue, and other sequences can not operate at all. since sequences on the same thread are always exclusive, exclusion control between sequences is not necessary.
+-->
 
 <!--
 ![about sequence](https://github.com/ysan/thread_manager/blob/master/etc/about_sequence.png)
 -->
+<!--
 <img src="https://github.com/ysan/thread_manager/blob/master/etc/about_sequence.png" width="75%" height="75%">
+-->
 
 ## How to use