diff --git a/README.md b/README.md
index ce1e2ee594d858cafe21556b96b26a4479fb83da..9360437c7a3abc8a2cc1df73c2134b5b5dcf2b69 100644
--- a/README.md
+++ b/README.md
@@ -53,11 +53,11 @@ cd Run
 
 FL scripts (including server and client scripts) can be updated, for example, in the `Flower_v1` directory.
 
-#### Important Notes on Flower Client Configuration
+**Important Notes on Flower Client Configuration**
 
 When using this framework for Flower deployment on distributed servers, the client script should not require manual input of the `IP:PORT` for the Flower server. The framework is already designed to handle this automatically.
 
-##### Key Points:
+**Key Points:**
 - The Flower client must be started with the correct `server_address`, which is automatically configured in the framework.
 - Users should **not manually input** the `IP:PORT` in configuration file, as the framework already passes this information automatically. 
 - The client script must be structured to accept the server address as an argument, ensuring compatibility with the framework. 
@@ -83,7 +83,6 @@ So, in Configuration file will not including the IP:PORT of server in client cmd
             },]
   ```
 By following this structure, the deployment will function as expected without requiring manual intervention for the server address configuration.
-```
 
 ### Configure instance for CPU
 Configure instances of experiment in a json format, structure is shown below.