Update availability.md

updated to reflect switch to exchange email/calendar!

policies/availability.md

@@ -2,15 +2,15 @@
 
 1. For time off known in advance that is more than a single day, such time off should be included in status reports in
    advance so the team can plan for absence.
-2. This time off should also be marked as "Out of Office" or "Busy" on your Colorado Google Calendar as far in advance
+2. This time off should also be marked as "Out of Office" or "Busy" on your [Colorado Exchange Calendar](https://outlook.office.com/calendar/view/week) as far in advance
    as possible.
 3. For large amounts of time (bigger vacations), an email is also often helpful (for instance to let people know if you
    will be completely out of touch, if you want messages marked URGENT, etc).
 
 ### Known time off (1/2 day to full day)
 
 1. For single day time off, best to also include in status reports.
-2. This time off should also be marked as "Out of Office" or "Busy" on your Colorado Google Calendar as far in advance
+2. This time off should also be marked as "Out of Office" or "Busy" on your [Colorado Exchange Calendar](https://outlook.office.com/calendar/view/week) as far in advance
    as possible.
 3. An email does not necessarily need to be sent to the group, but decline the meeting invitation so others know you
    will not be attending.
@@ -24,7 +24,7 @@
 ### Small unavailability (2'ish hours, long lunch, kid duties, errand, etc)
 
 1. Best communicated by changing slack status
-2. It is nice if this time is marked as "Out of Office" or "Busy" on your Colorado Google Calendar (so that others don't
+2. It is nice if this time is marked as "Out of Office" or "Busy" on your [Colorado Exchange Calendar](https://outlook.office.com/calendar/view/week) (so that others don't
    inadvertently schedule meetings with you)
 3. Again if expected to be in a meeting or such, decline the meeting invitation so others know you will not be
    attending.