From 1e20035cfe25af8c5d3a14de774f59e1e3a1be56 Mon Sep 17 00:00:00 2001
From: huongdm1896 <domaihuong1451997@gmail.com>
Date: Tue, 18 Mar 2025 18:11:19 +0100
Subject: [PATCH] readme

---
 README.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index ce1e2ee..9360437 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.
-- 
GitLab