1.1 --- a/docs/wiki/UseCases Tue Oct 27 18:56:08 2015 +0100
1.2 +++ b/docs/wiki/UseCases Tue Oct 27 19:06:56 2015 +0100
1.3 @@ -8,13 +8,13 @@
1.4 * Enforce booking privileges
1.5
1.6 * Enforce booking "budgets" to prevent people booking too many things or
1.7 - booking things simultaneously that they will attend
1.8 + booking things simultaneously that they will attend
1.9
1.10 * Support pools of resources where one address may be responsible for
1.11 multiple units that are not individually identified at the time of booking
1.12
1.13 * Support duration limits and start/end time granularity, using `COUNTER` to
1.14 - suggest acceptable periods
1.15 + suggest acceptable periods
1.16
1.17 == Appointment Booking ==
1.18
1.19 @@ -31,13 +31,13 @@
1.20 participants followed by the selection of a specific period by an organiser.
1.21
1.22 1. Free/busy information is solicited from potential recipients by the
1.23 - organiser.
1.24 + organiser.
1.25
1.26 1. Recipients respond with details of their availability (typically
1.27 - emphasising when they are free for the event, busy otherwise).
1.28 + emphasising when they are free for the event, busy otherwise).
1.29
1.30 1. The organiser then decides on a free period and notifies all free
1.31 - participants as normal.
1.32 + participants as normal.
1.33
1.34 1. Recipients respond as normal to the event invitation.
1.35