Fix minor formatting issues

Author: benclmnt

docs/DeveloperGuide.md

@@ -190,7 +190,7 @@ The following diagram shows a possible application state in FitEgo.
 
 <figure style="width:auto; text-align:center; padding:0.5em; font-style: italic; font-size: smaller;">
     <p>
-        <img src="images/tracing/DeleteSessionObjectDiagram.png" style="width: auto; height: 50%;"/>
+        <img src="images/tracing/DeleteSessionObjectDiagram.png" style="width: 80%; height: auto;"/>
     </p>
     <figcaption>Figure - A possible application state</figcaption>
 </figure>
@@ -246,18 +246,18 @@ In designing this feature, we had to consider several alternative ways in which
 
 ### Add Schedule feature
 
-The add schedule feature allows user to create a schedule associated with a client and a session. 
-In other words, it allows user to schedule a client to a session.
+The Add Achedule feature allows user to create a Schedule associated with a Client and a Session. 
+In other words, it allows user to schedule a Client to a Session.
 
 #### Implementation
 
-The add schedule mechanism is facilitated by `AddScheduleCommand` which extends `Command`. The format of the 
+The Add Schedule mechanism is facilitated by `AddScheduleCommand` which extends `Command`. The format of the 
 command is given by: 
 
 ```schadd c/CLIENT_INDEX s/SESSION_INDEX```
-When using this command, the `CLIENT_INDEX` should refer to the index shown in the Client List on the left panel, and is used to specify the client. The `SESSION_INDEX` should refer to the index shown in the Session List on the right panel, and is used to specify the session.
+When using this command, the `CLIENT_INDEX` should refer to the index shown in the Client List on the left panel, and is used to specify the Client. The `SESSION_INDEX` should refer to the index shown in the Session List on the right panel, and is used to specify the Session.
 
-The following activity diagram summarizes the decision making process when a user executes a new `AddSchedule` command. Notice how it checks for overlapping schedule first.
+The following activity diagram summarizes the decision making process when a user executes a new `AddSchedule` command. Notice how it checks for overlapping Schedule first.
 
 ![AddScheduleActivityDiagram](images/AddScheduleActivityDiagram.png)
 
@@ -267,19 +267,19 @@ Assume the current state of Client, Session, and Schedule is as illustrated on t
 
 ![OverlappingScheduleObjectDiagram0](images/OverlappingScheduleObjectDiagram0.png)
 
-Now, consider two cases of add schedule command to be invoked.
+Now, consider two cases of Add Schedule command to be invoked.
 
 **Case 1**:  `schadd c/2 s/1`
 
-Invoking `schadd c/2 s/1` will add a schedule associated with Andy (the second client in the Client List) and endurance training from 12/12/2020 1400 - 1600 (the first session in the Session List).
+Invoking `schadd c/2 s/1` will add a Schedule associated with Andy (the second Client in the Client List) and endurance training from 12/12/2020 1400 - 1600 (the first Session in the Session List).
 
-Thus, the result can be illustrated by the following object diagram, shown by a new created schedule:
+Thus, the result can be illustrated by the following object diagram, shown by a new created Schedule:
 
 ![OverlappingScheduleObjectDiagram1](images/OverlappingScheduleObjectDiagram1.png)
 
 **Case 2:** `schadd c/1 s/1`
 
-On the other hand, invoking `schadd c/1 s/1` will result in an error shown to the user as there is an overlapping schedule (John is already scheduled to endurance training from 12/12/2020 1400 - 1600).
+On the other hand, invoking `schadd c/1 s/1` will result in an error shown to the user as there is an overlapping Schedule (John is already scheduled to endurance training from 12/12/2020 1400 - 1600).
 
 ### \[Proposed\] Undo/redo feature
 

docs/UserGuide.md

@@ -481,7 +481,7 @@ of session view using [<code>sview</code>](#334-viewing-sessions-within-period--
 
 ### 3.3.1 Adding a Session : `sadd`
 
-You can create a session with its relevant details. It will show up on the Session List panel on the right side of the UI.
+You can create a session with its relevant details. If the new session is within the [viewing period](#334-viewing-sessions-within-period--sview) of the Session List, it will be displayed on the right panel of the UI.
 This provides you with an easy reference to the periods in which you have session(s) scheduled and the location of each session.
 
 Format: `sadd g/GYM_NAME ex/EXERCISE_TYPE at/START_TIME t/DURATION`
@@ -490,7 +490,7 @@ Points to take note when adding a session to the Session List:
 * Start time should be of format "dd/MM/yyyy HHmm" (date/month/year Hour minutes in 24 hr format).
 * Duration is in minutes.
 * Duration should be a positive integer (larger than 0).
-* If you want to schedule a session with a client, you need to make sure the session exists in FitEgo, then create a schedule (`schadd`) that references the client and the session.
+* If you want to schedule a session with a client, you need to make sure the session exists in FitEgo, then [create a schedule (`schadd`)](#341-adding-a-schedule--schadd) that references the client and the session.
 
 <div markdown="block" class="alert alert-info"> 
 
@@ -511,7 +511,6 @@ This helps to prevent you from accidentally agreeing to 2 sessions that overlaps
 
 Examples:
 * `sadd g/New Gym ex/Endurance at/06/11/2020 0900 t/65` adds a session at gym `New Gym` with exercise type `Endurance` at `06/11/2020 0900hrs` that lasts for `65` minutes. 
-If the session is within the [viewing period](#334-viewing-sessions-within-period-sview) of the Session List, it will be displayed on the right panel of the UI.
 
 
 ### 3.3.2 Editing a Session : `sedit`

docs/diagrams/AddScheduleActivityDiagram.puml

@@ -1,13 +1,14 @@
 @startuml
 start
-:User executes AddScheduleCommand;
+:User executes Add Schedule command;
 :Parse input from user;
-:Check for overlapping Schedule;
+:Get the specified Client and Session;
+:Check if a Schedule associated with the Client and Session already exists;
 
 ' Since the beta syntax does not support placing the condition outside the
 ' diamond we place it as the true branch instead.
 
-if () then ([Overlapping Schedule is found])
+if () then ([Existing Schedule is found])
     :Show error message to user;
     stop
 else([else])