From ca7e907659da7941dd205579c3ab2b548381d824 Mon Sep 17 00:00:00 2001
From: TomOstertag <121185965+TomOstertag@users.noreply.github.com>
Date: Wed, 15 Feb 2023 23:50:11 -0600
Subject: [PATCH] Handbook; Scrum Section Typos (#9387)

Charlie led onboarding we fixed some typos.
---
 handbook/engineering/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md
index eea9ff6300..e6b800956f 100644
--- a/handbook/engineering/README.md
+++ b/handbook/engineering/README.md
@@ -33,7 +33,7 @@ The following is the subset of proposed engineering meetings. Each group is free
 - Sprints are 3 weeks long to match our release cadence.
 - There are 5 “Scrum Ceremonies” performed during each sprint:
   - Sprint planning - At the first Monday of the sprint the team and stakeholders meet and pick items from the backlog. The team commit to finish those items.
-  - Daily sync standup - The team meet daily for updates. Each team member present what they did since the last sync and what they intend to do until next sync. Any impediments are raised.
+  - Daily sync standup - The team meets daily for updates. Each team member presents what they did since the last sync and what they intend to do until next sync. Any road blocks are raised.
   - Weekly estimation sessions - once a week (3 times a sprint) the team will estimate items in the backlog. Goals:
     - Have Stakeholders know in advance the time it will take to achieve those items.
     - Make it easier in the next planning meeting to know what the team can take for the next sprint.