From 451b52622d39373ad1f27352981b4d74795699a4 Mon Sep 17 00:00:00 2001
From: tsulim <limxiujia18@gmail.com>
Date: Mon, 15 Apr 2024 06:33:23 +0800
Subject: [PATCH] Resize diagrams in developer guide

---
 docs/DeveloperGuide.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/DeveloperGuide.md b/docs/DeveloperGuide.md
index ea352d0597b..6218d6b7c7e 100644
--- a/docs/DeveloperGuide.md
+++ b/docs/DeveloperGuide.md
@@ -182,7 +182,7 @@ The below sequence diagram goes into more detail on how the command is parsed in
 
 The below activity diagram illustrates the process when a user executes a edit command.
 
-<img src="images/EditActivityDiagram.png" width="250" />
+<img src="images/EditActivityDiagram.png" width="740" />
 
 #### Why edit is implemented this way
 
@@ -220,7 +220,7 @@ The below sequence diagram goes into more detail on how the command is parsed in
 
 The below activity diagram illustrates the process when a user executes a find command.
 
-<img src="images/FindActivityDiagram.png" width="250" />
+<img src="images/FindActivityDiagram.png" width="450" />
 
 #### Why find is implemented this way
 
@@ -297,7 +297,7 @@ The sequence diagram for executing a **"sort n/"** is shown below:
 
 The following activity diagram summarizes what happens when a user executes a new sort command:
 
-<img src="images/SortActivityDiagram.png" width="450" />
+<img src="images/SortActivityDiagram.png" width="600" />
 
 #### Why sort is implemented this way