mini

docs/DeveloperGuide.adoc

@@ -572,9 +572,9 @@ The PrisonBook calendar commands will instantiate a calendar class to interact w
 The initial step is to obtain valid credentials authorized from the API side to access its resources, then
 the calendar class will send HTTPS requests to the server, whether it is calling the listEvents, addEvents or delEvents API command.
 
-Calendar Commands that are supported are:
-* listing upcoming events
-* adding an event
+Calendar Commands that are supported are: +
+* listing upcoming events +
+* adding an event +
 * removing an event
 
 image::CalendarCommands_classDiagrams.PNG[Width="350"]
@@ -591,7 +591,7 @@ image::CalendarCommands_classDiagrams.PNG[Width="350"]
  ** Pros: Two accounts is still relatively simple to maintain, allows for some separation of events-scheduling.
  ** Cons: All guards still share the same schedule, so they cannot have personal schedules.
  * **Alternative 4:** Use one Google account for Warden and one for Guards
- ** Pros: All prison staff have their own calendar to work with, where they can have private individual events.
+ ** Pros: All prison staff have their own calendar for private individual events.
  ** Cons: Hard to maintain because we have to make sure all staff have the master prison schedule of the inmates' activities non-overlapping with personal events. There will also be a lot of calendars to keep track of, depending on how many guards are hired.
 
 ===== Aspect: Choosing Number of Calendars per Person