Skip to content

Commit 23635f6

Browse files
committed
Too much future
1 parent a5fc4c9 commit 23635f6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2019-12-03-managing-pagerduty-rotations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ solutions (people) as quickly as possible. When we discussed the various
105105
options with the entire team, the only clear path forward was to adopt the last
106106
option: switch to a 24/7 schedule for the developers on Core Platform. We
107107
shared the entire process, and conclusion with our friends at PagerDuty. I hope that we
108-
see a feature in the future which allows Schedules to be built from both users
108+
see a feature which allows Schedules to be built from both users
109109
_and_ other Schedules in the future. That level of composition would give us
110110
the flexibility to accomplish our _ideal_ end-state for developer incident
111111
response.

0 commit comments

Comments
 (0)