From c192b39d163997dce317013a9379fddacc27a5c7 Mon Sep 17 00:00:00 2001 From: Zane Bitter Date: Wed, 19 Dec 2018 12:24:37 +1300 Subject: [PATCH] Fix typo Change-Id: Idf2a8c72041e300c10319ef010b251e4b1c9ad50 --- resolutions/20170425-drop-tc-weekly-meetings.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/resolutions/20170425-drop-tc-weekly-meetings.rst b/resolutions/20170425-drop-tc-weekly-meetings.rst index 8d3254ff3..84f37c705 100644 --- a/resolutions/20170425-drop-tc-weekly-meetings.rst +++ b/resolutions/20170425-drop-tc-weekly-meetings.rst @@ -48,7 +48,7 @@ Keeping a rhythm ---------------- The weekly meeting gives us a good regular cadence to keep progress moving -forward. When we loose the regular meeting, we really need to keep this +forward. When we lose the regular meeting, we really need to keep this cadence. This should not be merely be a summary of what has happened, but rather should include a call to action and priority setting, much like the existing meeting agenda that is sent 24 hours before the current meeting.